A lot of people have been rooting for Google to bring a new method of verification to Google Webmaster Central and today, we have it: DNS Verification. We’ll explain how to properly set this record for WHM in just a moment (as a server or VPS admin), but the technique should be all the same. Here’s what Google had to say, read on after the blog to find out how to do it yourself.
DNS Verification FTW Wednesday, March 31, 2010 at 1:16 PM Webmaster Level: Advanced
A few weeks ago, we introduced a new way of verifying site ownership, making it easy to share verified ownership of a site with another person. This week, we bring you another new way to verify. Verification by DNS record allows you to become a verified owner of an entire domain (and all of the sites within that domain) at once. It also provides an alternative way to verify for folks who struggle with the existing HTML file or meta tag methods.
I like to explain things by walking through an example, so let’s try using the new verification method right now. For the sake of this example, we’ll say I own the domain example.com. I have several websites under example.com, including http://www.example.com/, http://blog.example.com/ and http://beta.example.com/. I could individually verify ownership of each of those sites using the meta tag or HTML file method. But that means I’d need to go through the verification process three times, and if I wanted to add http://customers.example.com/, I’d need to do it a fourth time. DNS record verification gives me a better way!
On the verification page, I select the “Add a DNS record” verification method, and follow the instructions to add the specified TXT record to my domain’s DNS configuration.
When I click “Verify,” Google will check for the TXT record, and if it’s present, I’ll be a verified owner of example.com and any associated websites and subdomains. Now I can use any of those sites in Webmaster Tools and other verification-enabled Google products without having to verify ownership of them individually.
If you try DNS record verification and it doesn’t work right away, don’t despair!
Sometimes DNS records take a while to make their way across the Internet, so Google may not see them immediately. Make sure you’ve added the record exactly as it’s shown on the verification page. We’ll periodically check, and when we find the record we’ll make you a verified owner without any further action from you.
DNS record verification isn’t for everyone—if you don’t understand DNS configuration, we recommend you continue to use the HTML file and meta tag methods. But for advanced users, this is a powerful new option for verifying ownership of your sites.
As always, please visit the Webmaster Help Forum if you have any questions.
Posted by Sean Harding, Software Engineer
So! Now, you may be onboard or you may be very confused. No worries. Let’s explain the anatomy of a TXT, or text, record.
name ttl class TXT text
With this in mind, you can easily SSH and dig txt domain.com, or go to http://www.kloth.net and do a DIG for TXT, to the domain of your choice. We originally speculated that you can have multiple TXT records, and you can. The trick, however, is in the name of the TXT record. Your TXT record name much match the CNAME of the domain that you are trying to create the record for or else it will not show up in the answer section of a DNS lookup. Therefore, let’s use turkreno.com as an example:
turkreno.com. 14400 IN TXT “google-site-verification: asdfasdlkfaslkjas2f2f2f2kfkjf2jkfkj2fkj2f”
Just make sure that you have a matching CNAME to the name of your TXT record and put your Google Site Verification in quotation marks, and you should be good to go! Post us some feedback if you have other ways on other DNS systems that this should be done and we’ll approve your comment!