Guide
How long does DNS propagation take?
What really happens when you change a record, why it takes time, and how to speed it up.
Updated
Short answer: a changed record reaches everyone within its old TTL, which is usually between five minutes and a day. Changing a domain’s name servers can take up to 48 hours. “Propagation” is a misleading word, though: nothing is pushed anywhere. Understanding what really happens is what lets you make changes fast.
What actually happens
Your records live on your DNS host’s authoritative name servers. A change there takes effect as soon as you save it (or within a minute or two, for some hosts).
But people don’t ask your name servers directly. Their devices ask a resolver: their ISP’s, or a public one like Google’s 8.8.8.8 or Cloudflare’s 1.1.1.1. The resolver fetches the record once, then keeps it in its cache for as long as the record’s TTL (time to live) allows, answering everyone else from the cache. Only when the TTL runs out does it ask again and get the new answer.
So after a change, each resolver keeps serving the old answer until its own cached copy expires. Different resolvers fetched it at different times, so they switch at different times. That patchwork is what a propagation checker shows.
How long, by type of change
| Change | Worst case |
|---|---|
| Edit an existing record | The record’s old TTL |
| Add a record that didn’t exist | The zone’s negative-cache time (the last number in its SOA record), if someone looked it up before you added it |
| Change name servers at the registrar | Up to 48 hours: the registry’s NS records for .com, for example, have a TTL of two days |
| Register a new domain | Usually minutes |
Making planned changes fast
- Lower the TTL first. At least one old-TTL period before the change (a day before, if the TTL is a day), set the record’s TTL to 300 seconds.
- Make the change. Resolvers now hold it for at most five minutes, so within five minutes everyone has the new answer.
- Check it. Run the propagation checker. When every resolver matches your authoritative servers, you’re done.
- Raise the TTL again, to an hour or a day, so resolvers cache it and lookups stay fast.
When it seems stuck
- The authoritative servers show the old record: the change wasn’t saved, or you edited the zone at a DNS host the domain doesn’t use. Check which name servers the domain really has with the WHOIS lookup.
- The authoritative servers disagree with each other: the zone isn’t copied to all of them. Contact your DNS host.
- Every resolver is right but your computer isn’t: your own device or browser
has cached it. Flush the DNS cache (
ipconfig /flushdnson Windows), or try another network. - Answers differ for a big site: large sites and CDNs give different addresses in different places on purpose. That’s not a propagation problem.
Related tools
All toolsDNS Propagation Checker
Ask 20 public DNS resolvers and the domain’s own servers, and see who has your change yet.
DNS Lookup
Look up A, AAAA, CNAME, MX, NS, TXT, SOA, CAA and SRV records for any domain.
WHOIS Domain Lookup
Registrar, creation and expiry dates, status and name servers, from the registry itself.
More guides
- SPF, DKIM and DMARC explained What each record does, how they work together, and the order to set them up in.
- Gmail, Yahoo and Microsoft sender requirements What the big mailbox providers require of senders, and how to check you meet it.
- Fix “SPF permerror: too many DNS lookups” Why SPF stops at 10 lookups, how to count yours, and four ways to get under the limit.