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, "nitecruzr.net".

nitecruzr.net@ns11.domaincontrol.com.:
nitecruzr.net.  3600 IN A 216.239.36.21
nitecruzr.net.  3600 IN A 216.239.32.21
nitecruzr.net.  3600 IN A 216.239.34.21
nitecruzr.net.  3600 IN A 216.239.38.21
nitecruzr.net.  3600 IN NS ns54.domaincontrol.com.
nitecruzr.net.  3600 IN NS ns53.domaincontrol.com.
nitecruzr.net.  3600 IN NS ns12.domaincontrol.com.
nitecruzr.net.  3600 IN NS ns11.domaincontrol.com.


nitecruzr.net@ns12.domaincontrol.com.:
nitecruzr.net.  3600 IN A 216.239.36.21
nitecruzr.net.  3600 IN A 216.239.32.21
nitecruzr.net.  3600 IN A 216.239.34.21
nitecruzr.net.  3600 IN A 216.239.38.21
nitecruzr.net.  3600 IN NS ns54.domaincontrol.com.
nitecruzr.net.  3600 IN NS ns53.domaincontrol.com.
nitecruzr.net.  3600 IN NS ns12.domaincontrol.com.
nitecruzr.net.  3600 IN NS ns11.domaincontrol.com.


nitecruzr.net@ns53.domaincontrol.com.:
nitecruzr.net.  3600 IN A 216.239.36.21
nitecruzr.net.  3600 IN A 216.239.34.21
nitecruzr.net.  3600 IN A 216.239.38.21
nitecruzr.net.  3600 IN A 216.239.32.21
nitecruzr.net.  3600 IN NS ns54.domaincontrol.com.
nitecruzr.net.  3600 IN NS ns53.domaincontrol.com.
nitecruzr.net.  3600 IN NS ns12.domaincontrol.com.
nitecruzr.net.  3600 IN NS ns11.domaincontrol.com.


nitecruzr.net@ns54.domaincontrol.com.:
nitecruzr.net.  3600 IN A 216.239.36.21
nitecruzr.net.  3600 IN A 216.239.34.21
nitecruzr.net.  3600 IN A 216.239.38.21
nitecruzr.net.  3600 IN A 216.239.32.21
nitecruzr.net.  3600 IN NS ns54.domaincontrol.com.
nitecruzr.net.  3600 IN NS ns53.domaincontrol.com.
nitecruzr.net.  3600 IN NS ns12.domaincontrol.com.
nitecruzr.net.  3600 IN NS ns11.domaincontrol.com.


www.nitecruzr.net@ns11.domaincontrol.com.:
www.nitecruzr.net. 3600 IN CNAME ghs.google.com.


www.nitecruzr.net@ns12.domaincontrol.com.:
www.nitecruzr.net. 3600 IN CNAME ghs.google.com.


www.nitecruzr.net@ns53.domaincontrol.com.:
www.nitecruzr.net. 3600 IN CNAME ghs.google.com.


www.nitecruzr.net@ns54.domaincontrol.com.:
www.nitecruzr.net. 3600 IN CNAME ghs.google.com.

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

Research Custom Domain Problems From The Beginning Of The Purchase

Sometimes, researching a problem, with a custom domain published blog, involves a Who Is lookup, to determine key domain details - like DNS server namess, purchase date, registrar name, and others. Starting with the properly spelled domain name is essential, to getting a useful Who Is lookup. In cases where the blog / domain owner can't spell the domain name consistently, you can start even more basically.

To determine the details about a domain purchase, when you have any doubt, ask for a copy of the invoice or receipt. If the transaction was conducted electronically, copy and paste of the key information is most useful. If the transaction involved a paper trail, have the receipt scanned, and a picture posted somewhere that you can view.

The invoice or receipt, for any domain purchase, will help identify - and confirm or deny - key details.

• Correct domain name - spelling.
• Purchase date.
• Name of registrar.

All of these details are useful, in researching a problem with a custom domain published blog.

Starting with the domain name, verified from the invoice or receipt, you can use any of several similar Who Is lookup tools.

• DomainTools.
• MXToolbox.
• Name ("who.is").
• Network-Tools.

Having multiple complementary tools can be useful, many times - both as backup (in case one is offline, for some reason) - and to confirm or deny unexpected results.

>> Top