What Is DNS Propagation?

Understand why DNS changes take time to propagate, how TTL affects propagation speed, and how to check and speed up the process.

What Is DNS Propagation?

DNS propagation is the process by which updated DNS records are distributed across all DNS servers worldwide. When you change a DNS record - such as pointing your domain to a new IP address - that change does not take effect instantly everywhere. Instead, it gradually spreads as cached records expire and are replaced with the new data.

During propagation, some users may see the old DNS records while others see the new ones, depending on which DNS server their request reaches and whether that server has already refreshed its cache.

Common Scenario: You migrate your website to a new server and update the A record. For the next few hours, some visitors reach the old server while others reach the new one. This is DNS propagation in action.

Why Does Propagation Take Time?

DNS is a distributed, hierarchical caching system. When a recursive resolver looks up a domain, it caches the result for the duration specified by the record's TTL (Time to Live). Until that cached entry expires, the resolver will continue serving the old data - even if the authoritative record has already changed.

The delay is caused by several factors:

TTL values: If your records had a high TTL (e.g., 86400 seconds = 24 hours), resolvers that cached the old record may not check for updates for up to 24 hours.
Multiple cache layers: DNS is cached at the browser, OS, router, ISP resolver, and sometimes CDN level. Each layer has its own cache expiration.
ISP behavior: Some ISPs ignore TTL values and cache records for longer than specified, which can further delay propagation.
Geographic distribution: DNS servers in different regions may update at different rates.

How Long Does Propagation Take?

Propagation time depends primarily on the TTL of the previous records:

Previous TTL	Typical Propagation Time	Scenario
`300` (5 minutes)	5–30 minutes	Pre-lowered for migration
`3600` (1 hour)	1–4 hours	Standard configuration
`14400` (4 hours)	4–12 hours	Common default at some registrars
`86400` (24 hours)	12–48 hours	High TTL, worst case

The commonly quoted "up to 48 hours" is a conservative upper bound. In practice, most propagation completes much faster, especially if TTL values were reasonable.

How to Check DNS Propagation

You can verify whether your DNS changes have propagated using several methods:

Our DNS Propagation Map: Use our DNS Checker Map tool to check your domain's DNS records from servers around the world.
Command line: Query specific DNS servers directly:
- dig example.com @8.8.8.8 - Check against Google DNS
- dig example.com @1.1.1.1 - Check against Cloudflare DNS
- nslookup example.com 9.9.9.9 - Check against Quad9
Check your authoritative server: dig example.com @ns1.yourdns.com - This confirms the change was applied correctly at the source.

How to Speed Up DNS Propagation

While you cannot force every DNS server in the world to update, you can minimize propagation time with these strategies:

Lower TTL in advance: Before making changes, reduce the TTL to 300 (5 minutes) at least 24–48 hours before the planned change. This ensures most caches will have the low TTL when you make the switch.
Make the change and wait: After updating the record, the low TTL means resolvers will refresh within minutes.
Restore the TTL: Once propagation is confirmed, raise the TTL back to a normal value (e.g., 3600 or 86400) to reduce DNS query load.
Flush local caches: Clear your own DNS cache to see changes immediately on your machine:
- Windows: ipconfig /flushdns
- macOS: sudo dscacheutil -flushcache
- Chrome: Visit chrome://net-internals/#dns and click "Clear host cache"

Best Practice: Always plan DNS changes ahead of time. Lower your TTL 24–48 hours before any migration, perform the switch, verify with multiple DNS servers, then restore the TTL. This approach minimizes downtime and user impact.

DNS Propagation Map

Use our free online tool - no signup required