You have just pointed your domain at a new server, or switched email providers, and some people see the change while others still reach the old setup. That in-between period is called DNS propagation. It is normal, it is temporary, and once you understand what causes it you can make it far shorter next time.
What DNS propagation actually is
When someone visits your website, their device does not ask your domain's DNS servers directly every time. It asks a resolver, usually run by their internet provider or by a public service such as Google Public DNS or Cloudflare. The resolver fetches the answer from your domain's authoritative name servers once, then keeps a copy in its cache so it can answer the next visitor instantly.
Each DNS record carries a time to live (TTL), a number of seconds that tells resolvers how long they may keep that cached copy. Until the TTL runs out, a resolver keeps handing out the old answer, even if you have already changed the record. Because thousands of resolvers around the world cached your record at different moments, they all expire at different times. "Propagation" is simply those caches emptying one by one.
Nothing is being pushed out across the internet. Your new record is live on your name servers the moment you save it; the delay is entirely down to other servers remembering the old one.
How long does DNS propagation take?
In practice, most changes are visible to most people within a few minutes to a few hours. The often-quoted "up to 48 hours" is a safe upper bound rather than a typical figure. What decides the real duration:
- The TTL of the old record. If the old A record had a TTL of 86,400 seconds (24 hours), a resolver that cached it just before your change may hold it for a full day.
- Name server changes take longer. Changing the name servers for a domain involves the registry for the domain ending (such as .com or .in). Those delegation records often have TTLs of one to two days.
- Some resolvers ignore short TTLs. A minority of internet providers enforce a minimum cache time, so a few users may lag behind everyone else.
- Local caches. Browsers, operating systems and office routers keep their own small caches, so one person's computer can show the old site after the wider internet has moved on.
How to check DNS propagation
Because the answer depends on which resolver you ask, checking from your own computer only tells you what your own provider sees. A propagation checker asks many public resolvers at once and compares their answers.
Our free DNS propagation checker queries public DNS servers run by different operators across North America, Europe and Asia. When every server returns your new value, the change has spread. If you want to see the full set of records for one resolver, including the TTL each is currently counting down, use the DNS lookup tool and pick the server you want to ask.
How to make DNS changes propagate faster
You cannot force other people's resolvers to forget your old record, but you can make sure they only remember it briefly:
- Lower the TTL in advance. At least one full old-TTL period before the change (a day before is a good habit), reduce the TTL on the records you plan to change to 300 seconds.
- Make the change. Because resolvers now only cache for five minutes, the new value reaches nearly everyone within minutes.
- Raise the TTL again. Once you are happy the new setup works, put the TTL back to an hour or more. Longer TTLs mean fewer lookups and slightly faster page loads for visitors.
For moves where both old and new servers can run side by side, keep the old server online until propagation is complete. Visitors still on cached records then see a working site instead of an error.
Clearing your own cache
If the checker shows the new value everywhere but your own browser still shows the old site, the stale copy is local. Restarting the browser usually clears it. On Windows you can also run ipconfig /flushdns; on macOS, sudo dscacheutil -flushcache. Restarting your office router clears its cache too.
When "propagation" is not the problem
If a change still has not appeared anywhere after the old TTL has passed, it is probably not a caching delay. Common causes are editing the record at the wrong DNS provider (the one your domain is no longer using), a typo in the value, or a conflicting record such as a CNAME that overrides your A record. Check which name servers your domain actually uses with a WHOIS lookup, and make sure that is where you made the change.
Key takeaways
- DNS propagation is the time it takes for cached copies of your old record to expire.
- It is governed mainly by the TTL; most changes spread within hours, and name server changes can take up to two days.
- Lower the TTL a day before planned changes to make them near-instant.
- Use a multi-server checker, not your own browser, to see whether a change has really spread.