Research Custom Domain Problems From The Foremost Of The Purchase

Sometimes, researching a problem, alongside a custom domain published blog, involves a Who Is lookup, to hit upwards one's hear fundamental domain details - similar DNS server namess, buy date, registrar name, too others. Starting alongside the properly spelled domain cite is essential, to getting a useful Who Is lookup. In cases where the weblog / domain possessor can't piece the domain cite consistently, you lot tin sack kickoff fifty-fifty to a greater extent than basically.

To hit upwards one's hear the details nearly a domain purchase, when you lot convey whatever doubt, inquire for a re-create of the account or receipt. If the transaction was conducted electronically, re-create too glue of the fundamental data is most useful. If the transaction involved a newspaper trail, convey the receipt scanned, too a motion painting posted somewhere that you lot tin sack view.

The account or receipt, for whatever domain purchase, volition deal position - too confirm or deny - fundamental details.

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

All of these details are useful, inward researching a employment alongside a custom domain published blog.

Starting alongside the domain name, verified from the account or receipt, you lot tin sack purpose whatever of several similar Who Is lookup tools.

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

Having multiple complementary tools tin sack survive useful, many times - both every bit backup (in illustration i is offline, for or too then reason) - too to confirm or deny unexpected results.

>> Top

Custom Domain Diagnoses - Put Dns Address Inconsistencies

One of the to a greater extent than intriguing causes of intermittent custom domain problems starts amongst inconsistent DNS server configuration. Recently, eNom, i of the "partners" inwards "Buy a domain", has been serving inconsistent DNS configurations, from fourth dimension to fourth dimension - including i rattling blatant episode the afternoon of 6/18/2012, which was reported past times several dozen angry weblog owners.

Detecting, in addition to diagnosing, the inconsistencies is typically a complicated process.

1. Identify the domain authorization servers, typically using a Who Is lookup.
2. Dig each domain address (typically "naked domain" in addition to "www" aliases), from each of the identified domain authorization servers.
3. Extract in addition to aggregate each Dig log.
4. Compare aggregated Dig snippets.

This was non a project for the faint of heart, or tech challenged, weblog owner.

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

The Dig Web Interface, nevertheless roughly other gratis online tool, provides us the mightiness to diagnose inconsistent DNS servers - such every bit the work eNom seems to have, inwards a thirty bit transaction.

1. Provide the "naked domain" in addition to "www" aliases.
2. Select "A" for "Type" ("A" / "CNAME" / "NS" lookups).
3. Select "Authoritative" for "Nameservers".
4. Hit "Dig".

Finally, but re-create the log produced, for examination.

It's non a fancy tool, but it does the chore - rattling well. Here, nosotros meet the log for this domain, "nitecruzr.net".

nitecruzr.net@ns11.domaincontrol.com.: nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.36.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.32.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.34.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 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 Influenza A virus subtype H5N1 216.239.36.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.32.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.34.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 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 Influenza A virus subtype H5N1 216.239.36.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.34.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.38.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 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 Influenza A virus subtype H5N1 216.239.36.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.34.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.38.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 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 non complicated, to parse. For each URL, each authorization server is identified, in addition to Dug. In the representative of this domain, hosted on GoDaddy, nosotros meet each URL, Dug from each of four authorization servers, i past times one.

If a DNS inconsistency existed, the inwards a higher house log would exhibit the differing DNS addresses - such every bit eNom hosted domains show, from fourth dimension to time. Given this tool, it may endure easier to await for DNS inconsistencies, when problems amongst custom domains are reported, inwards Blogger Help Forum: Something Is Broken.

>> Top