Skip to main content

Confusion Over Domains Purchased From Registrars

Blogger / Google offers the optional ability to publish a Blogger blog to any available non BlogSpot URL, aka "Custom Domain Publishing".

The process of setting up a custom domain is so simple - when we use the "Buy a domain" wizard. As simple as "Buy a domain" is, it involves details that are unbelievably complex - and too many blog owners, avoiding use of "Buy a domain", will find out about these details the hard way.

One important detail about custom domain publishing involves the level of service, as purchased from the registrar. There are three basic levels of service, offered by many registrars.
  1. Name registration, only.
  2. DNS hosting / Name registration.
  3. Content hosting / DNS hosting / Name registration.
Choose the wrong service level, and you'll waste either time - or money. And, we all know that "time is money".

Too many blog owners, anxious to setup and show off their new, non BlogSpot URL, make the wrong choice of service.

Blog owners, unsure how to purchase their domain, become more forum noise.

They end up in Blogger Help Forum: Something Is Broken, anxiously asking

What are the nameservers used for Blogger?


How do I publish my blog, using the registrar's Site Builder wizard?

The mistake of purchasing the wrong service is always a possibility, when buying directly from a registrar.

Please, only purchase "DNS Hosting" - not "Name Registration"!

Since custom domain publishing was first offered as an option, I've been advising people to

Please, check the invoice or receipt from the registrar. If you purchased "Name Registration", instead of "DNS Hosting", you need to go back immediately, and upgrade your service.

GoDaddy, for instance, offers "Bring your own DNS", where they register the domain on your behalf, and you provide the nameservers. If you understand DNS, you are entitled to try this option - just please don't publish your blog and try to advertise it in Blogger Help Forum: Something Is Broken as a solution.

GoDaddy "Bring your own DNS" is not an acceptable choice.

"Bring your own DNS" is simply not an advisable option, for 99.99% of all Blogger blog owners - and we do not need people suggesting it, as an immediate choice.

The sad thing is that Blogger, in even their current tutorial (which is, itself, subject to change), makes no canonical distinction between the three levels of service that the various registrars may offer. Long ago, they simply advised

... you only need to get the domain name; you don't have to pay extra for hosting service.

With that history, is it any wonder that we should expect to occasionally see the confusion

What are the primary and secondary DNS servers?

And having purchased "DNS Hosting", the blog owner must then setup the DNS addressing.


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: