Skip to main content

Custom Domain Diagnoses - Identify DNS Address Inconsistencies

One of the more intriguing causes of intermittent custom domain problems starts with inconsistent DNS server configuration. Recently, eNom, one of the "partners" in "Buy a domain", has been serving inconsistent DNS configurations, from time to time - including one very blatant episode the afternoon of 6/18/2012, which was reported by several dozen angry blog owners.

Detecting, and diagnosing, the inconsistencies is typically a complicated process.
  1. Identify the domain authority servers, typically using a Who Is lookup.
  2. Dig each domain address (typically "naked domain" and "www" aliases), from each of the identified domain authority servers.
  3. Extract and aggregate each Dig log.
  4. Compare aggregated Dig snippets.
This was not a task for the faint of heart, or tech challenged, blog owner.

Recently, I was given a handy tool which does all of this, in one quick GUI transaction.

The Dig Web Interface, yet another free online tool, provides us the ability to diagnose inconsistent DNS servers - such as the problem eNom seems to have, in a 30 second transaction.
  1. Provide the "naked domain" and "www" aliases.
  2. Select "A" for "Type" ("A" / "CNAME" / "NS" lookups).
  3. Select "Authoritative" for "Nameservers".
  4. Hit "Dig".
Finally, just copy the log produced, for examination.

It's not a fancy tool, but it does the job - very well. Here, we see the log for this domain, "".  3600 IN A  3600 IN A  3600 IN A  3600 IN A  3600 IN NS  3600 IN NS  3600 IN NS  3600 IN NS 3600 IN A 3600 IN A 3600 IN A 3600 IN A 3600 IN NS 3600 IN NS 3600 IN NS 3600 IN NS 3600 IN A 3600 IN A 3600 IN A 3600 IN A 3600 IN NS 3600 IN NS 3600 IN NS 3600 IN NS 3600 IN A 3600 IN A 3600 IN A 3600 IN A 3600 IN NS 3600 IN NS 3600 IN NS 3600 IN NS 3600 IN CNAME 3600 IN CNAME 3600 IN CNAME 3600 IN CNAME
The log is not complicated, to parse. For each URL, each authority server is identified, and Dug. In the case of this domain, hosted on GoDaddy, we see each URL, Dug from each of 4 authority servers, one by one.

If a DNS inconsistency existed, the above log would show the differing DNS addresses - such as eNom hosted domains show, from time to time. Given this tool, it may be easier to look for DNS inconsistencies, when problems with custom domains are reported, in Blogger Help Forum: Something Is Broken.

>> Top


Tim Cumper said…
A very useful tool.
I have tried it with & (a new blogger blog set up specifically for this recently - but getting a 404 message) - I notice that the report only contains one line of IP -
as distinct from the four lines which appear in your example (& are part of the instructions from Google.)
However - I have recently set up - which brings precisely the same results - but is successfully appearing online at the URL.
Are the four, separate IPs required - is it some sort of redundancy safeguard?
Chuck Croll said…

You only need one "A" record - if and ONLY if you are prepared to see your domain offline, when that one server is offline - as in what happened last week.

If you care at all for your readers - and their reliable access to your blog, you will always use 4 "A" records.

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 *, or maybe have network configuration or infrastructure problems. You can access or you can access, but you can't access, or

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):

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