Glossary

DNS Propagation

The time it takes for DNS changes to spread across global resolvers

DNS propagation is the period of time required for a DNS record change made at an authoritative nameserver to be reflected across the global network of recursive resolvers and caches, which can range from minutes to 48 hours depending on the record's TTL.

What is DNS Propagation?

DNS propagation describes the process by which changes made to DNS records — such as updating an A record, modifying an MX record, or changing nameservers — gradually spread to DNS resolvers around the world. The internet does not have a single DNS database; instead, it is a distributed system of caches and resolvers that each store copies of DNS records for a period defined by the record's Time to Live (TTL) value.

When you update a DNS record, the authoritative nameserver for your domain immediately reflects the new value. However, recursive resolvers that have previously cached the old record will continue to serve the outdated value until their cache entry expires. Only once the TTL has elapsed will those resolvers query the authoritative server again and retrieve the updated record.

Propagation is not a simultaneous global event — different resolvers will update at different times depending on when they last cached the record and their geographic location.

How Long Does DNS Propagation Take?

The propagation time for a DNS change is largely determined by the TTL of the record being changed. A record with a TTL of 300 seconds (5 minutes) will propagate quickly because resolvers must recheck after 5 minutes. A record with a TTL of 86400 seconds (24 hours) may take up to a full day to propagate everywhere.

Nameserver (NS) changes — such as moving a domain to a new hosting provider — can take longer because they involve updating the parent zone's delegation records and waiting for TTLs at multiple levels of the DNS hierarchy to expire. The commonly cited "24 to 48 hours" for nameserver changes reflects this compound waiting period.

A best practice when planning DNS changes is to reduce the TTL of the affected records to a low value (such as 300 seconds) several hours or days before making the change. Once the change is confirmed to be working correctly, the TTL can be increased again.

How to Check DNS Propagation

You can monitor how a DNS change is propagating across the globe using the DNS Propagation Checker at nslookup.net/tools/dns-propagation-checker. Enter your domain and select the record type, and the tool will query resolvers in multiple geographic regions simultaneously, showing which locations are returning the new value and which are still serving the old cached record.

This is invaluable when troubleshooting issues after a DNS change, as it pinpoints which regions are still seeing outdated records.

Related Tool

DNS Propagation Checker

Try the Tool →

Frequently Asked Questions

Why do some users see my new DNS record while others still see the old one?

Different users connect to different recursive resolvers, and each resolver caches DNS records independently. If a resolver last cached your record recently, it will continue to serve the old value until the TTL expires. This is why DNS changes appear to "propagate" gradually — each resolver updates independently when its cache entry expires.

Can I speed up DNS propagation?

The most effective way to speed up propagation for a planned change is to lower the TTL of the affected record well in advance — ideally 24 to 48 hours before the change — to a value like 300 seconds. This shortens the cache window so resolvers fetch the new record sooner after the change is made. You cannot force other resolvers to flush their caches.

What is the difference between DNS propagation and DNS replication?

DNS replication refers to synchronisation between the primary and secondary authoritative nameservers for a zone, which typically happens within seconds using NOTIFY and zone transfer (AXFR/IXFR) mechanisms. DNS propagation refers to the slower process of cached values expiring at recursive resolvers worldwide. Replication is fast; propagation is governed by TTL values.

Does DNS propagation affect email delivery?

Yes, DNS propagation directly affects email delivery during MX record changes. If you update your MX records to point to a new mail server, sending MTAs that have cached the old MX records will continue delivering to the old server until their cache expires. Overlapping the operation — keeping the old server active until propagation is complete — prevents mail loss during the transition.