If you just updated a DNS record and the change isn’t live yet, you’re probably waiting on DNS propagation. It’s normal, and it’s not instant. This guide explains what’s happening, how long it usually takes, and how to check it fast.
What is DNS propagation?
DNS is a global directory. When you change a DNS record (like A, CNAME, or MX), that update needs to spread across DNS resolvers worldwide. Each resolver caches results for a period of time (TTL), so some users see the new record while others still see the old one.
How long does DNS propagation take?
Most changes update within minutes to a few hours, but a full propagation can take up to 24–48 hours depending on:
- TTL values (Time To Live)
- DNS provider speed
- ISP resolver cache behavior
- Local device or router cache
Lower TTL = faster updates, but also more DNS queries.
How to check propagation fast
Use our DNS Propagation Tool to check how your records look from multiple regions. It shows which locations still have the old DNS data and which have the new.
Typical propagation scenarios
1. New website launch
- Old A record points to the previous server
- New record points to your new host
- Users may land on either server until caches expire
2. Email migration
- MX record changes
- Some senders still deliver to the old provider
- Use temporary forwarding if possible
3. CDN or load balancer changes
- CNAME updates can take time
- Expect region‑by‑region updates
How to speed it up
You can’t force everyone’s DNS cache to update instantly, but you can reduce delays:
- Lower TTL 24–48 hours before a planned change
- Keep the old server running until propagation completes
- Flush your local DNS cache after the change
Flush local DNS cache (quick fixes)
If you’re still seeing the old site, clear your local cache:
- Windows:
ipconfig /flushdns - macOS:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder - Linux:
sudo resolvectl flush-caches
Troubleshooting checklist
- Verify the record in your DNS provider
- Use our DNS Lookup Tool to confirm authoritative results
- Check propagation in multiple regions
- Wait for TTL to expire
Summary
DNS propagation is normal and usually quick, but it depends on TTL and resolver cache behavior. The fastest way to track progress is using a multi‑region checker and keeping old infrastructure online until the new records are fully live.