What Is DNS Propagation? Why Domain Changes Take Time

What "Propagation" Means

DNS propagationThe delay while an updated DNS record spreads to servers worldwide, so a change isn't visible everywhere at once. is the delay between changing a domain's DNSThe Domain Name System — the internet's directory that translates domain names into the IP addresses of servers. records and that change being visible everywhere on the internet. It isn't a single event; it's a gradual process, because DNS answers get cached at many points along the way, and each cached copy only updates once it expires on its own schedule.

Why It Isn't Instant: Caching and TTL

Every DNS record has a TTL, or time to live, a setting that tells other servers how long they're allowed to cacheA temporary store of already-fetched data, kept so it can be reused quickly instead of fetched again. that record's answer before checking again. If your domain's A recordA DNS record that points a domain at the IPv4 address of the server hosting its website. has a TTL of 24 hours, a server that looked up your domain 23 hours ago won't check again for another hour, even if you changed the record five minutes ago. Multiply that across every ISP, corporate network, and device cachingStoring a copy of data or a page so it can be served faster next time instead of being regenerated. your domain's records independently, and you get a rolling window where different visitors see different answers, not a single moment where the whole internet switches over together.

How Long It Actually Takes

In practice, most DNS changes are visible to most visitors within a few hours. Full propagation, meaning every cache worldwide has expired and picked up the new answer, can take anywhere from a few hours up to 24 to 48 hours, depending mostly on the TTL that was set before you made the change. A domain with a short TTL propagates fast; one with a long TTL takes longer, simply because more caches are still holding the old answer.

What You'll Actually See During Propagation

It's normal, during this window, for the same domain to resolve differently depending on who's looking: some visitors reach the new server immediately, others keep reaching the old one for a while longer, and this can even vary by device on the same network if they queried at different times. None of this means anything is misconfigured; it's the expected, temporary side effect of how DNS caching works everywhere.

How to Check Propagation Status

Rather than guessing, you can check directly: a DNS propagation checker tool queries your domain from servers in many locations worldwide and shows you what each one currently returns. You can also query a public DNS resolverA DNS server, usually run by your ISP, that looks up domain names on your behalf and caches the answers. directly from the command line. Once the record is consistent across locations and matches the new value you set, propagation is effectively done.

How to Minimize the Delay

You can't speed up a propagation window that's already started, but you can shrink it in advance: lower the record's TTL to a short value, like 5 or 10 minutes, a day or two before you plan to make a change. Once the old, longer TTL has fully expired everywhere, the actual cutover propagates far faster, often within minutes instead of hours, because caches are already checking back frequently by the time you flip the record.

When It's Not Actually a Propagation Problem

Propagation gets blamed for a lot of issues that aren't actually caused by it. If a domain still doesn't resolve correctly after 48 hours, or never worked at all, the more likely cause is a misconfigured record, for example the wrong IP addressThe numeric address (like 203.0.113.10) that identifies a server on the internet., a typo in a CNAMEA DNS record that points one name at another domain name rather than directly at an IP address. target, or DNS pointed at the wrong nameserversA DNS server that holds the authoritative records for a domain and answers where its website and email live. entirely, not propagation still in progress. Worth double-checking the actual record values before assuming it just needs more time.

Where Propagation Comes Up Most

Propagation matters most in two situations: registering a brand-new domain, where it's usually fast since there's no old cached answer competing with it, and migrating an existing domain to a new host, where the old answer is often cached widely and takes longer to fully clear. See our step-by-step guide to migrating your website for how to plan around propagation during a host switch, and our WordPress launch checklist for confirming DNS has fully settled before you consider a site properly live.

If you're not sure what your domain's current DNS records look like, our free WHOIS lookup is a quick way to check registration details, and our domains page is the place to start if you're registering something new.