Skip to main content

eNom Hosted Custom Domains Again Showing Intermittent Connectivity Issues

This week, we have a few reports in Blogger Help Forum: Something Is Broken, about active and mature domains, suddenly stopped working.
I have used my domain with no problems, since last year. Today, it suddenly stopped working, and the browser reports
Oops! Google Chrome could not find www.mydomain.com.
I asked my friends about my domain - and they tell me that my blog is inaccessible to them, also. I didn't change any settings - and it was fine, until last night.

As we reported last year, the Google partner registrar eNom occasionally has a problem with their DNS server complement. Right now, one of their DNS servers appears consistently bad.

Using a comprehensive Dig tool, we can observe a given domain, and compare the DNS addresses being served by all authoritative name servers for a given domain, in a single transaction.

Here's a hypothetical example, of what we're seeing right now, for several eNom hosted domains.
mycustomdomain.com@dns1.name-services.com.:

mycustomdomain.com.  1800 IN A 216.239.36.21
mycustomdomain.com.  1800 IN A 216.239.34.21
mycustomdomain.com.  1800 IN A 216.239.38.21
mycustomdomain.com.  1800 IN A 216.239.32.21

mycustomdomain.com@dns2.name-services.com.:

mycustomdomain.com.  1800 IN A 216.239.36.21
mycustomdomain.com.  1800 IN A 216.239.34.21
mycustomdomain.com.  1800 IN A 216.239.32.21
mycustomdomain.com.  1800 IN A 216.239.38.21

mycustomdomain.com@dns3.name-services.com.:

mycustomdomain.com.  1800 IN A 216.239.36.21
mycustomdomain.com.  1800 IN A 216.239.32.21
mycustomdomain.com.  1800 IN A 216.239.34.21
mycustomdomain.com.  1800 IN A 216.239.38.21

mycustomdomain.com@dns4.name-services.com.:

mycustomdomain.com.  1800 IN A 216.239.36.21
mycustomdomain.com.  1800 IN A 216.239.34.21
mycustomdomain.com.  1800 IN A 216.239.32.21
mycustomdomain.com.  1800 IN A 216.239.38.21

mycustomdomain.com@dns5.name-services.com.:

org.   3601 IN
 SOA dns1.name-services.com. info.name-services.com. 2010 10800 3600 604800 3600


www.mycustomdomain.com@dns1.name-services.com.:

www.mycustomdomain.com.  1800 IN CNAME ghs.google.com.

www.mycustomdomain.com@dns2.name-services.com.:

www.mycustomdomain.com.  1800 IN CNAME ghs.google.com.

www.mycustomdomain.com@dns3.name-services.com.:

www.mycustomdomain.com.  1800 IN CNAME ghs.google.com.

www.mycustomdomain.com@dns4.name-services.com.:

www.mycustomdomain.com.  1800 IN CNAME ghs.google.com.

www.mycustomdomain.com@dns5.name-services.com.:

org.   3601 IN
 SOA dns1.name-services.com. info.name-services.com. 2010 10800 3600 604800 3600
Right now, it appears that server "dns5" is consistently broken.

It's possible that this problem will affect more eNom customers, as the day progresses, cached DNS addresses expire, and readers of various eNom hosted domains request DNS addresses. I hope that eNom Customer Service can react to this problem more promptly than they have reacted to the immediately previous problem.

Watch for eNom acknowledged changes and problems.

Comments

Popular posts from this blog

Custom Domain Migration - Managing The Traffic

Your blog depends upon traffic for its success.

Anything that affects the traffic to your blog, such as any change in the URL, affects the success of your blog. Publishing the blog to a custom domain, like renaming the blog, will affect traffic to your blog. The effects of the change will vary from blog to blog, because of the different traffic to every different blog.Followers. People who find your blog because of recommendations by other people.Search engines. Robotic processes which methodically surf your blog, and provide dynamic indexing to people who search for information.Subscribers. People who read your content from their newsfeed reader, such as the dashboard Reading List.Viewers. People who read your content from their browser.No two blogs are the same - and no two blogs will have the same combinations of traffic sources.

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.