Skip to main content

Clear Or Refresh Your DNS Cache

Blogger custom domain publishing depends upon DNS.

Sometimes, when we have a blog published to a Google Custom Domain, we'll make a change to the domain DNS configuration and notice that our readers can see the change, but we can't.
Once again, at 6:23, someone was able to see my blog and leave a comment

Yet, moments after I tried, I was still getting the 404 error. So there seems to be some intermittent activity!
This is not an unusual report.

Problems with custom domain publishing almost always involve some sort of DNS issue.

Let's look at a hypothetical domain DNS configurations, as one example. First, current:   14400   IN      A 14400      IN      A 

Then, new:   14400   IN      A   14400   IN      A 14400      IN      CNAME 

Note that the above addresses have long since changed. We now have a quadruplet "A" address complement - which is a bit harder to notice, casually.

A TTL of 14400 seconds (4 hours) is a bit extreme. I see mostly 3600 seconds (1 hour), sometimes 900 seconds (15 minutes), in most DNS configurations.

If the TTL for your domain is 4 hours, it could be about that long after you make the change, before you start seeing any change.

I say "about", because the age of the configuration information, as cached on your computer or server when you make the change, is relevant. If the information is 15 minutes old, then with a TTL of 14400, you'll have to wait another 13500 seconds, or 3 3/4 hours. If the information is 3 hours old, you'll wait merely another hour.

Fortunately, you can hasten that if if the cache on your computer is the bottleneck.

From a command window, enter
ipconfig /flushdns
If the DNS cache in question is on your computer, it's gone now. The next time that you try for your custom domain, it should come up in its new configuration.

Note 2 Caveats

  • If you have a caching non-authoritative DNS server that your computer retrieves DNS directly from, you'll still have to wait. The "ipconfig" command works only under Microsoft Windows, and only on the computer with the cache. If the cache is upstream from you, you're going to have to remain patient.
  • Whether or not your local DNS cache, and your upstream non-authoritative DNS server gets the updates, you still can't predict the update status of the Google non-authoritative DNS servers.

Knowing your DNS setup is a good idea, when working with custom domains. And allowing for DNS latency at Google is essential.


Popular posts from this blog

What's The URL Of My Blog?

We see the plea for help, periodically I need the URL of my blog, so I can give it to my friends. Help! Who's buried in Grant's Tomb, after all? No Chuck, be polite. OK, OK. The title of this blog is "The Real Blogger Status", and the title of this post is "What's The URL Of My Blog?".

Where's The Dashboard?

We see this confusion, a couple times a week, in Blogger Help Forum: How Do I? . Where is the dashboard? In the Classic Blogger GUI, the display which contained the "Blog List" (at the top), and the "Reading List" (at the bottom) was labeled "Dashboard". Many people also called the "Settings" / "Template" screens for the various blogs, linked from the Blog List, the dashboard. The New Blogger GUI has no page with the label - and no links "To The Dashboard". The Navbar (another unlabeled feature) has two links - "Design" and "New Post" - which lead to different dashboard sections, when you are appropriately logged in to Blogger . And, the "B" logo at the far left of the navbar will, similarly, take you to the Blog List / Reading List.