DNS Propagation: What It Is & How Long It Takes

DNS propagation is the period after you update your domain’s nameservers or DNS records when the new information spreads across the internet’s domain name system. When you make a change, you enter it at your DNS provider, but the old records remain cached on servers worldwide until they expire. This article explains what propagation actually is, why it happens, how long it typically takes, and what you can do while waiting.

What Does DNS Propagation Actually Mean?

DNS propagation is the time it takes for a DNS record change to be picked up by every recursive resolver and caching server on the internet. When you update an A record, MX record, or nameserver, the change is immediately live on your authoritative DNS server. However, most other servers do not query your authoritative server directly—they use cached answers from a recursive resolver (like your ISP’s DNS or Google Public DNS). Those resolvers store records for a period called the TTL (time to live), which is set in seconds on the record itself. Until that TTL expires, the resolver keeps serving the old value, and that delay is what people call propagation.

It is not a single global switch. Different resolvers will update at different times, depending on when they cached the old record and what TTL was set. A record with a 300-second TTL will propagate in minutes; one with a 86400-second TTL (24 hours) can take a full day.

How DNS Propagation Works (Step by Step)

1. You edit a record at your DNS provider (e.g., change the IP address for www).
2. Your provider updates its authoritative nameservers instantly.
3. A user’s device asks its configured recursive resolver (e.g., 8.8.8.8) for the address.
4. The resolver checks its cache. If it has a fresh copy, it returns that—possibly the old IP.
5. If the cache is expired, the resolver queries the authoritative nameservers, gets the new IP, stores it for the TTL, and returns it to the user.
6. Different resolvers repeat this process at different times, so propagation is gradual.

The key factor is the TTL value on the old record. Lower TTLs mean shorter cache times, so changes spread faster. That is why many DNS guides recommend lowering TTL to 300 or 60 seconds a day before you make a change.

How Long Does DNS Propagation Take?

Typical propagation times vary by record type and TTL:

• Low TTL (300s or less): Most resolvers update within 5–15 minutes.
• Standard TTL (3600s): Usually 1–2 hours, but can stretch to 24–48 hours in rare cases.
• High TTL (86400s): Up to 24–48 hours, occasionally longer if a resolver ignores TTL.

In practice, most changes propagate within a few hours. However, some ISPs and corporate DNS servers cache records longer than the TTL, or ignore it entirely (a practice called TTL overrides). That is why you will often see “up to 48 hours” from hosting providers—it is a worst-case estimate, not a guarantee.

Common Problems and Misconceptions

“My site still shows the old page after 24 hours.” This is usually not a propagation issue. Your browser, your device, or your local network may be caching the old DNS answer. Try flushing your DNS cache (on Windows: ipconfig /flushdns; on macOS: sudo dscacheutil -flushcache) or testing from a different network (e.g., a mobile hotspot).

“Propagation is instant.” No. Even with a TTL of 60 seconds, a resolver that queried just before your change may hold the old record for up to 60 seconds. There is always some delay.

“You can force propagation.” You cannot force the entire internet to update. You can only reduce TTL before the change and wait. Some services offer “propagation checkers” that query multiple resolvers, but they only show the current state—they do not speed anything up.

How to Check Propagation Status

You can check whether a specific record has updated at a given resolver by using a public DNS lookup tool. These tools query a resolver directly and show the answer it returns. For example, you can query Google DNS (8.8.8.8) for your domain and see if it returns the new IP. If it still shows the old IP, that resolver has not yet refreshed its cache. You can also use the command line: nslookup example.com 8.8.8.8 (Windows) or dig @8.8.8.8 example.com (macOS/Linux).

If you want to see the global picture, a propagation checker tool queries many resolvers at once and shows a map of which ones have updated. These are useful, but remember that a single resolver showing the old value does not mean the whole internet is stuck—it just means that one cache is still valid.

How to Minimize Propagation Time

• Lower the TTL on the record you plan to change at least 24 hours before the change. Set it to 300 or 60 seconds.
• Make the actual change after the old TTL has expired. This ensures most resolvers have already dropped the old record.
• After the change, you can raise the TTL back to a normal value (e.g., 3600 or 86400) to reduce query load on your authoritative servers.
• If you are moving to a new hosting provider, update the nameservers at your registrar first, then wait—do not change records at the old provider.

DNS Propagation vs. TTL: What’s the Difference?

TTL is a number (in seconds) that tells a resolver how long to keep a record in cache. Propagation is the observable effect of that TTL expiring across many resolvers. TTL is a setting you control; propagation is a consequence. A low TTL does not make propagation instant—it just makes it fast. A high TTL makes propagation slow. There is no way to have zero propagation time because every resolver must eventually re-query your authoritative server.

Frequently Asked Questions

Why is my website still showing the old IP after 48 hours?

Most likely your device or local network is caching the old DNS answer. Flush your DNS cache, restart your router, or try a different network. If the new IP appears on a public resolver (like 8.8.8.8) but not on your ISP’s, your ISP may be ignoring TTL—contact them or wait longer.

Can I make DNS propagation faster?

You can only reduce the TTL before the change. Once the change is made, you cannot force resolvers to drop their cache. Some resolvers support “cache flush” commands, but you cannot send those to third-party servers.

Does changing DNS records affect email?

Yes. If you change MX records, email may be routed to the old server for a while. To avoid downtime, lower the TTL on the MX record in advance, and keep the old mail server active for at least 48 hours after the change.

What is the difference between propagation and DNS resolution?

DNS resolution is the process of converting a domain name to an IP address—it happens every time a user visits a site. Propagation is the delay in that resolution after a record change. Resolution is instant; propagation is not.

Should I use a low TTL permanently?

No. A very low TTL (e.g., 60 seconds) means every resolver queries your authoritative server more often, which increases load. Use a low TTL only before a planned change, then raise it back to 3600 or 86400 for normal operation.

Why do some propagation checkers show different results?

Each resolver caches independently, so at any moment some may have the new record and others the old. That is normal. Checkers query multiple resolvers at once, so you see the gradual spread—not a single global status.

Related

• Problem Sending the Command to the Program? Fix It Now
• Why Is Tesla Testing a Cybertruck With Lidar Sensors?
• Hide Helmet in Dune Awakening: Step-by-Step

in t | Time to wait | hours | 24 | 0
in p | Propagation progress | % | 50 | 0
out eff | Effective wait remaining | hours | t * (1 - p / 100) | 1