Skip to main content

Custom Domain DNS Addresses And Name Addressing Conventions

Periodically, when reviewing the many problem reports about Google Custom Domains, and especially those reporting the ubiquitous "Another blog ..." error message, we'll look at the DNS configuration and see a partial DNS setup
www.mydomain.com. 900 IN CNAME ghs.google.com.

yet the blogger reporting the problem states
I setup my domain with both the root, and the "www" alias, defined. This is what I setup! Whatever can the problem be?

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. 900 IN CNAME ghs.google.com.

We look deeper, and find not the above, but
mydomain.com.mydomain.com.  3600 IN A 216.239.32.21
mydomain.com.mydomain.com.  3600 IN A 216.239.34.21
mydomain.com.mydomain.com.  3600 IN A 216.239.36.21
mydomain.com.mydomain.com.  3600 IN A 216.239.38.21
www.mydomain.com. 900 IN CNAME ghs.google.com.

or maybe
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.mydomain.com. 900 IN CNAME ghs.google.com.

SAY WHAT?

This is a typical problem with many GUI Domain Managers, where "mydomain.com" is already known to the wizard (look at the top of the Domain Manager display). When you specify a "CNAME" for "www.mydomain.com", in the "CNAMES (Aliases)" entry, you don't specify "www.mydomain.com", you simply specify "www". Specifying "www.mydomain.com" for "CNAMES (Aliases)" results in
www.mydomain.com.mydomain.com. 900 IN CNAME ghs.google.com.

Similarly, specifying "mydomain.com" for "A (Host)" results in
mydomain.com.mydomain.com. 900 IN CNAME ghs.google.com.

This will not always be the case, unfortunately. Some DNS Manager wizards automatically extract redundant "mydomain.com" phrases from the "A (Host)" and "CNAMES (Aliases)" entries. Others, like GoDaddy, do not.

For GoDaddy and some (not all) similar wizards
  • To designate "mydomain.com": Enter "@" (that's a Shift-2, on most keyboards), under "A (Host)".
  • To designate "www.mydomain.com": Enter "www", under "CNAMES (Aliases)".

If you have a third party DNS Host (not eNom or GoDaddy), you are responsible for finding out how they signify the domain root, when entering the "A (Host)" and "CNAMES (Aliases)" records. Try and prevent
mydomain.com.mydomain.com.  3600 IN A 216.239.32.21
mydomain.com.mydomain.com.  3600 IN A 216.239.34.21
mydomain.com.mydomain.com.  3600 IN A 216.239.36.21
mydomain.com.mydomain.com.  3600 IN A 216.239.38.21
www.mydomain.com. 900 IN CNAME ghs.google.com.

or
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.mydomain.com. 900 IN CNAME ghs.google.com.

and eliminate one possible cause for the "Another blog ..." error.

Comments

Popular posts from this blog

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.

Help! I Can't See My Blog!

I just posted to my blog, so I know that it's there. I can tell others are looking at it. But I can't see it.

Well, the good news is you don't have a blog hijack or other calamity. Your blog is not gone.

Apparently, some ISPs are blocking *.blogspot.com, or maybe have network configuration or infrastructure problems. You can access Blogger.com or you can access Blogspot.com, but you can't access nitecruzr.blogspot.com, or bloggerstatusforreal.blogspot.com.

You can't access them directly, that is. If you can access any free, anonymous proxy servers, though, you may be able to access your blog.

Note: You can use PKBlogs with the URL pre packaged. Here is the address of this post (with gratuitous line breaks to prevent the old post sidebar alignment problem):
http://www.pkblogs.com/bloggerstatusforreal.blogspot.com/
2006/07/help-i-cant-see-my-blog.html


And an additional URL, to provide to those suffering from this problem, would be the WordPress version of this post:
ht…