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

Arnold A. 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
Nitecruzr 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

Add A Custom Redirect, If You Change A Post URL

When you rename a blog, the most that you can do, to keep the old URL useful, is to setup a stub post , with a clickable link to the new URL. Yo! The blog is now at xxxxxxx.blogspot.com!! Blogger forbids gateway blogs, and similar blog to blog redirections . When you rename a post, you can setup a custom redirect - and automatically redirect your readers to the post, under its new URL. You should take advantage of this option, if you change a post URL.

Jump Break Is Visible Only In An Index Page

Some blog owners are unsure what a Jump Break looks like, when applied to their blogs. Occasionally, in Blogger Help Forum: Get Help with an Issue , we see the confusion. Where's the Jump Break? or I added a Jump Break to several posts, but it never shows up! When asked for a screen print of what they're seeing, they may provide a image of the post, in the Post Editor Preview window - or possibly, the published post, but in post page view.

Leave Comments Here

Like any blogger, I appreciate polite comments, when they are relevant to the blog, and posted to the relevant article in the right blog . If you want to ask me a question thats relevant to blogging, but you can't find the right post to start with (I haven't written about everything blogger related, yet, nor the way things are going I don't expect to either), ask your questions here, or leave an entry in my guestbook . As noted above, please note my commenting policy . If you post a comment to this post , I will probably treat it as a "Contact Me" post . If you have an issue that's relevant to any technical issue in the blog, please leave a comment on the specific post , not here. This post is for general comments, and for non posted contact to me. If the form below does not work for you, check your third party cookies setting! For actual technical issues, note that peer support in Blogger Help Forum: Something Is Broken , or Nitecruzr Dot Net - Bloggin...