Skip to main content

Custom Domain Setup Advice From GoDaddy Is Wrong

We have recently seen a few blog owners, in the process of setting up their blogs for custom domain publishing, reporting various symptoms.
I get a bX-rfwe0f error, when trying to use the Publishing tab on Blogger, after purchasing a new domain from GoDaddy.

When investigated, an excerpted Dig log shows a common symptom. 3600 IN    A 3600 IN CNAME
Server "" is not a Google custom domain DNS server - it's owned by GoDaddy, and it's used for DNS forwarding. ( -, Inc. GO-DADDY-SOFTWARE-INC (NET-64-202-160-0-1) -

GoDaddy recently published new, easy to use, instructions for setting up DNS addresses for Google custom domains. Mapping Your Domain Name to Work with Blogger is so nicely written, that Blogger blog owners don't realise that - as well written as it is - it is still wrong.
To point your Blogger blog to your domain name, you set up domain name mapping, which configures your blog settings and domain name. You update your settings in your Blogger account and our Domain Manager:
  1. Park the domain name you want to use with your Blogger account on our parked nameservers.
  2. Edit the www CNAME record for the domain name you want to use with your Blogger account. This update tells the Web browser to open your Blogger blog when visitors enter your domain name's URL in the browser address bar.
  3. Forward your domain name to use www. This step ensures your Blogger blog displays for visitors who go to your domain name with or without the www prefix. For example, it displays for visitors who entered both and
  4. Configure your Blogger account to use your domain name.
That's just the overview. Each step comes with a nicely written step by step instruction, that almost any blog owner can use, and setup their domain in 15 minutes.

The problem is that, once the 15 minutes are up, the domain is forwarded to Blogger. And forwarding is not an effective technique for redirecting custom domain traffic. To setup a custom domain, you have to use referral, in one of 3 models.

If you wish to see how to setup a properly referred domain, read Correcting The GoDaddy Custom Domain Setup Advice.

>> Top


Anonymous said…
I have experienced this problem for the past two weeks and cannot get into the settings/publishing tab to do anything about it. Google Support keeps telling me that they are trying to get a hold of the specialist for an update on my issue.

Can you recommend any steps in the meantime?

Many thanks,
Jo said…
okay so how do we fix it? or is there no fix at this moment?
Chuck said…
You need to use "4 x "A" + "CNAME"" referral, or one of the other two supported DNS models.

Watch this blog for detailed instructions which will supplement or correct the GoDaddy instructions, coming soon.
Helen Bushnell said…
Yes, please post this. I am going to be doing this sometime in the next month, and I would like to get it right.

Popular posts from this blog

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.

Help! I Can't See My Blog!

I just posted to my blog, so I know that it's there. I can tell others are looking at it. But I can't see it.

Well, the good news is you don't have a blog hijack or other calamity. Your blog is not gone.

Apparently, some ISPs are blocking *, or maybe have network configuration or infrastructure problems. You can access or you can access, but you can't access, or

You can't access them directly, that is. If you can access any free, anonymous proxy servers, though, you may be able to access your blog.

Note: You can use PKBlogs with the URL pre packaged. Here is the address of this post (with gratuitous line breaks to prevent the old post sidebar alignment problem):

And an additional URL, to provide to those suffering from this problem, would be the WordPress version of this post: