Skip to main content

What Is "" vs. ""?

With Google Domains registered custom domains becoming more normal, we are seeing one odd attention to detail, expressed as confusion in Blogger Help Forum: Learn More About Blogger.
My website uses "" - am I supposed to use "", instead?
It's good to be attentive to detail, particularly with custom domain publishing. This is one detail that may not require immediate attention, however.

Long ago, with custom domains purchased and setup under "Buy a domain", a properly published blog always targeted "".  3600 IN A  3600 IN A  3600 IN A  3600 IN A 3600 IN CNAME

Now, with custom domains purchased and setup under Google Domains, we are seeing a subtle difference.  3600 IN A  3600 IN A  3600 IN A  3600 IN A 3600 IN CNAME

Or maybe  3600 IN A  3600 IN A  3600 IN A  3600 IN A 3600 IN CNAME

What is "" - or more specifically, what is the difference between "" and ""?

Let's look at a pair of Dig logs, using the Kloth.Net Dig utility.

;   IN A



;  IN A


Here, we see that "" and "" are, essentially, the same host - two names pointing to "". "" apparently omits the extra "CNAME" referral to "", used by "".

Now, to the original question.

Am I supposed to use "", instead of ""?

I do not use Blogger Help: How do I use a custom domain name for my blog? casually - particularly since they insist on trying to tell us that the domain root DNS addressing is optional.

Optional: You can also enter A-records, which links your naked domain ( to an actual site ( If you skip this step, visitors who leave off the "www" will see an error page.

That "Optional" causes too much confusion. In this case, however, I'll suggest that they can provide a guideline.

Where it says Name, Label or Host simply enter "www" and list as the Destination, Target or Points to.

If I were to get up tomorrow, and observe a change, I would probably react, as convenient.

Where it says Name, Label or Host simply enter "www" and list as the Destination, Target or Points to.

Until that day, or until I see an announcement in Blogger Buzz, I might tweak any new domains, or new domain host, that I were setting up - when convenient.  3600 IN A  3600 IN A  3600 IN A  3600 IN A 3600 IN CNAME

or possibly 3600 IN CNAME

I probably won't be tweaking this blog, immediately.

Adding to the confusion, when treating some problems, Google Domains Support may advise you to use a "CNAME" to "", instead of "",

As always, I'll thank you for paying attention to detail - when publishing your blog - and when redirecting the domain root. And always, please retain control of your Blogger account.


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: