DNS Propagation Checker — Check DNS Changes Worldwide

DNS propagation is the time it takes for DNS changes to spread across the internet. When you update a DNS record, the change does not take effect everywhere at once. Different DNS resolvers around the world need to learn about the new value, and that takes time.

Our DNS propagation checker lets you see exactly where your changes have propagated and where they have not. Enter a domain, and we query multiple locations worldwide to check the current DNS record values.

This is essential when you migrate a website, change hosting providers, or update email servers. You need to know that your visitors in Tokyo, London, and New York are all seeing the correct DNS records.

What Is DNS Propagation?

DNS propagation is not a single event. It is a gradual process. When you update a DNS record on your authoritative nameserver, the change is immediate at the source. Your DNS provider's servers start serving the new record instantly. But the rest of the internet does not know about it yet.

Millions of DNS resolvers around the world have cached the old record. They continue serving the old value until their cached entry expires. The time it takes for all these caches to expire and fetch the new value is the propagation period.

Propagation is not controlled by any central authority. It depends on the TTL (Time to Live) you set on your DNS records and how aggressively each resolver caches responses. Some resolvers respect TTL strictly. Others ignore it and cache for longer than instructed. This is why propagation is unpredictable.

How Long Does DNS Propagation Take?

There is no single answer. Propagation can take anywhere from a few minutes to 72 hours. In practice, most changes propagate within 15 minutes to 2 hours if you set low TTL values beforehand.

The biggest factor is your TTL setting. If your old records had a TTL of 86400 seconds (24 hours), resolvers that cached the old value will not check for a new one for 24 hours. This is why you should lower your TTL to 300 seconds (5 minutes) a few days before making a major DNS change.

Other factors include your DNS provider's infrastructure, geographic distance from your nameservers, and the caching policies of individual ISPs. Some ISP resolvers ignore TTL entirely and cache for 48 hours regardless of what you specify. There is nothing you can do about this except wait.

Changes to NS records take the longest to propagate because they are cached at multiple levels of the DNS hierarchy — at TLD nameservers and by recursive resolvers worldwide. A record and CNAME changes propagate faster because they are only cached by recursive resolvers.

How to Check DNS Propagation Status

Use our propagation checker to query your domain from multiple geographic locations. The tool connects to DNS resolvers in North America, Europe, Asia, Australia, and South America, then reports what each one sees.

If all locations show the same record value, your change has propagated globally. If some locations show the old value and others show the new one, propagation is still in progress. The tool shows you which regions are updated and which are still catching up.

You can also check propagation manually using command-line tools with specific resolvers. Use dig with a resolver in a different region: dig @1.1.1.1 example.com (Cloudflare, US), dig @8.8.8.8 example.com (Google, global), or dig @9.9.9.9 example.com (Quad9, Switzerland). Compare the results to see if propagation is complete.

For a quick spot-check, use our DNS lookup tool with your preferred resolver. If it shows the new record, your authoritative nameserver is serving it correctly. The remaining work is waiting for the rest of the internet to catch up.

How to Speed Up DNS Propagation

You cannot force DNS propagation, but you can prepare for it. The most effective technique is lowering your TTL before making changes. Switch your TTL to 300 seconds (5 minutes) at least 48 hours before the planned change. This gives resolvers time to re-cache with the new, shorter TTL.

After the change, you can raise the TTL back to a normal value like 3600 seconds (1 hour) or 86400 seconds (1 day). Low TTLs increase query load on your nameservers because resolvers check back more frequently. You do not want to keep a low TTL permanently unless you expect frequent changes.

Use a DNS provider with a global anycast network. Anycast makes your nameservers available from multiple locations worldwide, which reduces the time it takes for resolvers in different regions to reach your servers. Providers like Cloudflare, AWS Route 53, and Google Cloud DNS use anycast.

For emergency changes — like when you need to redirect traffic away from a failed server — there is no shortcut. You make the change, wait for propagation, and monitor using a propagation checker. This is why it is smart to have a DNS failover plan ready before you need it.

Common DNS Propagation Questions

Why does my website show the old server after 24 hours?

Either your TTL was too high before the change, or your ISP's resolver is overriding TTL with its own caching policy. Try clearing your local DNS cache and restarting your router. If that does not work, contact your ISP, but do not expect quick action.

Is DNS propagation the same as DNS caching?

They are related but different. DNS caching is what individual resolvers do to improve performance. DNS propagation is the aggregate effect of millions of resolvers updating their cached values after a change. Propagation is just caching at internet scale.

Why do different propagation checkers show different results?

Each checker uses different resolvers in different locations. One checker might query from New York and another from Singapore. If propagation is uneven, they will show different results. This is normal and reflects the actual state of global propagation.

For a full picture of your domain's DNS health, use our DNS checker which combines propagation status with record validation and DNSSEC verification.