DNS Propagation Explained: How Long Does It Take?
When you make a change to your domain's DNS records—like pointing your domain to a new server or adding a new subdomain—you're often told you have to wait for "DNS propagation." This can be a frustrating waiting period, but understanding what's happening behind the scenes can help you manage it effectively. DNS propagation is the process by which DNS servers across the internet update their caches with the new information for your domain.
Why Isn't DNS Propagation Instant?
The Domain Name System (DNS) is a hierarchical and distributed naming system for computers, services, or other resources connected to the Internet. To prevent the root DNS servers from being overwhelmed with requests, the system relies heavily on caching at multiple levels.
When you change a DNS record, here's what happens:
- You update the record at your authoritative DNS server (usually managed by your domain registrar or a service like Cloudflare/AWS Route 53). This change is instant on that server.
- However, millions of other DNS servers around the world, such as those run by Internet Service Providers (ISPs), have a copy of your old record stored in their cache.
- These servers will not ask for the new record until their cached version expires. The expiration time is determined by a value you set called the Time to Live (TTL).
- DNS propagation is the time it takes for the majority of these recursive DNS servers worldwide to clear their cache and fetch the new, updated record from your authoritative server.
Note — there is no such thing as "forcing" DNS to propagate faster. You are always at the mercy of other servers respecting your TTL settings.
The Role of Time to Live (TTL)
TTL is the most critical factor influencing propagation speed. It's a value (in seconds) that you set for each DNS record. It tells recursive DNS servers how long they are allowed to cache that record.
Servers will cache the record for a full day. This reduces load on your authoritative server and can speed up lookups for returning visitors, but it means changes will propagate very slowly.
Servers will only cache the record for five minutes before they have to ask for it again. This is ideal when you are planning to make a change, as it ensures propagation will be very fast.
Best Practice: Before a planned DNS change (like a server migration), lower the TTL on the relevant records to a very short value (e.g., 60-300 seconds) at least 24 hours in advance. Once the change is complete and verified, you can raise the TTL back to a higher value.
Factors Affecting Propagation Time
As explained above, this is the primary factor. Propagation can't be faster than the TTL you had set on the old record.
Some ISPs or DNS resolvers may not perfectly respect your TTL settings. They might have their own minimum caching times, which can delay propagation in certain regions.
If you change your domain's name servers (e.g., moving from your registrar's DNS to Cloudflare), the propagation time is dictated by the TTL set at the TLD (Top-Level Domain) registry (e.g., for .com). This can often take 24-48 hours and is outside your direct control.
How to Check DNS Propagation
Since propagation happens at different rates in different parts of the world, you can't just check from your own computer. Use an online DNS propagation checker tool.
# Using dig from your terminal (checks your local resolver)
dig yourdomain.com A
# Checking against a specific public DNS server (Google's)
dig @8.8.8.8 yourdomain.com A
For a global view, use a web-based tool like:
Checks your DNS records from dozens of locations worldwide in real-time.
Another popular tool that provides a global view of your current DNS records.
Google provides a web-based version of the dig command.
Use our free DNS Propagation Checker to send the same query to five public resolvers — Google, Cloudflare, OpenDNS, Quad9 and Level3 — and compare each answer with your authoritative nameserver. The queries go from our server, so each answer is what that resolver network has cached near us, not a view from every continent.
Common questions
How long does DNS propagation take?
DNS propagation typically takes between a few minutes and 48 hours, depending on the TTL (Time to Live) value on the old record. Records with a short TTL (300 seconds = 5 minutes) propagate quickly. Records with a long TTL (86400 = 24 hours) take longer because resolvers cache the old value until TTL expires.
Why are some users seeing my old DNS while others see the new one?
Different users query different DNS resolvers (ISP resolvers, Google 8.8.8.8, Cloudflare 1.1.1.1), and each caches records independently based on TTL. During propagation, some resolvers have the new record while others serve the cached old value. This is normal and resolves as all caches expire.
How can I check if my DNS changes have propagated globally?
Use a DNS propagation checker to ask several public resolvers for the record at once and compare their answers with the value your authoritative nameserver now serves. Services with probes in many countries can also show where an old value is still cached. You can also run nslookup yourdomain.com 8.8.8.8 locally to check against Google's resolver specifically.
How do I speed up DNS propagation?
Reduce the TTL on the relevant DNS record 24-48 hours before making changes. Once the TTL is low, existing caches expire quickly and resolvers pick up your change faster. After propagation completes, increase the TTL again. You cannot force third-party resolvers to clear their cache — lowering TTL in advance is the most effective control.
References and further reading
The specifications and primary documentation this article is based on.
- RFC 1034 — Domain Names: Concepts and Facilities
- RFC 1035 — Domain Names: Implementation and Specification
- RFC 2308 — Negative Caching of DNS Queries
Defines how long a negative answer is cached — the mechanism behind most "propagation" delays.
Read next
More guides on the same subject.