DNS Propagation: Monitor Global DNS Propagation in Real Time

DNS propagation: why changes are not instant

You just changed your site's IP in the DNS A record. You open the browser and the site works with the new IP. You call a colleague and for them the site still shows the old content. What's happening? Welcome to the world of DNS propagation. DNS resolvers around the world keep cached copies of records for the duration of the TTL (Time To Live). Until the old record's TTL expires, each resolver continues to serve the old response from cache without querying the authoritative nameserver again.

Propagation is not an active process where your nameserver "sends" changes to resolvers around the world. It is a passive process: resolvers update their cache as the old TTL expires and they request a new response. This means that different resolvers, queried at different times, have caches of different ages and therefore potentially different versions of the record. The result is a transitional period where some users see the new value and others see the old one.

How to monitor propagation

$ dns-prop --domain esempio.com --type A

Server              Regione        Valore           TTL
─────────────────────────────────────────────────────────
8.8.8.8             US-East        93.184.216.34    1247
1.1.1.1             US-West        93.184.216.34    892
9.9.9.9             EU-Central     203.0.113.50     ← vecchio!
208.67.222.222      EU-West        93.184.216.34    445
119.29.29.29        Asia-East      203.0.113.50     ← vecchio!

Propagazione: 60% completata (3/5 server aggiornati)

Our DNS Propagation queries over 20 DNS resolvers distributed across all continents, showing which value each one returns and the remaining TTL. This lets you know exactly how many resolvers have already updated the record, how many still have the old value, and how much time remains based on the remaining TTL. It is the indispensable tool after every DNS change to confirm that propagation is complete.

Strategies to speed up propagation

The main strategy is to plan ahead: 24-48 hours before the planned change, lower the record's TTL to 300 seconds (5 minutes). Wait for the old TTL to fully expire (if it was 86400 seconds, wait 24 hours after the TTL change). Then make the actual change: with a 300-second TTL, all resolvers will update their cache within minutes. Once stability is verified with DNS Lookup, raise the TTL back to its normal value.

To verify that your record is configured correctly before propagation completes globally, you can query your authoritative nameservers directly with NS Lookup — the response from the authoritative nameserver is always updated in real time, regardless of resolver caches. If the authoritative nameserver returns the correct value, the change is effective and propagation is just a matter of time and TTL.

Avoid "Friday evening DNS changes": if something goes wrong, having a weekend in between enormously complicates resolution. Plan critical DNS changes at the beginning of the week, with enough time to monitor and correct any issues. And always keep a record of previous values: if the change causes problems, being able to quickly restore the old record is essential to minimize downtime.