Custom domains, which give us the ability to publish a blog, hosted on a Google server (and using a Layouts template), to a non-BlogSpot URL, are great.
If we don't plan what we're doing, though, sometimes we wind up with a URL that we later decide, just won't suit our long term needs.
Like used underwear, you can't return a used custom domain name. You buy it, you're stuck with it.
Buy another domain, and move on.
Easy enough, if you think about what you're doing.
>> Top
If we don't plan what we're doing, though, sometimes we wind up with a URL that we later decide, just won't suit our long term needs.
Like used underwear, you can't return a used custom domain name. You buy it, you're stuck with it.
Buy another domain, and move on.
- Publish the blog back to its original BlogSpot URL.
- If you have properly setup DNS addresses for your new domain, use "Advanced Settings", and setup the new domain inside Google. If not, buy a new domain, using the "Buy A Domain" wizard.
- If you run into the old "Another blog ..." error, recycle the domain settings using Google Apps.
- Done.
Easy enough, if you think about what you're doing.
>> Top
Comments
This is the "Zone file" for the new domain & it matches the setup instructions in Google.
@ 3600 IN A 216.239.32.21
@ 3600 IN A 216.239.34.21
@ 3600 IN A 216.239.36.21
@ 3600 IN A 216.239.38.21
www 3600 IN CNAME ghs.google.com
j535uwnlqsex 3600 IN CNAME gv-oxihiivmag57ho.dv.googlehosted.com
I know that it takes a while to broadcast the changes, but it seems to me that once the zone file is correct google should be able to verify it.
Is it a problem that the old domain still points to it?
Thanks for your help!
You have to verify it. by adding a verification key to the domain.
http://productforums.google.com/forum/?hl=en&fromgroups=#!category-topic/blogger/something-is-broken/snN0wJzgRmg[1-25-true]