Another blog or Google Site is already using this address.
The most frequently seen solution to this problem, contrary to the opinions expressed in some blogs and websites, starts with correction of the domain DNS addresses. But even after careful DNS address correction, some blog owners still report the well known "Another blog ..." error.
Maybe 99.99% of the custom domain published blogs use what I call an asymmetrical DNS address configuration.
mydomain.com. 3600 IN A 184.108.40.206Note the restriction with the asymmetrical configuration, sometimes overlooked.
mydomain.com. 3600 IN A 220.127.116.11
mydomain.com. 3600 IN A 18.104.22.168
mydomain.com. 3600 IN A 22.214.171.124
www.mydomain.com. 3600 IN CNAME ghs.google.com.
With an asymmetrical configuration, you may not publish to the domain root. Your only valid choice is to publish to "www.mydomain.com", and select "Redirect mydomain.com to www.mydomain.com". If you publish to "mydomain.com", you will eventually seeBlogs may not be hosted at naked domains.or maybe a well known monolithic errorAnother blog or Google Site is already using this address.
The conclusion is simple. Unless you intentionally created a symmetrical or non root virtual host address configuration, always publish to the "www" host. And, even though you do publish to the "www" host, understand that righteous addressing of the domain root is a necessity - not an option.