Skip to main content

Diagnosing Problems With Custom Domains - Case Study #10

Recently, we've had a few custom domain problem reports in Blogger Help Forum which start with the usual generic problem report
I'm getting "404 Not Found".
or
OK, here's another case of "Another blog is already hosted at this address."
and when we look at an excerpted Dig log, we see an odd setup.

mydomain.com. 3600 IN A 66.98.145.18
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. 3600 IN A 66.98.145.18

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

mercury.orderbox-domainforward.com (66.98.145.18)
66.98.128.0 - 66.98.255.255
ThePlanet.com Internet Services, Inc.


Looking at the server "66.98.145.18", chances are that it's some sort of forwarding server. But why are the bloggers in question so careful to retain the existing forwarding server, then add the Google Apps servers and / or "ghs.google.com"?

Obviously, and to repeat myself yet again, the correct setup is

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


And, another.

mydomain.com. 1800 IN A 68.178.232.100
mydomain.com. 1800 IN A 216.239.32.21
mydomain.com. 1800 IN A 216.239.34.21
mydomain.com. 1800 IN A 216.239.36.21
mydomain.com. 1800 IN A 216.239.38.21
www.mydomain.com. 3600 IN CNAME ghs.google.com.

parkwebwin-v01.prod.mesa1.secureserver.net (68.178.232.100)
68.178.128.0 - 68.178.255.255
GoDaddy.com, Inc.


Another reference to the GoDaddy parked server. The registrars like GoDaddy call this "user friendly 404 display". Some network / security experts call it "404 hijacking".

The frustrating thing about "66.98.145.18" or "68.178.232.100" is that it won't necessarily cause an immediate failure. If any one of the 4 of the right servers come up in the resolution sequence first, you'll not have a problem. But one day, "66.98.145.18", "68.178.232.100", or whatever bogie is configured in your bogus solution will be tried. If you're lucky, you'll simply hear
Your domain is "404" again!
If you're not, you'll be seeing
Another blog is already hosted at this address.


>> Top

Comments

Owner said…
Help me. I am having a problem using Go Daddy's Domain. If I am going to visit my site which is www.arnoldarieta.com it is redirecting to blogger but when I removed the www. , I always have a Page Not Found page of Go Daddy??? Help me. Email me please
Chuck said…
Owner,

This may be a problem that you can solve, on your own.

If you're unable or unwilling to troubleshoot the problem, this is where I urge you to post in Blogger Help Forum: Something Is Broken, or in Nitecruzr Dot Net - Blogging, for peer support.

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.