Skip to content

DNS Propagation

DNS propagation describes the period during which cached DNS answers expire and different resolvers begin returning newly updated DNS information.

DNS propagation is the common term used to describe the period during which different DNS resolvers and clients begin observing updated DNS information.

It is not usually a single update being pushed outward from one central DNS server.

What Actually Happens

DNS uses distributed caching.

Suppose:

example.com

changes from:

192.0.2.10

to:

192.0.2.20

A resolver with the old answer cached may continue using it until its TTL expires.

Another resolver that has no cached answer may request the new value immediately.

Different visitors can therefore temporarily receive different answers.

Why the Term Can Be Misleading

“Propagation” can make DNS sound like this:

Change record
    ↓
Wait for new value to physically spread everywhere

A better mental model is:

Change authoritative record
        ↓
Old cached answers expire at different times
        ↓
Resolvers request the new answer

TTL is therefore an important part of the behaviour.

Nameserver Changes

Changing authoritative Nameservers can involve additional caching and delegation behaviour.

This is one reason nameserver migrations should be planned more carefully than changing a single A record.

Other Caches

Even after DNS caches update, a user may still experience stale behaviour because of:

  • Browser caching
  • Operating-system DNS cache
  • Network resolver cache
  • CDN Caching
  • Application caching
  • Local hosts configuration

Not every stale page is a DNS propagation problem.

Why It Matters

Understanding propagation prevents unnecessary changes.

If an administrator repeatedly edits DNS because one connection still shows the old result, they may make the situation harder to diagnose.

How to Improve

Before a migration:

  • Review TTL
  • Lower it ahead of time if appropriate
  • Verify the authoritative record
  • Test with more than one resolver
  • Distinguish DNS results from website caching

Then allow existing cached records to expire normally.