Ever since Blogger added the domain ownership verification requirement to blogs published to custom domains, we've been seeing various complaints from some blog owners, who have purchased domains directly from registrars who can't provide the required DNS addresses on their servers.
Last month, Blogger Engineering, responding to the complaints, provided a workaround to the problem.
Even though not all registrars have DNS servers that will provide the right DNS address entries, most registrars will allow us to use third party DNS servers. The use of publicly available DNS servers, which can provide the required DNS addresses, will eliminate the need to transfer domain registration - when the registrar is unable to provide the right DNS addresses, using their own servers.
If you're trying to setup your domain, purchased from 1And1 or a similar registrar, you need only to setup a suitable third party DNS server. Marc Ridey, of Blogger Engineering, describes three simple steps, added to the normal third party registrar domain setup process.
Any time that you need to update DNS addresses, use the CloudDNS Domain Manager wizard.
(Note): CloudDNS, when setup, may offer the option to redirect the domain root (aka "naked domain") to the "www" alias (or whatever DNS address you may setup). For best results, you should ignore that option, and use the Blogger or Google Apps redirect. There are still only three acceptable DNS models - use of CloudDNS, or any comparable DNS host, will not change that.
This may not be an ideal solution for the problem - it introduces a bit of complexity into the domain setup process - but it will allow owners of newly purchased domains from 1And1, Network Solutions, and others to get their domains verified, and get their blogs online again. And, since this starts with blog owners who elected to purchase their domain directly from a registrar - and setup the domain themselves - maybe it's not too much, technically.
It's also possible that this technique can be used for victims of the eNom DNS Infrastructure problem - and for those who only purchased Name Registration, directly from the registrar.
If you are using your third party registrar because you have actual web content (a web site, email, files, or other service) hosted by the registrar, please note the warning by Marc!
>> Top
Last month, Blogger Engineering, responding to the complaints, provided a workaround to the problem.
Even though not all registrars have DNS servers that will provide the right DNS address entries, most registrars will allow us to use third party DNS servers. The use of publicly available DNS servers, which can provide the required DNS addresses, will eliminate the need to transfer domain registration - when the registrar is unable to provide the right DNS addresses, using their own servers.
If you're trying to setup your domain, purchased from 1And1 or a similar registrar, you need only to setup a suitable third party DNS server. Marc Ridey, of Blogger Engineering, describes three simple steps, added to the normal third party registrar domain setup process.
- Setup a (free) CloudDNS account.
- Setup your normal DNS addresses (including the required domain ownership verification "CNAME") in CloudDNS, using the CloudDNS Domain Manager wizard.
- Setup your domain, using your registrar's domain manager wizard, pointing to the CloudDNS DNS servers.
Any time that you need to update DNS addresses, use the CloudDNS Domain Manager wizard.
(Note): CloudDNS, when setup, may offer the option to redirect the domain root (aka "naked domain") to the "www" alias (or whatever DNS address you may setup). For best results, you should ignore that option, and use the Blogger or Google Apps redirect. There are still only three acceptable DNS models - use of CloudDNS, or any comparable DNS host, will not change that.
This may not be an ideal solution for the problem - it introduces a bit of complexity into the domain setup process - but it will allow owners of newly purchased domains from 1And1, Network Solutions, and others to get their domains verified, and get their blogs online again. And, since this starts with blog owners who elected to purchase their domain directly from a registrar - and setup the domain themselves - maybe it's not too much, technically.
It's also possible that this technique can be used for victims of the eNom DNS Infrastructure problem - and for those who only purchased Name Registration, directly from the registrar.
If you are using your third party registrar because you have actual web content (a web site, email, files, or other service) hosted by the registrar, please note the warning by Marc!
Warning: If you are using 1and1 hosting services to display a website as well as a Blogger blog, these instructions will disable the website. Please post a comment with your website address and I'll check how these instructions must be updated. If you're using eMail, remember to complete the optional eMail step.
>> Top
Subscribe to: Post Comments (Atom)
This is very helpful for a newbie SEO person. I just bookmarked this post for future reference. Keep sharing this kind of post. Thanks for sharing
ReplyDeleteReliable dedicated server