DNS Propagation: Definition, Time, and How to Check It

DNS propagation is the period between changing a DNS record and every resolver on the internet returning the new value. It exists because resolvers cache DNS answers for a set time, called the TTL, and keep serving the old answer until that time runs out. Most record changes take effect within minutes to an hour, while nameserver changes can take up to 48 hours.

How DNS Propagation Works

DNS changes are not pushed anywhere. The new value is live on your authoritative nameserver the moment you save it. The delay comes from caches that still hold the previous answer.

Every DNS lookup follows the same path:

A browser asks the operating system, which checks its own cache.
If the answer is missing, the request goes to a recursive resolver, such as an ISP resolver, Google Public DNS (8.8.8.8), or Cloudflare (1.1.1.1).
The resolver checks its cache. On a miss, it queries the root, the TLD servers, and then your authoritative nameserver.
The resolver stores the answer for the record’s TTL and returns it.

example.com.    3600    IN    A    203.0.113.10

The 3600 is the TTL in seconds. A resolver that cached this record a minute before you edited it will keep returning 203.0.113.10 for up to 59 more minutes. Thousands of resolvers cached the record at different moments, so the switch happens gradually. That gradual switch is what people call propagation.

DNS Propagation Time by Change Type

Propagation time depends on what changed and on the TTL that was cached before the change.

Change	Typical time	What controls it
New record at a new name	Seconds to minutes	Negative cache, if the name was looked up before
Edited record (A, CNAME, MX, TXT)	Up to the old TTL	TTL on the record before the edit
Nameserver change	Up to 48 hours	TTL on the NS records at the TLD
Domain transfer, same nameservers	Usually none	Nothing changes in DNS

The “24 to 48 hours” figure comes from nameserver changes. Verisign publishes the NS records for .com domains with a TTL of 172,800 seconds, which is exactly 48 hours. A plain record edit with a 300 second TTL is visible everywhere in about 5 minutes.

New records have one trap. If anyone looked up the name before it existed, resolvers cached the “does not exist” answer. RFC 2308 sets that negative cache by the SOA record of the zone, often 3600 seconds or more.

How to Check DNS Propagation

Query several public resolvers and compare the answers with your authoritative nameserver.

dig A go.example.com @ns1.your-dns-host.com +short
dig A go.example.com @8.8.8.8 +short
dig A go.example.com @1.1.1.1 +short

The first command shows the true current value. If the public resolvers return the same value, the change has reached them. dig +trace go.example.com follows the full chain from the root, which confirms that a nameserver change took effect at the TLD. On Windows, nslookup -type=A go.example.com 8.8.8.8 does the same job.

Web tools such as whatsmydns.net run the same query from dozens of locations at once. They show which regions still hold the old answer, not which visitors do.

For a new A record or CNAME on a branded subdomain, link platforms run this same check before they verify the domain and issue an SSL certificate.

How to Speed Up DNS Propagation

Nothing forces every resolver to drop its cache. Planning ahead and clearing the caches you control are the only reliable levers.

Lower the TTL in advance. Set it to 300 seconds at least one full old TTL before the change. If the TTL was 86,400, lower it a day early.
Purge public resolver caches. Google offers a flush form at dns.google/cache, and Cloudflare offers one at one.one.one.one/purge-cache.
Flush your own machine. Run ipconfig /flushdns on Windows or sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder on macOS. In Chrome, clear the host cache at chrome://net-internals/#dns.
Avoid early lookups of new names. Checking a subdomain before creating its record fills the negative cache.
Raise the TTL afterward. Return to 3600 once the change is confirmed, to cut lookup traffic.

Common Misconceptions About DNS Propagation

“DNS changes spread from server to server.” They do not. Each resolver fetches the new value on its own when its cached copy expires.
“Every change takes 48 hours.” Only nameserver changes approach that. Most record edits finish within the old TTL.
“A working site on my phone means it worked everywhere.” Your phone may use a different resolver than your laptop or your customers.
“Resolvers always obey TTL.” Some ISP resolvers apply minimum cache times, so a handful of users may see the old value a little longer.

Frequently Asked Questions

How long does DNS propagation take?

DNS propagation takes anywhere from a few minutes to 48 hours. A normal record edit completes within the TTL that applied before the change, often 5 minutes to 1 hour. Nameserver changes are the slow case, because .com delegation records are cached for 48 hours. Most changes are visible to the large majority of users well before the maximum.

Why is my DNS not propagating?

The usual cause is that the change was saved at the wrong provider. Records edited at the registrar have no effect when the domain uses another DNS host’s nameservers. Other causes are a long TTL on the old record, a cached “does not exist” answer, or a typo in the host field. Query the authoritative nameserver directly to see which one applies.

What is a DNS lookup?

A DNS lookup is the process of translating a domain name into an IP address or other record value. The device asks a recursive resolver, which returns a cached answer or queries the root, TLD, and authoritative servers. Propagation affects lookups only by deciding whether the resolver serves a cached old value or fetches the new one.

Can you check DNS propagation online?

Yes, tools like whatsmydns.net and DNSChecker query a record from many resolvers worldwide and show each result. They are useful for spotting regions still serving an old value. For an exact answer, also query your authoritative nameserver with dig and compare.

Once your DNS records resolve, connect a branded subdomain to your short links with linkutm branded domains.