Skip to main content

Schizophrenia And Custom Domain URLs

When you setup a Blog*Spot blog, and publish to "", Blogger automatically defines "" and redirects it for you, to "".

This is a traditional convenience for your readers. When custom domains were first developed, they didn't provide the same thoughtfulness - the ability to (optionally) redirect "" to "" (or vice versa) wasn't added, as an option, until much later, and after a lot of pleading by the blogger community.

The great majority of all bloggers consistently select the "Redirect to" option, when setting up their custom domain publishing. It's also possible that Blogger has, maybe not intentionally, enabled that option by default, in some (though maybe not all) custom domain scripts.
I am trying to use the custom domains option to publish my blog but I keep getting the 'Another blog is already hosted at this address' error.

Investigation of the current DNS setup shows us, as summarised in an excerpted Dig log: 3600 IN CNAME

or  3600 IN A  3600 IN A

or maybe 3600 IN CNAME

rather than the more traditional (and complete) configurations, as described in Your Blog, Custom Domains, And Righteous Solutions. Having a domain with only half of the DNS address defined produces the same result as a domain with only half of the DNS address properly defined. You will, eventually, see our old friend

Another blog is already hosted at this address.

Unlike the normal redirection of "" to "", redirection of "" to "" requires the DNS definitions, as shown above. Blogger doesn't provide these settings - you (or your DNS host) do. Without both settings (the above provided intentionally, or by mistake), you should expect to see

Another blog is already hosted at this address.

Why not offer both URLs to your readers? If it solves your personal experience of

Another blog is already hosted at this address.

so much the better - for both you and your readers. Take a look at Your Blog, Custom Domains, And Righteous Solutions for the correct DNS configurations, for detailed, up to date configuration information.

Having changed your DNS to use "A" / "CNAME" referrals for both URLs, remember to publish back to BlogSpot, then republish to your "www" alias, to ensure a clean repair of the problem.

And finally, having made the above improvements in your domain DNS setup, you may still need to select the Redirect option. You'll have only 2 choices here - select or don't select. You'll only have one option - for any primary URL, there is one and only one possible secondary URL.

  • If you publish to "", you'll have the option to select "Redirect to".
  • If you publish to "", you'll have the option to select "Redirect to".
  • If you publish to "", you'll have the option to select "Redirect to". (You should have this option - though right now, you do not.)
  • If you publish to "", you'll have the option to select "Redirect to".
  • If you publish to "", don't look for the option to select "Redirect to".
  • If you publish to "", don't look for the option to select "Redirect to".

(Update 12/3): This issue gets odder, with more interesting symptoms.


Harper said…
Hey Chuck,

I've been reading your blog for the past few evenings-- great stuff!

I'm still somewhat of a beginner, and was wondering if you could explain what you mean by the "900 IN" included in your example. ( 900 IN CNAME 900 IN CNAME

I'm battling the dreaded monolithic
"Another blog is already hosted here" Beast.

My DNS is set up correctly,(when I ping it, it returns correctly pointed at google)but I am still getting the "old friend" message.

Also, do you offer personalized service for a fee?

Thank you- I appreciate your time,
Harper (my custom domain is ironswan dot com)
ahardslojdlife said…
Hey, I started here and somewhere along the way I got my custom domain to work. Thanks! I got both the 404 message and the message that there is already a blog on that domain. I did a dig log (which I have never done) and it turned out my CNAME was ok. I had to disable the custom domain and enable it again. (I read your commenting policy, I hope I didn´t break it now!)

Best regards and thanks for helping out!
oldmilwaukee said…
Thank you for the information that enabled me to get my custom domain working. Publishing once more to blogspot and then going back to custom domain publishing fixed everything! So simple. Thanks!!!

Popular posts from this blog

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.

Help! I Can't See My Blog!

I just posted to my blog, so I know that it's there. I can tell others are looking at it. But I can't see it.

Well, the good news is you don't have a blog hijack or other calamity. Your blog is not gone.

Apparently, some ISPs are blocking *, or maybe have network configuration or infrastructure problems. You can access or you can access, but you can't access, or

You can't access them directly, that is. If you can access any free, anonymous proxy servers, though, you may be able to access your blog.

Note: You can use PKBlogs with the URL pre packaged. Here is the address of this post (with gratuitous line breaks to prevent the old post sidebar alignment problem):

And an additional URL, to provide to those suffering from this problem, would be the WordPress version of this post: