DNS TTL & Propagation Calculator

Frequently Asked Questions

What is the standard DNS propagation time?

There is no fixed standard - propagation time equals the TTL. A 1-hour TTL can take up to 1 hour to propagate. The old 24-48 hour window referred to scheduled zone transfers, not modern authoritative DNS.

Why do some resolvers serve the old record longer than the TTL?

Some resolvers use serve-stale or lazy expiry to improve availability during authoritative server outages. Always treat the TTL as a minimum, not a maximum propagation bound.

What is the difference between TTL and propagation time?

TTL is a per-record cache lifetime setting. Propagation time is the real-world window during which some resolvers still serve the old record, bounded above by the TTL.

Should I set a very low TTL permanently for flexibility?

No. A permanently low TTL increases query load on authoritative servers and can trigger rate limiting. Keep a normal TTL outside of planned change windows.

Provided by AllCalculators.io
Free online calculators for everyday. No registration required.

Estimates for informational purposes only.

Important Disclaimer: Estimates for informational purposes only.

This calculator provides estimates for informational purposes only. Results are based on assumptions and may not reflect actual outcomes. Consult qualified professionals in relevant fields before making important decisions based on these results.

JavaScript is required to use the interactive calculator above. The questions and answers below remain readable without JavaScript.

How It Works

A DNS record's TTL (Time To Live) tells resolvers how long they may cache the answer. The worst-case propagation window is one full TTL: imagine a resolver caches the old record one second before you change it - it can keep serving the stale value for the entire TTL afterward.

This calculator converts your TTL to seconds, then given how long ago the change was made, computes the maximum remaining time any resolver could still serve the old record and whether the change has certainly fully propagated. It also shows the recommended low-TTL pre-change lead: lower the TTL to 300 seconds at least one full old-TTL period before the cutover, so by switch time every resolver is re-fetching every 5 minutes - turning a 1-hour blind window into a 5-minute one.

Use Cases

DNS administrators and DevOps engineers use this calculator to:

Plan zero-downtime server migrations by calculating how early to lower the TTL before the IP cutover.

Determine when it is safe to decommission an old IP address after an MX or A record change.

Estimate how long users may experience disruption after an emergency DNS change.

Build runbooks for CDN provider switches, failover events, and SSL certificate renewals requiring DNS changes.

Answer the question: how long must I wait after changing a record before I can be confident every user is hitting the new target?

Tips

Lower the TTL at least one full old-TTL period before the change - the low value itself is cached at the old TTL, so lowering it one minute before a cutover gives you no benefit.

Use 300 seconds (5 minutes) as the pre-change low TTL - this is the industry standard that balances quick propagation against increased resolver load.

Raise the TTL back after the change is confirmed stable - leaving it at 300 seconds permanently multiplies DNS query load and can increase costs for paid DNS providers.

Do not trust DNS checker tools as a guarantee - they sample a subset of resolvers; the worst case is still a full TTL, especially for ISP resolvers with large user populations.

Account for negative caching - NXDOMAIN responses are cached too, controlled by the SOA minimum TTL; plan accordingly when creating records that did not previously exist.

FAQ

What is the standard DNS propagation time?

There is no fixed standard - it is determined by the TTL. A record with a 1-hour TTL can take up to 1 hour to propagate after a change. A record with a 5-minute TTL can take up to 5 minutes. The concept of a fixed 24-48 hour propagation window is outdated and refers to the era of scheduled zone transfers, not modern authoritative DNS.

Why do some resolvers serve the old record longer than the TTL?

Some resolvers violate the TTL specification and serve records past their expiry (a feature called serve-stale or lazy expiry) to improve availability during authoritative server outages. Most enterprise and ISP resolvers comply correctly, but the TTL must always be treated as a minimum, not a maximum.

What is the difference between TTL and propagation time?

TTL is a per-record setting that controls cache lifetime. Propagation time is the observed real-world window during which some resolvers still serve the old record. They are related - propagation time is bounded above by the TTL - but propagation time also depends on when each resolver last refreshed its cache.

Should I set a very low TTL permanently for flexibility?

No. A permanently low TTL (30-60 seconds) significantly increases query load on authoritative servers, can trigger rate limiting, and makes your domain more expensive to operate on pay-per-query DNS services. Keep a normal TTL (1-24 hours) outside of planned change windows.

DNS TTL & Propagation Calculator

Frequently Asked Questions

Related Networking & IT Calculators