How Long Does DNS Propagation Take and How to Check It

“It’s not working yet” is one of the most common questions right after a DNS or nameserver change — and it’s almost always propagation, not a mistake. Here’s what’s actually happening.

Why propagation isn’t instant

DNS relies on caching at every layer — your ISP, your operating system, your browser, and countless resolvers across the internet — to avoid looking up the same record millions of times a second. Each cached copy has a TTL (Time To Live), and it won’t refresh until that TTL expires, even after you’ve already updated the record at the source.

Typical timeframes

• Record changes within an existing zone (e.g. editing an A record’s IP) — usually visible within the record’s TTL, often minutes to a few hours.
• Nameserver changes (switching which DNS provider is authoritative) — can take up to 24-48 hours to reach full global propagation, since some resolvers cache the old nameserver delegation separately.

How to check propagation yourself

• Use a propagation-checker tool (search “DNS checker”) to see the record’s value as seen from dozens of locations worldwide at once.
• Run nslookup yourdomain.com or dig yourdomain.com from your own machine to see what your current resolver returns.
• Try flushing your local DNS cache (ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS) if you suspect you’re seeing a stale local copy rather than a genuinely unpropagated record.

Speeding it up next time

If you know a change is coming (a planned server migration, for example), lower the TTL on the relevant record to something like 300 seconds a day or two in advance. Once the low TTL itself has propagated, your actual change will then spread much faster when you make it.

Propagation delay is normal and expected — it isn’t a sign that something was set up incorrectly.