What is DNS Propagation?

DNS propagation happens every time you register a domain or point one at a new server: your new records are published immediately, but resolvers across the Domain Name System (DNS) may keep serving the old, cached answers until they expire, so the change doesn’t take effect everywhere at once.

The DNS uses a collection of servers that store records mapping each domain name to the address it points to. (Who owns a domain is separate registration data you look up through WHOIS, not something DNS servers store.) Nothing is pushed out to those servers when you make a change. Resolvers across the internet fetch your records on demand and cache them for the record’s TTL (time to live), so an update only takes full effect once every cached copy of the old record has expired.

The DNS propagation process

When someone visits your domain, their device asks a DNS resolver, usually run by their internet service provider (ISP), for the matching IP address. The resolver fetches the answer from your domain’s authoritative nameserver, then caches it for the record’s TTL so it doesn’t have to ask again. Your change reaches a visitor only once their resolver’s cached copy expires and a fresh answer gets fetched. Millions of caches expire at different moments, so the change rolls out gradually: one visitor sees the new site while another still lands on the old one.

Two things stretch the wait. Some ISP resolvers ignore TTLs and hold answers longer than they should. And if a name was queried before its record existed, resolvers may cache the “no such record” answer for a while, a behavior called negative caching. A brand-new domain nobody has queried before, though, often resolves right away: there are no cached copies waiting to expire.

DNS propagation timing

Changes often finish within a few hours, but the standard guidance is to allow 24 to 48 hours, and in some cases a few days, before assuming something is wrong. IBM’s DNS propagation explainer puts the general range at between a few hours and a few days. What you changed sets the timescale:

• A change to an existing record (an A record, CNAME, or MX): up to that record’s TTL, often minutes to a few hours.
• A nameserver change: commonly 24 to 48 hours, because the nameserver records published at the TLD level are cached longer than most records. Our guide to nameservers vs. DNS covers this case in depth.
• A brand-new registration: usually fast, since no resolver holds old data for the name.

Here’s the math on a record change: say your A record has a 4-hour TTL and you point it at a new IP address at 2 p.m. A resolver that cached the old answer at 1:59 p.m. can keep sending its users to the old server until almost 6 p.m. That isn’t a broken setup; it’s caching working as designed. The blanket advice most registrars give, to allow 24 to 48 hours, exists to cover the slowest cases.

Reducing propagation time

You can shorten propagation before a change, not after it. Ahead of a planned cutover, lower the record’s TTL (to 300 seconds, for example), then wait at least one full cycle of the old TTL before you change the record, so every cache has picked up the short value. The rule is simple: if the record’s TTL is 24 hours, lower it more than 24 hours before the change; if it’s 4 hours, allow at least 4 hours. Then make the change: caches now refresh within minutes instead of hours. Restore the higher TTL once the new record resolves everywhere.

After the change is live, your options shrink. You can’t flush other people’s resolvers; you can only flush your own device’s DNS cache. And a nameserver change can’t be accelerated this way, because the caching at the registry level isn’t under your control. If a cutover is coming, check the record’s current TTL and lower it at least one full TTL period in advance. It’s the one lever that reliably shortens the wait.

Propagation outside web hosting

In general use, to propagate means to spread or reproduce. Gardeners propagate plants from cuttings, radio waves propagate through the air, and rumors propagate through a crowd. In web hosting, the word is shorthand for DNS propagation: the wait while resolvers across the internet replace their cached copies of your old DNS records with the new ones, which is what the rest of this page covers. If you were after the gardening or physics sense, a general dictionary will serve you better.