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

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: