Skip to main content

Custom Domains, and a Second Typical "404 Not Found"

Sometimes, even with a properly setup custom domain, you (or your readers) may encounter a well known problem
Server Not Found

Error 404
I wrote about this earlier, about a symptom that has no obvious cause.

Sometimes, the well known "Server Not Found Error 404" symptom has a cause, but you may have to look carefully to find it. Many times, you find no clue in the DNS addresses. This is a normal (asymmetrical) DNS address configuration.
mydomain.net.            3600    IN      A       216.239.32.21
mydomain.net.            3600    IN      A       216.239.34.21
mydomain.net.            3600    IN      A       216.239.36.21
mydomain.net.            3600    IN      A       216.239.38.21
www.mydomain.net.      3600    IN      CNAME   ghs.google.com.
---
ghs.google.com.         282206  IN      CNAME   ghs.l.google.com.
ghs.l.google.com.       300     IN      A       74.125.43.121 


Here, an (abbreviated) HTTP trace will give you a clue.

Sending request:

GET / HTTP/1.1
Host: mydomain.net
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:
1.9.0.5) Gecko/2008120122 Firefox/3.0.5
Connection: close

• Finding host IP address...
• Host IP address = 209.85.171.121
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...

Receiving Header:

HTTP/1.1·302·Moved·Temporarily(CR)(LF)
Location:·http://www.mydomain.net(CR)(LF)

Sending request:

GET / HTTP/1.1
Host: www.mydomain.net
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:
1.9.0.5) Gecko/2008120122 Firefox/3.0.5
Connection: close

• Finding host IP address...
• Host IP address = 209.85.171.121
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...

Receiving Header:

HTTP/1.1·302·Moved·Temporarily(CR)(LF)
Location:·http://start.mydomain.net(CR)(LF)

Unlike the previously noted "Server Not Found Error 404" symptom, this one won't be solved by merely publishing back to Blog*Spot, then re publishing to the custom domain.

What we see here is that the Start Page service in Google Apps is apparently enabled, and published to "www.mydomain.net". In this case, you're going to first have to disable Start Page. If you don't, you're going to see another old friend
Another blog is already hosted at this address.
After doing that, then you can publish back to Blog*Spot, then re publish to the custom domain.

Similar to the Start Page redirect, you may on occasion see a redirect to the Google Sites service.

>> Top

Comments

Fru Kaos said…
My blog: www.annaskaos.blogspot.com

Many thanks for the information.

Do you think you can help me to find the problem by looking on the printed screen on my blog?

http://annaskaos.blogspot.com/2009/02/detta-suger.html

Use Firefox ;-)

Many thanks!

Anna
Chuck said…
Anna,

Technical conversations like what you need are much better conducted from GBH: Something Is Broken, or in Nitecruzr Dot Net - Blogging.

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.