How Long Does DNS Propagation Take?
You've updated a DNS record — pointed your domain at a new host, changed a mail server — and now some visitors see the new site while others still land on the old one. This in-between state is DNS propagation, and the standard answer for how long it takes is "up to 48 hours." The more useful answer: it's controlled almost entirely by one setting, the record's TTL, and if you plan ahead you can cut a migration's effective propagation time to minutes. Here's how it actually works.
Why changes aren't instant
DNS doesn't push updates out to the world — the world pulls, and caches. When you change a record at your DNS provider, the authoritative nameserver starts answering with the new value immediately. But the resolvers between users and your nameserver (their ISP's resolver, public resolvers like 8.8.8.8, their OS and browser caches) keep serving the old cached answer until it expires. Propagation isn't one global event; it's thousands of independent caches timing out one by one.
TTL: the setting that controls everything
Every DNS record carries a TTL (time to live) — the number of seconds resolvers may cache it. A record with TTL 3600 can be served from cache for up to an hour after you change it; TTL 86400 means up to a day. This is why realistic propagation estimates range from minutes (low TTL) to 24–48 hours (long TTLs, plus a minority of resolvers that ignore TTLs and cache longer than they should).
The corollary is the single best migration trick: lower the TTL to 300 seconds a day or two before a planned change, while the old record is still in place. By cutover time, every cache holds the short-TTL version, and your actual switch propagates in about five minutes. Raise the TTL back afterward for normal cache efficiency.
Typical timelines by change type
A and CNAME record edits at the same DNS provider propagate within the record's TTL — often 5 minutes to a few hours. MX (mail) changes behave the same, though mail servers retry delivery, which masks brief inconsistency. Changing nameservers (moving DNS providers) is the slow one: the NS records at your registrar are cached by the TLD with TTLs commonly set at 24–48 hours, and you don't control that TTL. Full domain transfers between registrars can add further registry processing on top.
How to check propagation status
Because propagation is per-resolver, checking from your own machine tells you almost nothing — your own cache may be the stale one. A DNS propagation checker queries nameservers in many countries at once and shows which regions have the new value. Consistent new values everywhere means you're done; a mix means caches are still expiring; the old value everywhere means the change didn't take at the source, and you should re-check the record at your DNS provider.
When it seems stuck
If a change shows the old value globally hours after you made it, the usual suspects are: the record was edited at the wrong provider (the domain's actual nameservers point elsewhere — a WHOIS lookup shows which nameservers are live), a typo in the record, or a proxy/CDN layer like Cloudflare answering with its own addresses by design. If the world shows the new value but your machine doesn't, flush your local DNS cache and reboot your router.