What DNS propagation actually means
When you edit a record at your DNS provider, the authoritative nameservers update immediately. But most users don't query authoritative servers directly — they ask a recursive resolver (like 8.8.8.8 or 1.1.1.1) that caches the previous answer until its TTL expires.
- Authoritative update — your provider publishes the new record right away.
- Recursive cache — resolvers keep the old answer for up to the record's TTL.
- Global spread — different cities and ISPs refresh at different times, so propagation is never instant everywhere.
How TTL controls propagation speed
TTL (time to live) tells resolvers how long they may cache an answer. A record with TTL 300 (five minutes) propagates much faster than one with TTL 86400 (24 hours). Before a planned migration, lower TTLs 24–48 hours ahead so caches expire quickly when you flip the record.
After the change, expect full global propagation within roughly one to two TTL cycles — not a fixed 24 or 48 hours. Short TTLs (60–300s) often converge in minutes; long TTLs can take a day or more.
How to check if DNS has propagated
Querying from your laptop only shows what your local resolver cached. To see the real picture, check from multiple geographic locations and compare answers across public resolvers.
- Use a global propagation checker that resolves from many cities in parallel.
- Compare Cloudflare, Google, and Quad9 — if all three match the authoritative answer, propagation is effectively complete.
- Re-check after one TTL period if some locations still show stale data.
Check propagation with DNSfish
DNSfish resolves your domain from 16 probe cities across six continents and compares answers from nine public resolvers side by side. Differences are highlighted so you can tell a slow cache from a misconfiguration.