mydomain.com. 3593 IN A 184.108.40.206
www.mydomain.com. 3600 IN CNAME mydomain.com.
220.127.116.11 - 18.104.22.168
The blogger reporting a problem states
I tried publishing back on blogger and then back to my custom domain but no change.which, to me, suggests that our old friend
Another blog is already hosted at this addressmay not be part of this scenario. Typically when "Another blog is already hosted at this address." is seen, it's when trying to re publish to the custom domain address.
The problem of domains redirecting to a parking server, owned and operated by the registrar, has been with us for a while. Generally we see it when a blogger, who has yet to learn of the special needs of custom domains, buys a domain from a registrar, starts right into "Advanced Settings", and tries to publish the blog to the domain. Here we generally see
Another blog is already hosted at this addressbecause the domain DNS does not yet point to Google.
With this case, we see no such error. Just a non accessible blog, and another old friend
Server Not Found
And, the blogger further claims
Bought it right on Blogger, through Google.which implies, to me, a DNS setup by Google Apps. The wording of that statement makes me think of a blogger who doesn't know of the difference between DNA and DNS. It's certainly not from a blogger who would covertly edit the standard Asymmetrical setup, into the broken setup above.