How Long Does DNS Propagation Take?
DNS propagation is the time it takes for DNS changes to spread across resolvers worldwide. It can be as fast as a few minutes or as slow as 48 hours, depending on TTL values and how resolvers handle their caches.
The Short Answer
- Best case: A few minutes (if old TTL was already low)
- Typical case: 1–4 hours (TTL of 3600)
- Worst case: Up to 48 hours (high TTL, slow resolvers, ISP caching)
Why DNS Takes Time to Propagate
DNS is a distributed, cached system. When you change a DNS record, the authoritative nameserver is updated instantly — but resolvers around the world continue serving their cached copy until the TTL expires.
Example: If your A record has a TTL of 3600 (1 hour), and a resolver cached it 1 minute before you made the change, that resolver will serve the old IP for another 59 minutes before fetching the new one.
The Propagation Process
- You update a DNS record at your authoritative nameserver
- The change is immediately live at your nameserver
- But resolvers worldwide are still caching the old record
- Each resolver independently waits for its cached TTL to expire
- When the TTL expires, it queries the authoritative nameserver and gets the new record
- Eventually, all resolvers have the new record — propagation is complete
What Affects Propagation Speed
| Factor | Impact |
|---|---|
| Old record TTL | Most important — high TTL = slow propagation |
| New record TTL | Determines refresh rate after propagation |
| ISP resolver behavior | Some ISPs ignore TTL and cache longer (rare) |
| CDN / proxy caching | CDNs may cache DNS independently |
| Browser DNS caching | Chrome caches DNS for ~1 minute regardless of TTL |
How to Speed Up Propagation
The key technique: lower your TTL before making changes.
- 48 hours before: Change TTL to 300 seconds (5 minutes)
- Wait 48 hours (so old high-TTL caches expire globally)
- Make your DNS change
- Propagation now happens in under 5 minutes for most resolvers
- After confirming everything works, raise TTL back to 3600
Why You Might See Different Results from Different Locations
Because each resolver independently caches and refreshes DNS records, different parts of the world see different results during propagation. A resolver in Japan may still have the old IP while a resolver in Europe has already picked up the new one.
This is why checking propagation from multiple locations is important after a DNS change.
Myth: "Wait 48 hours for DNS propagation"
The "48 hours" advice is outdated. If you lower your TTL beforehand, propagation happens in minutes, not days. The 48-hour estimate assumes a maximum TTL of 172800 seconds (2 days) — very few records use TTLs this high in practice.
Check DNS Propagation Worldwide
See the theory in practice — run a DNS Propagation Checker for your own domain.