Skip to main content

Don't Always Blame Blogger, With Your Blog Down!

Some of my favourite problem reports, in Blogger Help Forum: Get Help with an Issue, are about inconsistent blog online status.
It was fine yesterday. Why is it down, now?
I see the blog, just fine! Why are some of my readers complaining?
I can access it, using my phone! Why is Blogger down, on my home computer?
The registrar tells me everything is OK!
Whenever I see the latter report, I know exactly where to start.

Particularly when I see the latter symptom, I know exactly where to start.

The registrar tells me everything is OK!

The "registrar says" is a frequent indicator of the problem. I'm not naming names, but the initial "G" (and not "Google") is very frequently involved, in this case.

So, I start with a Dig log, for the domain. And 99% of the time, that's all that is needed.

Bogus DNS addresses are a very commonly seen diagnosis, in so many of these cases. For 99.99% of the blogs, published to a custom domain, there is simply no effective substitute for the "Asymmetrical DNS" setup, provided long ago.

  • Maybe the blog will be up for you, and some would be readers - but others will be seeing the "404".
  • Maybe it was fine, yesterday - and today it is suggesting spam and viruses.
  • It will only work, for some people, some of the time. That is the only constant.

So you call the registrar - and they tell you that it has to be Blogger, because they have no problem accessing it. But the registrar is part of the problem.

The righteous address setup. 3600 IN A 3600 IN A 3600 IN A 3600 IN A 3600 IN CNAME

The domain root uses 4 x "A" addresses, accessed in a round robin sequence. And the published URL uses a single "CNAME", resolved using a complex name server array. With both domain root and "www" alias properly addressed, your blog has much better chance of being consistently and reliably accessed.

One possibly righteous address setup.

One Blogger Engineer recommended a modified version of the asymmetrical DNS setup, to be used by 1&1 customers. Only time will tell if this setup is reliable. I have seen several 1&1 customers, this year, suggesting that this is not long term reliable. 3600 IN A 3600 IN CNAME

Some spurious address setups.

Spurious address setups are unlimited, in variety. Here are a random 3 examples, from recent forum history.

Error when adding domain

When i am trying to adding the domain it shows the error
Whoops, that's an error! (bX-6g9yx1) 600 IN A 3600 IN CNAME

Blogger appears to be detecting this setup as a problem - and throws a bX code, to indicate a problem.

Mobile Redirection Failure

When I am on mobile on google chrome (only browser I tested). does not redirect to on mobile. 600 IN A 3600 IN CNAME

This blog is online - and visible, using broadband - but no domain root redirection, for mobile browsing. "" is not a Blogger / Google name server, and won't provide reliable redirection.

Can't publish my blog

When I entered the "" domain in 3rd-party domain settings, I did not receive an error. I did not see the 2 CNAME records. 600 IN A 3600 IN CNAME

This blog published - but ownership verification did not provide the required second "CNAME".

The bottom line.

There simply is no substitute for righteous DNS addressing, for custom domain publishing. Publishing to a custom domain is not a productive activity, if you cannot follow instructions.

The ability to publish a #Blogger blog to a non BlogSpot URL has been provided, for almost 10 years. Some blog owners still cannot setup the domains properly - and remain oblivious, when a problem arises.

Learn why there is one effective DNS address setup, for custom domain publishing.

If you want a reliable custom domain, this is the address choice.


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: