Skip to main content

Google Domains Purchases Should Involve Transition

One of the features of custom domains, when purchased using "Buy a domain", was the Transition period.

Transition was Blogger, allowing that even with Blogger / Google controlling the domain authoritative servers (which they did, indirectly, by using eNom / GoDaddy as the registrars), and the initial DNS address setup (offered for GoDaddy purchased domains), the stability of custom domains only starts with the domain authoritative servers, and the Root Name servers.

Custom domain published blogs, to be consistently stable, can only rely on the DNS addresses being available on the local DNS servers, on a worldwide basis, 48 to 72 hours after the DNS addresses are added. This built in latency period has nothing to do with how custom domains are designed - and it's an issue over which Blogger and Google have no control.

Blogger provided the "Buy a domain" option, for custom domain purchases, 2008 - 2012, then briefly 2012 - 2013.

The previous "Buy a Domain" ended, in 2013 - now, we have "Google Domains".

Having permanently shut down "Buy a domain" in 2013, we now see the successor, Google Domains - which some customers call "Buy a domain - 2". Google Domains offers domain registration and DNS hosting, as a yearly package, with various popular features such as anonymous registration - all Google in house services, this time.

For all of the advantages of providing the domain purchase, registration, and setup, that just gets the domain paid for, registered with the Root Servers, and setup with the right DNS addresses. That does not get the DNS addresses, that point each domain to Google and to each Blogger blog, cached on the local DNS servers that we all use, as we surf the Internet.

The worldwide DNS infrastructure is immense, compared to Google.

The DNS infrastructure is hundreds to thousands the size of the Google DNS infrastructure, Think of how many ISPs there are, worldwide. Any ISP of any size is going to provide its customers with DNS service - if only to provide addresses for its own non DNS servers.

Google will never dominate the worldwide DNS infrastructure. Even domains which they sell, register, and setup have to be propagated worldwide, to every local DNS server - and there is the latency, that they do not control.

Allow 48 to 72 hours, for the domain to be visible, everywhere.

We still need a "Transition" period, to allow for every ISP, worldwide.

And the Blogger custom domain Transition period is needed, to allow for that latency.

And anybody who remembers Transition under "Buy a domain" should remember the mysterious gadget update period, that did not happen until after Transition was complete.

If you register a domain, using Google Domains - then use the Blogger wizard "Setup a Google Domains URL for your blog" to publish your blog to your new domain, you should get a dashboard reminder

Your blog is in transition

While that reminder is visible, your domain is being propagated, to the worldwide DNS infrastructure.

While you see the reminder - or even if you don't see the reminder - spend your time reading, and preparing for the migration process - that starts after Transition ends. You want your domain to work properly? Be patient.


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: