Not Foundor its equivalent in another browser
Were you looking for: My Custom Domain?
When that happens, there's just one way to recover, and that involves repeating the previous setup.
- If you haven't done so already, and if you're able to do so, check and correct your DNS setup.
- If you just removed or edited a DNS entry, examine the TTL value of the entry that you removed or edited. To improve your chances of getting through this without seeing "Another blog ...", do nothing during the TTL period, while you wait, to know that your new settings are visible from Google!
- Publish the blog back to "myblog.blogspot.com". You can't repeat the previous setup, without first removing the (incomplete or incorrect) previous setup.
- Publish the blog, again, to "www.mycustomdomain.com", using the "Advanced Settings" wizard. This repeats the previous setup, hopefully correctly this time.
- If you get the well known "Another blog ..." / "naked domain" error, deal with that.
- If the "404" is not resolved, and you do not get the "Another blog ..." / "naked domain" error, repeat from Step 2.
In some cases, you may have to publish back, then forward, several times in succession before this workaround will take effect. You're still looking at maybe 15 minutes of work, much less time than it took me to write this article, and way faster than filling out the Custom Domain Reset Form, and waiting for it to be actioned. Though do not omit Step 2 - better to be safe than sorry. Always allow time for DNS latency.