I need to reuse my domain for my website - but when I try to re publish my blog, I keep seeingAnother blog is already hosted at this address.How can I get my blog back online?
When we look at the domain, and the DNS addresses, we see the domain pointing to the website, already. And this is where many custom domain publishing problems start.
Any time you make any change to a blog, that involves custom domain publishing, the changes will go much more smoothly with the domain properly pointing to the blog. Whether you are setting up a new custom domain publishing, changing a custom domain publishing, or maybe removing a custom domain publishing, the publishing process works much better with the domain properly redirected to the Google database.
One of the causes of the mysterious message
Another blog is already hosted at this addresscomes from the domain not being properly redirected to the Google servers. When the Blogger re publishing process can't continue because the domain DNS addresses are not correct, the process terminates with an error. Whenever any database change terminates with an error, it's always possible that the process may not clean up after itself before ending - and artifacts (aka broken pointers) will be left behind in the database.
The next time that you try to re publish the blog - or when you (or your readers) try to view the blog - you (or they) will see, yet again
Another blog is already hosted at this address.or an alternate
Server Not Found Error 404When that happens, you have only two choices - recycle the domain settings, or submit a domain cleanup request using the Magical Custom Domain form.
Neither of the latter processes are known to be 100% effective. The best way to deal with them is to never deal with them - to not start by causing a problem. That means to always keep the domain DNS addresses righteous, whenever maintaining a custom domain published blog.
If you are going to use your domain for a non Blogger website, always publish your Blogger blog back to BlogSpot, first. Then, verify the status of the blog. Finally, and with no problems discovered, change the DNS addresses.