Blogs may not be hosted at naked domains
Recently, we are starting to see forums reports
Once I changed the A records as mentioned above I changed it back to the blogspot address and then switched back to the custom domain name.
After that was done successfully, it has a box below that says "Redirect mydomain.com to www.mydomain.com". It then states an error "Blogs may not be hosted at naked domains".
It appears that we have now a more descriptive version of the old error "Another blog is already hosted at this address".
If you're seeing this message when publishing to your domain, first and always first, check your DNS addresses. Next, try to use Google Apps, and recycle the domain settings. If recycling in Google Apps doesn't prove effective, you'll need the Custom Domain Reset Form, and patience.
In at least this instance, the message is misleading; as in this case, the blog is supposedly hosted at the "www" alias. The wording of the message is intriguing, too. Which does it really mean
- "No blogs may be published to naked domains" (by policy).
- "This blog may not be published to a naked domain" (because the DNS is wrong, or the Google database is hosed).
I am told by Blogger Support that, by policy, blogs are to be blocked from being published to the domain root ("naked domain") when the domain is purchased through the "Buy A Domain" wizard, or from Google Apps.
This is to prevent unnecessary load on the 4 Google Apps servers, in an asymmetrical DNS configuration, which is not as robust a setup as is the "ghs.google.com" array. We don't know, though, whether this policy is effective when an asymmetrical configuration is used with the "Advanced Settings" wizard, with the domain purchased from a third party registrar.
Besides involving the history of the domain (how it was setup), it's possible that identification of the domain in the URL, as a function of the Top Level Domain in the URL, may be a concern here.