March 26, 20265 min read

DNS Propagation Time Estimator

Estimate how long DNS changes take to propagate globally. Understand TTL, resolver caching, and how to minimize downtime during domain migrations.

networking dns propagation domain calchub

"I updated the DNS record, why isn't it working yet?" This question gets asked thousands of times a day by developers, sysadmins, and everyone who's ever moved a website. DNS propagation is mostly a waiting game — but understanding what controls the wait time (and how to shorten it) makes domain migrations much less stressful.

How DNS Propagation Actually Works

When you update a DNS record with your registrar or DNS provider, the change is immediate at the authoritative nameserver. But the internet doesn't query your authoritative server directly for every lookup — it queries recursive resolvers (like your ISP's DNS, or 8.8.8.8), and those resolvers cache answers according to the record's TTL value.

The propagation timeline:

You update the record — authoritative server reflects the change instantly
Cached answers at resolvers across the world continue serving the old value until their TTL expires
As each resolver's cache expires, it fetches the fresh answer from your authoritative server
After the longest TTL worth of time, essentially all resolvers have the new answer

TTL: The Only Number That Matters

TTL (Time To Live) is set on the DNS record and tells resolvers how many seconds to cache the answer. Common values:

TTL	Cache Duration	Best For
60s	1 minute	Active migration (change it right now)
300s	5 minutes	Frequent changes expected
3600s	1 hour	Typical production records
86400s	24 hours	Stable records, rarely change
604800s	7 days	Very stable, no plans to change

The CalcHub DNS Propagation Calculator works backward: enter your current TTL and the calculator tells you the maximum propagation window when you make a change. Enter a new TTL and it shows how long you need to wait before that shorter TTL takes effect everywhere.

The Smart Migration Strategy

Here's the professional way to do a zero-downtime domain migration:

Lower your TTL now — Set TTL to 300s (5 minutes) at least 2× current TTL before the change. Wait for the old TTL to expire so all resolvers pick up the low TTL.
Make the change — Switch the A/CNAME record. Worst case, resolvers that just cached the old answer will have it for 5 minutes.
Monitor propagation — Check resolution from multiple global vantage points.
Raise TTL back — Once the migration is stable, raise TTL back to 3600s or higher.

If your current TTL is 86400 seconds (24 hours), you need to lower it 24 hours before the actual migration cutover — not the morning of.

Record Types and Propagation

Not all records behave the same:

Record Type	Typical TTL	Notes
A / AAAA	3600s	Most common, carries IP address
CNAME	3600s	Alias; resolver follows chain
MX	3600s	Email routing; be careful here
TXT	3600s	SPF, DKIM, domain verification
NS	172800s	Nameserver changes propagate slowest
SOA	3600s	Zone authority info

NS record changes (switching DNS providers) are the slowest to propagate because they involve the parent zone (like .com) caching the delegation, and those TTLs are set by the registry, not you.

Tips

Don't trust browser cache. Your browser has its own DNS cache that ignores TTL and keeps records for minutes or hours. Use ipconfig /flushdns (Windows) or sudo dscacheutil -flushcache (macOS) when testing propagation on your own machine.
Test from multiple locations. Use tools like DNS Checker or the CalcHub propagation tool to query from resolvers in North America, Europe, and Asia simultaneously.
MX changes need extra caution. Email queues. If you change your MX records and something goes wrong, in-flight email can get lost or deferred for hours. Always set up the new mail server and verify it's receiving before cutting over.

How long does DNS propagation really take in 2026?

With a 300s TTL, propagation is effectively complete in 5–15 minutes worldwide. With a 3600s TTL, expect 1–2 hours for 99% of resolvers. The "24–48 hours" figure you see cited is outdated and only applies when someone didn't lower their TTL before migrating.

Why does my DNS change show the new value on my phone but not my laptop?

Different devices use different resolvers. Your phone might be querying 8.8.8.8 (Google DNS), which already has the new record. Your laptop might be querying your ISP's resolver, which still has the old answer cached. Clearing local DNS cache and switching resolvers can test this.

Can I force propagation faster?

You can't force other resolvers to flush their cache. But if you control the environment (like a corporate network), you can configure local resolvers to query authoritative servers more aggressively. For public internet users, the TTL is the only lever you have.

Network Uptime Calculator — plan downtime windows around migrations
IP Converter Calculator — understand IP address changes during migrations
Latency Calculator — check performance after DNS changes