Skip to main content

New Google Domains Need Time To Propagate

We're seeing an increasing number of problem reports, mentioning Google Domains.

Google Domains is becoming a popular registrar for new custom domains - and this leads to more problems, reported in Blogger Help Forum: Get Help with an Issue. Many reports look like timing problems, from long ago.

The most common symptom is the mysterious Redirect Warning.
I purchased a Google Domains site, and connected it to Blogger so it redirects my blog to my domain, no problem.

The problem is now when accessing the BlogSpot URL, it now shows a redirect warning message, which is killing my web traffic.
This blog is not hosted by Blogger and has not been checked for spam, viruses and other forms of malware.
How do I publish my blog, and keep my readers, with this confusion?

When a Redirect Warning is reported, we'll check the DNS addresses, and do an HTTP trace.
  • Base DNS addresses are righteous.
  • The domain is published to the blog - and the blog uses the domain URL, internally.
  • The BlogSpot URL redirects, to the warning notice, as noted.
The problem here is DNS propagation, combined with Blogger anti-malware classification.

New custom domains, long ago, had a built in "Transition" period.

Long ago, when Google "Buy a domain" was used for domain purchases, people would see a different "redirect notice" on their blogs, after a domain purchase.
Your blog is in transition
This notice would appear on the dashboard, when "View Blog" was clicked. Blogger would advise the new domain owner to wait "2 to 3 days", while the new domain would propagate to the worlds DNS servers, before publishing the blog to the domain.

Domains published through Google Domains must be watched for spam hosting.

Just as there is no way to prevent hackers and spammers from publishing Blogger blogs, there is no way to prevent them from using Google Domains to purchase and setup domains - that redirect to non Google websites, and serve malware and spam. Domains purchased through Google Domains must be subject to the same scrutiny, as domains purchased through eNom or GoDaddy - or any registrar in China, India, or any other country.

To detect malicious redirections, the Blogger anti-malware classification process must simulate our readers, viewing under real world conditions.

Part of the Blogger anti-malware classification involves checking for blogs containing redirects, that would cause our readers to load malicious or spammy websites, instead of a promised blog. The redirection checking has to include using DNS servers that are subject to real world DNS propagation delay - even when Google Domains is involved.

We "allow 48 to 72 hours" as a worst case scenario.

The stated "48 to 72 hour" delay is a worst case scenario - and in most cases, a few hours should suffice. When a blog owner reports the mysterious redirection notice
This blog is not hosted by Blogger and has not been checked for spam, viruses and other forms of malware.
If we verify righteous DNS addresses, we advise re publishing the blog to the domain.
Publish the blog back to BlogSpot, then re publish to the www host in the domain.
And when the dashboard Publishing display shows successful publishing, an HTTP trace will generally show the BlogSpot URL, properly redirecting to a published blog at the domain URL.

If republishing does not produce results, the domain publishing database may be corrupt. This is a long known problem, with custom domain publishing, and worldwide DNS timing. Use the "Contact support" link at the bottom of the Google Domains dashboard, and request that they reset the domain.

In some cases, the "48 to 72 hour" latency period will need to continue - but as Google Domains becomes more popular, this possibility will slowly decrease.


Thanks for the explanation. Unfortunately, I'm still waiting for mine to resolve.
Cherdo said…
I just discovered your blog and it is the most useful thing on the 'net. I'll be back!
Kristopher Daia said…
Google Domains takes every bit of the 24-72 hours to propagate. I hope that gets better!
Chuck Croll said…

Thanks for your observation.

Unfortunately, registrars do not control new domain propagation delay. New domain propagation is delayed by different ISPs that update their master DNS records, every 2 to 3 days.

Your computer does not connect directly to every different registrar, it connects to your ISP server, which maintains a master list of every domain, and where the domain name server is. The master DNS records are cached, and the cache is updated every 2 to 3 days, at the discretion of the ISP.

Google "new domain propagation time" if you want to read more about this. It's worth reading, if you have doubts.
Kristopher Daia said…
Thanks for setting the record straight Chuck!

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: