How long does DNS propagation take?
What affects propagation time
Propagation isn't a single event; it's the time it takes for caches around the world to expire and fetch the new records. The TTL value you set on a record determines how long resolvers keep the old data. If your TTL is 3600 seconds (1 hour), resolvers may hold the old record for up to an hour after you make a change.
Some ISPs and public resolvers ignore TTLs or have their own minimums, which can extend propagation. Also, if you change nameservers at your registrar, the registry may take time to update the delegation, adding to the delay.
Typical timeframes
For a simple A record change with a low TTL (e.g., 300 seconds), most users see the new IP within 5–30 minutes. For nameserver changes, it can take 24–48 hours because the old nameservers may still be cached. If you're moving to a new hosting provider, expect up to 72 hours in rare cases.
You can check propagation using online tools like whatsmydns.net, which queries resolvers worldwide. Remember that your own computer might have a longer cache, so flush your DNS cache to see changes faster.
- TTL of 300 seconds: changes visible in ~5–30 minutes.
- TTL of 3600 seconds: changes visible in ~1–2 hours.
- Nameserver changes: often 24–48 hours.
- Registry updates: can add a few hours.
- Local cache: flush it to avoid confusion.
Common mistakes
- Expecting instant updates; caching is designed to reduce load, so delays are normal.
- Forgetting that your own device may cache DNS longer than the TTL.
- Assuming all resolvers respect TTL; some override it with their own minimums.
