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!
Thomas Massie 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

Embedded Comments And Main Page View

The option to display comments, embedded below the post, was made a blog option relatively recently. This was a long requested feature - and many bloggers added it to their blogs, as soon as the option was presented to us. Some blog owners like this feature so much, that they request it to be visible when the blog is opened, in main page view. I would like all comments, and the comment form, to be shown underneath the relevant post, automatically, for everyone to read without clicking on the number of comments link. And this is not how embedded comments work.

What's The URL Of My Blog?

We see the plea for help, periodically I need the URL of my blog, so I can give it to my friends. Help! Who's buried in Grant's Tomb, after all? No Chuck, be polite. OK, OK. The title of this blog is "The Real Blogger Status", and the title of this post is "What's The URL Of My Blog?".

With Following, Anonymous Followers Can't Be Blocked

As people become used to Blogger Following as just another tool to connect people, they start to think about the implications . And we see questions like How do I block someone who's been following my blog secretly? I couldn't see her in my Followers list (hence I couldn't use the "Block this user" link), but I have looked at her profile and could see that she's Following my blog. Following, when you look at the bottom line, is no more than a feed subscription and an icon (possibly) displayed on your blog, and linking back to the profile of the Follower in question. If someone Follows your blog anonymously, all that they get is a subscription to the blog feed. If you publish a feed from your blog, and if the feed is open to anybody (which, right now, is the case ), then it's open to everybody. If someone wants to use Following to subscribe to the feed, you can't stop this. You can't block it before, or after, the fact. You can't Block w