IPHere.org › DNS propagation

What is DNS propagation?

You changed a DNS record and some people see the new result while others still see the old one. That delay is DNS propagation.

What is happening

DNS is a distributed system. When someone looks up your domain, their resolver (at their ISP, or a public one like Cloudflare or Google) asks your authoritative name servers and then caches the answer for the length of the record's TTL (time to live). Until that cached copy expires, the resolver keeps serving the old value. "Propagation" is simply all of those caches expiring at different times.

How long does it take?

ChangeTypical time
Record edit with a short TTL (300s)Minutes
Record edit with a 1-hour TTLUp to an hour
Record edit with a 24-hour TTLUp to a day
Changing name servers at the registrarHours, sometimes up to 48 hours

How to check propagation

  1. Open the DNS checker.
  2. Enter your domain and the record type you changed (A, MX, TXT, and so on).
  3. Compare results from Cloudflare, Google and NextDNS. If they all show the new value, propagation has largely completed.

If the resolvers disagree, the ones showing old data have not expired their cache yet. You can also look at the TTL numbers: that is roughly the longest it can take.

How to make DNS changes smoother

See also the DNS record types guide.

Frequently asked questions

Why do I still see the old website after changing DNS?

Your resolver, operating system or browser is still using a cached copy. Wait out the TTL or flush your caches.

Is DNS propagation really global?

Not literally. There is no push; it is just many independent caches expiring on their own schedules.

See your own IP addressCheck it now or look up a domain with the free DNS checker.

Related guides

An Matrix Anchor free tool. We build websites, apps and VoIP for businesses.