DNS Propagation: Why It Takes Time & How to Check (2026)

What Is DNS Propagation?

DNS propagation is the process by which updated DNS records spread across the global network of DNS servers. When you change a record at your domain registrar or DNS host, that change starts at your authoritative nameserver. But DNS resolvers worldwide have cached the old record. Propagation is the time it takes for every resolver to expire its cached copy and fetch the new record.

Strictly speaking, DNS doesn't "propagate" in a push-based way. There is no broadcast. Instead, resolvers passively expire their caches and re-query your authoritative server. The term "propagation" describes the observable effect: over time, more and more resolvers return the new record.

How DNS Caching Works

DNS is designed for performance. Every time a resolver looks up a record, it caches the result to avoid repeated queries to the authoritative server. This caching happens at multiple levels:

• Recursive resolvers — Your ISP's DNS server or public resolvers like Google (8.8.8.8) and Cloudflare (1.1.1.1) cache records for the duration of the TTL.
• Operating system cache — Your computer's OS maintains its own DNS cache. On Windows you can flush it with ipconfig /flushdns; on macOS with sudo dscacheutil -flushcache.
• Browser cache — Browsers cache DNS lookups internally, typically for 60 seconds, independent of the TTL.
• Application cache — Some applications and libraries maintain their own DNS caches.

Each cache layer adds potential delay. Even if a resolver has fetched the new record, your local OS or browser cache may still serve the old one.

TTL Explained

TTL stands for Time to Live. It is a value (in seconds) attached to every DNS record that tells resolvers how long they are allowed to cache that record before they must re-query the authoritative nameserver.

For example, a TTL of 3600 means resolvers will cache the record for one hour. After 3600 seconds, the cached entry expires and the resolver fetches a fresh copy. A TTL of 86400 (24 hours) is common for stable records, while 300 (5 minutes) is typical when you expect frequent changes.

The TTL is the single biggest factor in propagation time. If your record has a 24-hour TTL, resolvers that just cached it will hold the old record for up to 24 hours. If you lowered the TTL to 300 seconds before making your change, the worst-case wait is only 5 minutes.

Why DNS Propagation Isn't Instant

Several factors combine to make DNS changes take time:

1. TTL caching. The primary reason. Resolvers respect the TTL and won't re-check until the cached record expires.
2. Multiple cache layers. Even when the recursive resolver has the new record, your OS, browser, and applications may still serve cached data.
3. Registrar processing time. Some registrars and DNS hosts batch updates or have internal delays before publishing changes to the authoritative nameservers.
4. Resolver behavior. Some ISP resolvers ignore low TTLs or enforce a minimum cache time (often 5 minutes), even if your TTL is lower.
5. Negative caching. If a resolver queried your domain and received an NXDOMAIN (not found) response, it may cache that negative result for the SOA minimum TTL, delaying when it retries.

How Long Does Propagation Take?

Propagation time depends on the record type and TTL. Here are typical ranges:

• A / AAAA records — Usually 5 minutes to 24 hours. Most propagation completes within a few hours if the TTL is reasonable.
• MX records — Similar to A records (minutes to 24 hours). Changes can temporarily cause mail routing issues, so plan carefully.
• NS records (nameserver changes) — These often take the longest, up to 48 hours. The parent zone (TLD registry) must update its delegation, and registrars process NS changes asynchronously.
• TXT records (SPF, DKIM, DMARC) — Usually 1 to 24 hours. Since email authentication relies on TXT lookups, keep old and new records valid during the transition.
• CNAME records — Usually 5 minutes to 24 hours, depending on TTL.

The "up to 48 hours" figure often cited in documentation is a conservative worst case. In practice, most propagation finishes in under 4 hours for records with standard TTLs.

How to Check DNS Propagation

The fastest way to verify propagation is to query multiple DNS resolvers worldwide and compare results. Our DNS Propagation Checker queries resolvers including Google, Cloudflare, OpenDNS, Quad9, and others simultaneously and shows you which resolvers have the new record and which still serve the old one.

You can also check manually using command-line tools:

• dig @8.8.8.8 example.com A — Query Google's resolver directly.
• dig @1.1.1.1 example.com A — Query Cloudflare's resolver.
• nslookup example.com 9.9.9.9 — Query Quad9's resolver.

If different resolvers return different results, propagation is still in progress. When all resolvers return the same record, propagation is complete.

Tips to Speed Up DNS Propagation

You cannot force propagation to happen faster after a change, but you can prepare in advance:

1. Lower the TTL before making changes. At least 24 to 48 hours before your planned change, reduce the TTL on the record to 300 seconds (5 minutes). This ensures resolvers worldwide are caching with the short TTL by the time you make the actual change.
2. Make the change, then raise the TTL back. After propagation completes, increase the TTL to a normal value (3600 or 86400) to reduce query load on your nameserver.
3. Flush your local DNS cache. After making a change, flush your OS DNS cache so you see the new record immediately on your own machine.
4. Use a reliable DNS provider. Providers like Cloudflare, AWS Route 53, and Google Cloud DNS publish changes to their authoritative nameservers within seconds. Some budget registrar DNS hosts can take minutes to publish.
5. Avoid changing nameservers unless necessary. NS record changes involve the TLD registry and take the longest to propagate. If you only need to change an A or CNAME record, do it within your existing nameserver.

Common DNS Propagation Issues

• Seeing the old record after hours. Check whether the TTL on the old record was very high (e.g., 86400). The resolver must wait for that TTL to expire. Also check your local OS and browser caches.
• Some resolvers show the new record, others don't. This is normal during propagation. Different resolvers cached the record at different times, so their TTLs expire at different times.
• Record shows correct on Google but not your ISP. ISP resolvers sometimes enforce a minimum cache time or are slow to expire. Try switching to a public resolver like 8.8.8.8 or 1.1.1.1 as a workaround.
• Email not working after MX change. MX propagation can take several hours. Keep the old mail server running and accepting mail during the transition window to avoid bounced messages.
• Nameserver change appears stuck. NS changes go through the TLD registry and can take up to 48 hours. Verify that the registrar has processed the change and the correct NS records appear at the TLD level using our NS Lookup tool.

Useful Tools for DNS Propagation

• DNS Propagation Checker — Check propagation status across 8+ global resolvers instantly.
• DNS Lookup — Query any DNS record type for a domain.
• NS Lookup — Check which nameservers are authoritative for a domain.