Custom Domain Publishing has come a long way since February 2007, when I wrote Custom Domain Names Hosted By Blogger. For a while, each custom domain was setup by hand, resulting in a variety of configurations. This prompted my Custom Domain Setup series of articles.
Then, Blogger developed the "Buy A Domain For Your Blog" wizard, and the Custom Domain Google Apps configuration, which provided an easy and standard setup. This worked for domains setup specifically to host Blogger blogs, as well as domains which host additional services. This lead, eventually, to my Righteous Solutions and Spurious Solutions pair of articles.
That was a clean setup, and it worked for both "nitecruzr.net" and "www.nitecruzr.net", and for services besides a plain Blogger blog - for a while.
(Update 2008/12): Servers "64.233.179.121" and "66.249.81.121" having been removed from service, the correct configuration is now:
or possibly
Occasionally, we see something vaguely resembling the latter setup.
The "68.142.212.nnn" series of DNS servers are the Yahoo equivalent of Google Apps. A Yahoo registered domain, in the Yahoo world, gets the same treatment as a Google Apps custom domain, with integrated, online accessories for the primary domain. But the primary domain goes to the Yahoo servers, instead of to the Google Apps servers.
And, when an anxious blogger selects "Redirect mydomain.com to www.mydomain.com.", and gets a well known (and not loved) error
Right now, we have no experience with making a Blogger blog, published to the primary domain, work properly when Yahoo DNS is involved. It appears that the best solution, in this case, is to get a third party DNS service that supports "CNAME" referral, and avoid Yahoo DNS altogether.
>> Top
Then, Blogger developed the "Buy A Domain For Your Blog" wizard, and the Custom Domain Google Apps configuration, which provided an easy and standard setup. This worked for domains setup specifically to host Blogger blogs, as well as domains which host additional services. This lead, eventually, to my Righteous Solutions and Spurious Solutions pair of articles.
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.
That was a clean setup, and it worked for both "nitecruzr.net" and "www.nitecruzr.net", and for services besides a plain Blogger blog - for a while.
(Update 2008/12): Servers "64.233.179.121" and "66.249.81.121" having been removed from service, the correct configuration is now:
mydomain.com. 3600 IN A 72.14.207.121
www.mydomain.com. 3600 IN CNAME ghs.google.com.
or possibly
mydomain.com. 3600 IN A 216.239.32.21
mydomain.com. 3600 IN A 216.239.34.21
mydomain.com. 3600 IN A 216.239.36.21
mydomain.com. 3600 IN A 216.239.38.21
www.mydomain.com. 3600 IN CNAME ghs.google.com.
Occasionally, we see something vaguely resembling the latter setup.
mydomain.com. 1200 IN A 68.142.212.118
mydomain.com. 1200 IN A 68.142.212.119
mydomain.com. 1200 IN A 68.142.212.120
mydomain.com. 1200 IN A 68.142.212.121
mydomain.com. 1200 IN A 68.142.212.122
mydomain.com. 1200 IN A 68.142.212.123
www.mydomain.com. 600 IN CNAME ghs.google.com.
p10w2.geo.mud.yahoo.com (68.142.212.118)
68.142.192.0 - 68.142.255.255
Inktomi Corporation
The "68.142.212.nnn" series of DNS servers are the Yahoo equivalent of Google Apps. A Yahoo registered domain, in the Yahoo world, gets the same treatment as a Google Apps custom domain, with integrated, online accessories for the primary domain. But the primary domain goes to the Yahoo servers, instead of to the Google Apps servers.
And, when an anxious blogger selects "Redirect mydomain.com to www.mydomain.com.", and gets a well known (and not loved) error
Another blog is already hosted at this addressand the DNS setup involves Yahoo as the registrar, that is why. Recycling the domain settings, in Google Apps, won't solve this problem.
Right now, we have no experience with making a Blogger blog, published to the primary domain, work properly when Yahoo DNS is involved. It appears that the best solution, in this case, is to get a third party DNS service that supports "CNAME" referral, and avoid Yahoo DNS altogether.
>> Top
Comments