Skip to main content

Another blog is already hosted at this address - January 2009

Recently, a variant on the well known custom domain setup problem, "Another blog is already hosted at this address" has been seen in newly setup custom domains.

A (excerpted) Dig extract, for the domain in question shows no problem. Maybe, the standard Asymmetrical DNS Configuration (aka Google Apps configuration).

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. 1800 IN CNAME ghs.google.com.
---
ghs.google.com. 465476 IN CNAME ghs.l.google.com.
ghs.l.google.com. 300 IN A 74.125.43.121

alternately, the standard Symmetrical DNS Configuration

mydomain.com. 1800 IN CNAME ghs.google.com.
www.mydomain.com. 1800 IN CNAME ghs.google.com.
---
ghs.google.com. 465476 IN CNAME ghs.l.google.com.
ghs.l.google.com. 300 IN A 74.125.43.121

Even with the standard DNS configuration, we still have the problem
Another blog is already hosted at this address.


An HTTP trace shows us the cause of the problem.

Sending request:

GET / HTTP/1.1
Host: mydomain.com
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 = 216.239.36.21
• 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.com(CR)(LF)

Sending request:

GET / HTTP/1.1
Host: www.mydomain.com
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)
Content-Type:·text/html;·charset=UTF-8(CR)(LF)
Location:·http://sites.google.com/a/mydomain.com/sites/system/app/pages/meta/domainWelcome(CR)(LF)


In this case, you'll need to disable the Sites service. You'll have to start by getting access to Google Apps. Then use the URL "www.google.com/a/cpanel/mydomain.com/SitesSettings", and disable Sites. (As always, substitute the actual domain URL for "mydomain.com").

A similar HTTP trace:

Sending request:

GET / HTTP/1.1
Host: mydomain.com
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 = 216.239.36.21
• 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.com(CR)(LF)

Sending request:

GET / HTTP/1.1
Host: www.mydomain.com
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)
Content-Type:·text/html;·charset=UTF-8(CR)(LF)
Location:·http://start.mydomain.com(CR)(LF)

The Start Page service is similar to Sites, except it has to be reset directly within Google Apps. As above, start by getting access to Google Apps.

>> Top

Comments

Alan A said…
Hi Chuck,

I have been reading up on DNS, www or not www, 301 redirects, set preferred domain, etc. for a couple of months & my brain fried! I still don't quite know how to handle a couple of things. I hope you can help. I purchased my domain w/ Google a couple months ago & my DNS settings appear as above. Setting up my custom domain in Blogger, I had to use www.mydomain.com as the main address & mydomain.com is being forwarded to the www URL. I don't believe there was a choice. I would get the "nother blog is published" error if I used mydomain.com as the primary. Yet my DNS settings have www a CNAME & @ as the A records as in your example above. Is this set-up ok? Is everything routed properly? And, in following your directions to set up a site map, I am now confused about "setting a preferred domain" & doing a 301 redirect. Not sure what to do here despite reading countless posts. Do you make house calls? :) I will be more than happy to post this in forum if that is better for you. Thanks Chuck!
Chuck said…
Alan,

You have a lot of questions there. Yes, I think that either GBH: Something Is Broken, or in Nitecruzr Dot Net - Blogging would be better choices.

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.