How Long Does DNS Propagation Take?
Made a DNS change and wondering why it's not working yet? Here's everything you need to know about DNS propagation time and how to track it.
Quick Answer
DNS propagation typically takes 4-24 hours for most changes, though it can range from minutes to 72 hours. The main factor is your record's TTL (Time to Live) value — lower TTL means faster propagation. You can track real-time progress using DNSFly's propagation checker across 21 global servers.
In this article
What is DNS Propagation?
DNS propagation is the time it takes for DNS changes to be updated across all DNS servers on the internet. When you change your domain's DNS records (like pointing to a new web host), that change needs to spread from your DNS provider to thousands of DNS servers worldwide.
Think of it like updating your phone number in a phone book. It takes time for everyone to get the new edition with your updated number. During this time, some people might still have your old number while others have the new one.
This is why, after making DNS changes, some visitors might see your new website while others still see the old one. From my years in web hosting support, the most common DNS issue I saw was people not waiting long enough for propagation to complete.
How Long Does It Take?
The short answer: typically 24-48 hours, but it can range from a few minutes to 72 hours.
Typical Propagation Times
In practice, most DNS changes propagate to major regions within a few hours. The "48 hour" rule is often mentioned to account for the slowest DNS servers and heavy caching.
Factors That Affect Speed
Several factors determine how quickly your DNS changes spread:
TTL (Time to Live)
The most important factor. TTL tells DNS servers how long to cache your record. A TTL of 3600 means servers will cache your old record for up to 1 hour before checking for updates. Lower TTL = faster propagation.
ISP DNS Caching
Internet providers cache DNS records to speed up browsing. Some ISPs ignore TTL and cache records longer than specified, causing delays for their users.
Geographic Location
DNS servers closer to your DNS provider typically update faster. Remote regions or smaller ISPs may take longer to receive updates.
Record Type
Some record types propagate faster than others. A records (IP addresses) often propagate quickly, while MX records (email) might take longer due to how mail servers cache DNS.
How to Check Propagation Status
The best way to check DNS propagation is using a tool that queries multiple DNS servers around the world. This shows you exactly which regions have received your updated records.
Check Your DNS Propagation
Use DNSFly to check DNS propagation across 20+ global locations instantly. See which servers have your new records and which are still caching old data.
Check If Your Records Have Propagated — Launch Global CheckerWhen checking propagation, look for consistency across all locations. If most servers show your new record but a few show old data, propagation is still in progress - just wait a bit longer.
Tips to Speed Up Propagation
While you can't force DNS servers to update, you can minimize propagation time with these strategies:
Lower TTL Before Changes
24-48 hours before making DNS changes, lower your TTL to 300 seconds (5 minutes). This ensures old records expire quickly when you make the actual change.
Clear Local DNS Cache
Your computer caches DNS too. On Windows: ipconfig /flushdns. On Mac: sudo dscacheutil -flushcache.
Use Public DNS
Switch to Google DNS (8.8.8.8) or Cloudflare DNS (1.1.1.1). These update faster than most ISP DNS servers and respect TTL values.
Plan Ahead
Make DNS changes during low-traffic periods and keep both old and new servers running until propagation completes.
Real-World Examples
Averages are useful, but the actual wait depends on what you changed and how your TTL was set beforehand. Here are timelines that match what you'll typically see in practice.
| Change | TTL beforehand | Typical wait |
|---|---|---|
| Point A record to a new host | 300s (5 min) | Minutes to ~1 hour |
| Point A record to a new host | 86400s (24h) | Up to 24 hours |
| Update MX records (email) | 3600s (1h) | 1 to several hours |
| Change nameservers | registrar-controlled | Often 24 to 48 hours |
The pattern is consistent: the record's TTL sets the ceiling on how long a cached copy survives, and nameserver changes are slowest because they depend on the registrar and the parent TLD, not just your zone. To watch any of these complete in real time, run a propagation check across global servers.
Common Mistakes That Slow It Down
Most "propagation is taking forever" complaints come down to a handful of avoidable mistakes. None of them actually speed up the global DNS, but they make the wait feel far longer than it is.
Not lowering the TTL first
If the old record had a 24-hour TTL, resolvers can hold it for a full day no matter how fast you make the change. Lower the TTL a day in advance so the old copy expires quickly.
Testing only from your own machine
Your computer and router cache DNS, so you may see the old record long after it has propagated elsewhere. Flush your DNS cache or test from a global checker instead.
Changing records again out of panic
Editing the record repeatedly doesn't push it out faster. It just resets your own confidence in what's live. Make the change once, then wait and verify.
Changing nameservers and records at the same time
If you move nameservers and edit records together, it's hard to tell which change is still propagating. Move nameservers first, confirm they've settled, then adjust individual records.
Tip: If a change is urgent and you forgot to lower the TTL, switching your own device to a public resolver like 1.1.1.1 or 8.8.8.8 often shows the new record sooner, because those resolvers honor TTLs tightly and may not have cached your old value.