DNS Propagation Explained: Why Your Domain Changes Take Time
· 5 min read
You point your domain at a new server, your own browser shows the new site — and a friend across the world still lands on the old one. Welcome to "DNS propagation," the most misunderstood waiting game on the internet. The twist: nothing is actually propagating.
There is no broadcast
DNS changes aren't pushed out to the world's servers. When you update a record, only your domain's authoritative nameservers change — instantly. Everyone else finds out lazily: resolvers (your ISP's, Google's 8.8.8.8, Cloudflare's 1.1.1.1) cache each answer they fetch and keep serving the cached copy until it expires. What looks like slow propagation is really thousands of independent caches counting down at different times.
TTL is the countdown
Every DNS record carries a TTL (time to live) — the number of seconds a resolver may cache it. With a TTL of 3600, a resolver that fetched your record one minute before your change will serve the stale answer for another 59 minutes. That's why two people see different sites: their resolvers cached at different moments.
The practical trick for migrations: lower the TTL in advance. Drop it to 300 seconds a day before the move (while the old TTL is still draining), make the change, confirm it everywhere, then raise the TTL back.
Checking where your change has landed
Testing from your own machine proves nothing — your OS and browser have caches of their own, on top of your resolver's. What you want is the view from many resolvers at once. Our DNS propagation checker queries your record against dozens of public DNS servers around the world in one shot, so you can watch a change roll out resolver by resolver instead of asking friends to "try it now."
For a single authoritative answer — including MX, NS and TXT records — the resolve tool shows what a fresh, uncached query returns right now.
When it's not propagation at all
- Wrong nameservers: if the change was made at your old DNS host but the domain points at a new one (or vice versa), no amount of waiting helps. Check the NS records first.
- Typos and missing trailing dots: a CNAME of
www.example.cominstead ofwww.example.com.at some providers quietly becomeswww.example.com.example.com. - Registrar-level caching: nameserver (NS) changes at the registry itself commonly carry TTLs of 24–48 hours — the one case where a long wait is genuinely built in.
- Local caches: flush your OS cache and restart the browser before concluding anything from your own machine.
The takeaway
DNS changes are instant at the source and stale everywhere else, for at most one TTL. Lower the TTL before you migrate, verify with a multi-server DNS check rather than your own browser, and the "propagation" wait becomes a countdown you control.