How Long Does DNS Propagation Take?
DNS changes can appear within minutes for one user and remain unchanged for another. There is no single global propagation timer: each recursive resolver refreshes its cached answer according to the TTL and the moment it last queried the authoritative DNS servers.
The practical answer
A well-planned record change often becomes widely visible within minutes to a few hours. A nameserver migration or a record with a long previous TTL can remain inconsistent for 24 to 48 hours. The important value is the TTL that was cached before the change, not only the TTL currently published.
When a resolver has no cached answer, it can retrieve the new record immediately. A resolver that cached the old answer just before the update may continue returning it until that cache expires.
Check the current TTL
Use dig to inspect the answer and remaining TTL returned by a resolver. The first number after the hostname is the remaining cache lifetime in seconds.
dig @1.1.1.1 example.com A
dig @8.8.8.8 example.com A
dig @9.9.9.9 example.com AWhat affects propagation time
- The previous TTL cached by recursive resolvers.
- Whether the change is a record update or a parent-zone nameserver delegation change.
- Negative caching after a previous NXDOMAIN or missing-record response.
- Inconsistent authoritative nameservers serving different zone versions.
- Local browser, operating system, router or application caches.
A safer migration sequence
- Lower the TTL at least one old-TTL period before the planned change.
- Confirm every authoritative nameserver serves the same current value.
- Make the record change and keep the old service available during the transition.
- Compare several independent resolvers instead of relying on your local ISP.
- Raise the TTL again after responses are stable.
Common mistakes
Lowering TTL at the same time as the change
Resolvers may already hold the old record with the previous longer TTL.
Assuming one successful lookup means completion
One resolver can refresh while others still return cached data.
Turning off the old server immediately
Users behind stale caches may still connect to the previous address.
Confusing browser cache with DNS cache
Test with explicit public resolvers to isolate DNS behavior.