Skip to main content

Custom Domains And URL Forwarding - Still A Bad Idea

Setting up a Google Custom Domain, which gives us the ability to publish our Blogger blog to a non BlogSpot URL, is a reasonably simple process. That simple process, though, depends upon several not so simple factors.
  1. Our understanding of how rigidly simple the DNS setup is.
  2. Our acceptance of how rigidly simple the DNS setup is.
  3. Our use of a registrar that provides us the DNS setup that is required.
Custom Domain setup is simple - but allows for no deviations.

You may read my series Diagnosing Problems With Custom Domains - and examine a total of 7 unique configurations.

2 identified configurations work properly - and 5 either don't work at all, or work temporarily or unreliably. I actually recommend 3 configurations - and focus on one configuration, for best results.

One example of the latter possibility - a configuration which works temporarily - is a custom domain setup using URL forwarding. Here, I'll show excerpted Dig logs of various domain DNS configurations.

During the past couple weeks, we have seen dozens of reports similar to "".        51      IN      A      43200   IN      CNAME

An intriguing variation would be "". 10800 IN A 86400 IN A

Then, we have "". 3600 IN A 3600 IN CNAME

These are, each, various examples of URL forwarding. Apparently, URL forwarding worked for a while, though I've been predicting the emergence of this problem for some time. Now, changes by Blogger means that URL forwarding does not work reliably, and many blogs are out of action.

If your blog recently stopped working, and your DNS is setup similar to "", "", or "", that is why you are here. You need to change your setup to use a Google Apps configuration, with up to date DNS.

With a normal custom domain DNS configuration, the domain uses an "A" or "CNAME" referral, which points directly to a Google server. When the Blogger script verifies that the domain URLs both point to Google, it can proceed with confidence.

If one, or both, of the domain URLs point to a non-Google server        51      IN      A      43200   IN      CNAME

or 10800 IN A 86400 IN A

or 3600 IN A 3600 IN CNAME

the Blogger script has no way of knowing that your Blogger blog is targeted, even indirectly. The Blogger script can't look within the forwarding script on the non-Google server, as it can when verifying "A" and "CNAME" referrals, by using Dig (as we do above). Trying to eliminate one cause of the "Not Found Error 404", the Blogger script is conservative, and without an "A" or "CNAME" referral, you see
Another blog is already hosted at this address.

It's quite simple, when you understand the complexities. But you do need to either understand the complexities, or at least understand that they exist, and accept the advice of the people who do understand.

Having changed your DNS to use "A" / "CNAME" referrals for both URLs, remember to publish back to BlogSpot, then republish to your "www" alias, to ensure a clean repair of the problem.

(Update 11/21): Want to see a tangible example why URL Forwarding is a bad idea? That's one more example showing that URL forwarding is simply another spurious solution.


imamnic said…
Dear Chuck,
Thank you for the DNS analysis you did to my page
It's awesome, I am still learning on that

I am using URL forwarding because Blogger said if we use custom domain for other registrar but still using blogger as host, the picture will not be normal.
Of course I want my domain showed in address bar (like, not redirected to but if that sacrifies the picture setting that would not be nice.
1. Is it true that if we assign CNAME using other domain registrar Blogger will not show our picture?
2. Can I renew my domain in blogspot with autenthication code from my last registrar (I switch the registrar not the domain)?

Thank you very much, your help is very much appreciated

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: