Back in December 2008, Google was finishing the process of deploying the new Google Apps DNS servers - a set of 4, to replace the old set of 3. Around that time, Blogger Support had (unofficially) stated that they would inform us when the old 3 servers had been officially retired, so bloggers everywhere who used the Custom Domain Asymmetrical DNS Configuration would know, definitively, when it was essential to update their DNS setup.
It's now 9 months later, and we have still gotten no official word. In the mean time, almost weekly, we see problem reports with attempted use of the old 3 servers (all long offline) being the center of the problem.
Enough. In my opinion, all bloggers using the old 3 servers, for their domain DNS, need to update their DNS setups. You need to have your domain using the 4 new Google Apps DNS servers.
For the record, I will now state this.
Anybody with a custom domain using a DNS setup of
needs to immediately update to
I can't hazard a guess why anybody would not have updated, but it appears that this is still the case.
For the sake of your readers, update your Custom Domain DNS configurations. This week, or sooner.
>> Top
It's now 9 months later, and we have still gotten no official word. In the mean time, almost weekly, we see problem reports with attempted use of the old 3 servers (all long offline) being the center of the problem.
Enough. In my opinion, all bloggers using the old 3 servers, for their domain DNS, need to update their DNS setups. You need to have your domain using the 4 new Google Apps DNS servers.
For the record, I will now state this.
Anybody with a custom domain using a DNS setup of
mydomain.com. 3600 IN A 64.233.179.121
mydomain.com. 3600 IN A 66.249.81.121
mydomain.com. 3600 IN A 72.14.207.121
www.mydomain.com. 3600 IN CNAME ghs.google.com.
needs to immediately update to
mydomain.com. 1800 IN A 216.239.32.21
mydomain.com. 1800 IN A 216.239.34.21
mydomain.com. 1800 IN A 216.239.36.21
mydomain.com. 1800 IN A 216.239.38.21
www.mydomain.com. 3600 IN CNAME ghs.google.com.
I can't hazard a guess why anybody would not have updated, but it appears that this is still the case.
For the sake of your readers, update your Custom Domain DNS configurations. This week, or sooner.
>> Top
Comments