What Is DNS Propagation?

DNS propagation is the delay you wait after changing a DNS record while the old, cached version expires on servers around the world. Despite the name, nothing is actively pushed out. Each server keeps its cached answer until that record's TTL, its time to live, runs out, then fetches the new one. In practice the wait runs from a few minutes to about 48 hours.

Why do DNS changes take time?

DNS changes take time because the internet caches DNS records to stay fast, and those caches only refresh when they expire. Nothing tells them a record has changed.

Every DNS record carries a TTL, a number of seconds that tells resolvers how long to hold the answer before asking again. Until that timer runs out, a resolver keeps serving the old value, even after you have updated it at the source.

This is why "propagation" is a slightly misleading word. As one DNS explainer puts it, "the authoritative nameserver never pushes updates, it just replies with the current record when it receives a query" (Julia Evans, December 2021).

What you are really waiting for is those cached records to expire, not a change spreading outward.

How long does DNS propagation take?

DNS propagation usually takes from a few minutes to about 48 hours. Namecheap's guidance says a nameserver change may take up to 24-48 hours for the change to take effect (Namecheap knowledgebase). Google's DNS basics page says a record with a day-long TTL will take up to 24 hours to go into effect (Google Workspace Admin Help, updated September 2026). The single biggest factor is the TTL set on the record before you changed it.

A record with a low TTL, say 300 seconds, refreshes within minutes. One set to 86,400 seconds, a full day, can leave some visitors seeing the old site for that long.

TTL on the record	Longest a cache holds the old answer
300 seconds (5 minutes)	A few minutes
3,600 seconds (1 hour)	About an hour
86,400 seconds (24 hours)	Up to a full day

Source: each record's TTL is the maximum time a resolver caches it, per the DNS standard.

Different people also see the change at different times. Your office may load the new site while a customer across town still hits the old one, because their resolver cached the record at a different moment.

How can you make DNS changes faster?

You can speed up a DNS change by lowering the record's TTL well before you make it. The lower TTL has to take effect first, so plan ahead.

The reliable pattern is simple. A day or two before a planned move, drop the TTL on the records you will change to a few minutes. Make the actual change at the planned time, and most resolvers pick it up quickly. Raise the TTL again afterward for performance.

The same TTL wait applies to records for email or an SSL certificate, so plan those changes together rather than one at a time.

A pattern we see is a business that cannot say who controls its DNS until a move is due and nobody has the login. Lowering a TTL is easy; finding the right account under time pressure is the part that hurts. This is one reason we register domains and DNS in the client's name at their registrar, never our own.

How do you check if a change has propagated?

You check propagation by querying DNS from more than one place, since your own computer may still be caching the old answer. A global DNS checker shows what resolvers in different regions currently return.

Online tools that query many locations at once give the quickest view. Command-line tools like dig or nslookup check a specific resolver.

If some locations show the new record and others the old, the change is mid-flight, and you are waiting on the slower caches to expire. Clearing your local DNS cache helps rule out a stale answer on your own machine.

If nothing loads at all, in every location, that points to a host or server outage rather than propagation.

Frequently asked questions

How long does DNS propagation really take?

Usually a few minutes to 48 hours. The record's TTL sets the ceiling: a low TTL clears in minutes, a high one can linger for a day or more. During the window, some visitors see the new record while others still get the cached old one. That is normal and resolves on its own.

Does DNS actually "propagate"?

Not in the way the word suggests. No central system pushes your change outward. Each resolver holds its cached copy of a record until the TTL expires, then asks for the current value. So the wait is cached answers timing out, not data spreading across the internet. Understanding this saves a lot of needless worry during a move.

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

Because a resolver between you and the site is still serving the cached record until its TTL expires. Your browser, your operating system, or your internet provider may hold the old answer. Clearing your local DNS cache and trying another network or device usually confirms whether the change is live. If a global checker shows the new value, you are just waiting on your own cache.

Can I speed up DNS propagation?

You cannot force other servers to drop a cached record early, but you can prepare. Lower the TTL on the records a day or two before you change them, so caches hold the answer for only a few minutes around the switch. Raise it again afterward. There is no button to flush the whole internet's cache at once.

Does DNS propagation affect my email too?

Yes, if you change mail-related records. Your MX records control where email is delivered, and they cache and expire on a TTL just like your website's records. During a mail change, some messages may route to the old server until the change is fully live. That is why email moves are planned carefully, to avoid lost mail.

Planning DNS changes without the guesswork

Storming Solutions builds and maintains websites for Malaysian businesses. DNS moves are part of the plumbing we handle, so a launch or migration does not turn into a day of downtime. We lower TTLs in advance and keep every account in the client's name, so the change is quick and you are never locked out.

Facing a site move, a new CDN, or an email switch and unsure how long it will take? Message us on WhatsApp, check who controls your hosting and DNS, or ask about our web development work.