Another blog is already hosted at this address

That's the old well known monolithic error, seen when you try to publish your blog to a Google Custom Domain, and possibly later too, when you try to setup the "www" alias of the blog to point to the root.

The literal reason for this error is that the Custom Domain setup wizard validates the DNS setup for the custom domain to which you're trying to publish. If the wizard sees that your prospective custom domain does not point to "ghs.google.com", it gives you that error, instead of publishing the blog there.

There are basically 3 scenarios which may result in this error.

1. Bad DNS: DNS for the URL provided does NOT point to Google ("ghs.google.com").
2. The literal meaning: DNS points to Google, but the URL is in use (another blog has been published to that URL).
3. The most common meaning: The Blogger database entry for your domain is corrupt, and has to be reset. You typically do that, using Google Apps.

So, you have to research why the wizard isn't seeing the DNS referral that you presumably setup.

• In some cases, you may have made a mistake in the DNS setup. Verify your DNS setup, before trying to blame Blogger.
• In other cases, the problem is a bug in the Blogger database, or maybe in the "ghs.google.com" database itself.
• If your custom domain was setup before October 2008, it's possible that you may be able to fix the problem, using Google Apps, by recycling the domain settings. In some cases, this will work even for those not currently using Google Apps. In normal life, these steps would negate each other, and all would be a waste of time. This isn't normal life, so don't omit any steps, however silly it all appears.
  1. If you're not registered for Google Apps, you'll have to register. If you just purchased your custom domain, using the "Buy A Domain For Your Blog" wizard, you're going to have to find your registration information and login to Google Apps.
     • When you login, you will be at the Google Apps Dashboard. If you're logged in using an account with administrative authority, you'll have the links that you need, there in front of you.
     • The Web Pages service is disabled and enabled from the "Service settings" pull down menu in the upper right, or from the "Web Pages" link on the Google Apps desktop. If there's no selection in the pull down menu, and no icon / link on the desktop, click on the "Add more services" link, then on the next screen click on the "Add it now" button for Web Pages.
     • Google Apps pages are created from the "Web Pages" link in the lower left, then the Service setup "Edit your web pages" link.
  2. If the Web Pages service in Google apps is currently enabled, disable it.
  3. Enable the Web Pages service, and set it to publish to the "www" alias.
  4. Create, then Publish a Google Apps page, using Google Page Creator.
  5. Again disable the Web Pages service.
  6. If you want to use the Web Pages service, re enable it.
  In recent cases, some newly setup custom domains have one of the Apps activated, and set to publish to the "www" alias. You'll want to execute Step 2, for that App. If you can wait 30 to 60 minutes after Step 2, you may be able to eliminate Steps 3 - 5.
• Blogger has provided a new problem reporting tool, that lets them fix the problems similar to those resolved by Google Apps, using the Magical Custom Domain Form. This requires manual human intervention, so don't anticipate immediate resolution of the problem.
• If that doesn't work either, use Blogger Contact, and let them know of the problem.

(Update 2008/10/12): Pages was deprecated recently, and replaced by Sites. Newer domains, setup in Google Apps, may not have Pages available. You may have to use Sites, or Start Page, and configure that to publish to your "www" alias. Until Blogger develops a more efficient domain resetting tool, we may have to improvise. Any results, positive or negative, that you wish to share will be included here, and may help others.

>> Top