DNS Propagation: Why Your Changes Take Time (and How to Check)
You updated your DNS records. You saved. You waited. And nothing happened. Your website still points to the old server. Your email is still broken. Welcome to DNS propagation — the most common source of confusion in domain management.
What DNS propagation actually means
DNS propagation is not a single event. It is the gradual process by which your updated DNS records spread across the global network of DNS resolvers and caches. When you change a record at your DNS provider, that change takes effect on the authoritative name server immediately. But every other DNS server in the world — your ISP's resolver, Google DNS, Cloudflare DNS, corporate DNS servers — still has the old record cached.
Each cached copy must expire before that resolver fetches the updated record. This is why propagation is not instant — it depends on when each cache expires.
TTL: the timer behind propagation
Every DNS record has a TTL (Time to Live) value, measured in seconds. The TTL tells resolvers how long they may cache that record before they must check for an update.
| TTL Value | Cache Duration | Typical Use |
|---|---|---|
| 300 | 5 minutes | During active migrations |
| 3600 | 1 hour | Standard for most records |
| 14400 | 4 hours | Common default for many providers |
| 86400 | 24 hours | Stable records that rarely change |
If your A record has a TTL of 86400 (24 hours), and a resolver cached it 23 hours ago, that resolver will continue serving the old IP address for another hour — even though you already updated it.
The propagation trick: lower your TTL before making changes
This is the single most useful technique for reducing propagation time. At least 24-48 hours before you plan to change a DNS record, lower its TTL to 300 seconds (5 minutes). Wait for the old TTL period to pass so all caches pick up the short TTL. Then make your actual change. Now every resolver will check for updates every 5 minutes instead of every 24 hours.
Migration timeline example
- 48 hours before: Lower TTL from 86400 to 300
- 24 hours before: Verify the low TTL is being served (check with ZonePeek)
- Migration time: Update the record to the new value
- 5-15 minutes later: Most resolvers now serve the new record
- After confirming: Raise TTL back to 3600 or higher
How to check propagation status
The most reliable way to check propagation is to query multiple DNS resolvers and compare results. If Google DNS and Cloudflare DNS both return your new record, propagation is well underway.
With ZonePeek, you can do this in seconds: look up your domain on Google DNS, then switch to Cloudflare DNS and look it up again. If both show the updated record, the change has reached the two largest public resolvers in the world.
Pay attention to the TTL value shown in the results. If the TTL is counting down (e.g., showing 1847 instead of 3600), it means the resolver cached the record some time ago and the cache will expire when the counter reaches zero.
Why propagation seems inconsistent
You might see the new record on your phone but the old one on your laptop. This is because each device may use a different DNS resolver, and each resolver has its own cache. Your phone might use Cloudflare DNS while your laptop uses your ISP's resolver — and they cached the record at different times.
Some ISP resolvers also ignore TTL values and cache records longer than specified. This is technically incorrect behavior, but it happens. There is nothing you can do about it except wait.
Common propagation issues and fixes
“I changed my A record but the site still shows the old server”
Check the TTL. If it is 86400, you may need to wait up to 24 hours. Clear your browser cache and try a different device or network to rule out local caching.
“Google DNS shows the new record but Cloudflare does not”
They cached the record at different times. Wait for the TTL to expire on Cloudflare. You can track the countdown by checking the TTL in the response.
“It has been 48 hours and my ISP still shows the old record”
Some ISP resolvers cache aggressively. Try switching your device to use Google DNS (8.8.8.8) or Cloudflare DNS (1.1.1.1) directly. This bypasses your ISP's cache entirely.
Key takeaways
- DNS propagation is cache expiry, not a broadcast — each resolver updates independently
- TTL controls how long records are cached — lower TTL before changes, raise after
- Check multiple resolvers (Google DNS, Cloudflare DNS) to track propagation progress
- Browser and OS caches can make it seem like propagation is slower than it is
- Full propagation across all resolvers worldwide typically takes 15 minutes to 48 hours