DNS Propagation — What It Is and How Long It Takes

You updated your DNS records. The nameserver shows the new values. But your site still points to the old server, your colleague sees the new one, and your client sees something completely different. This is DNS propagation — one of the most confusing aspects of managing web infrastructure.

Check how your domain resolves right now using our WHOIS Lookup tool.

DNS is a distributed caching system. When you change a record, the change is immediate on your authoritative nameserver. But thousands of recursive resolvers around the world — operated by ISPs, companies, and public DNS services — have your old record cached. They don't check for updates until the TTL expires.

There is no push mechanism in DNS. You cannot force all resolvers to refresh simultaneously. You control only how long they cache your records through TTL values.

It depends entirely on your TTL settings.

If your TTL was 86400 (24 hours) when you made the change, resolvers that cached your record just before the change will serve the old value for up to 24 hours. If your TTL was 300 (5 minutes), propagation completes within minutes.

The "24-48 hours" estimate you often see comes from the industry default of 24-hour TTLs. It is not a fixed property of DNS itself.

Lower your TTL before making changes — not after.

1. Lower TTL to 300 seconds at least 24-48 hours before the planned change 2. Wait for the current high TTL to expire everywhere 3. Make your DNS change 4. Propagation now completes in 5-10 minutes for most resolvers 5. After the change is confirmed stable, raise TTL back to 3600 or 86400

This is the single most impactful thing you can do to reduce downtime during migrations. Many teams skip this step and then wait 24 hours unnecessarily.

Your browser, your colleague, and your client each use different recursive resolvers. Your ISP resolver, Cloudflare 1.1.1.1, Google 8.8.8.8, and corporate DNS servers all have independent caches with independent TTL timers.

Test from multiple resolvers: dig @8.8.8.8 yourdomain.com A queries Google DNS specifically. Compare results from 8.8.8.8, 1.1.1.1, and 9.9.9.9 to understand propagation status.