How Long DNS Changes Take
DNS propagation typically takes between a few minutes and 48 hours, with most changes visible worldwide within four to six hours. The delay happens because thousands of recursive resolvers around the world cache your old record until its TTL expires. The checker on this page lets you test whether your change has reached major resolver networks in real time.
Closest fit
Every class, ranked
This is a category, not a company. Any host selling that category can serve you well or badly; the checks below are how you tell them apart.
Before you pay, check these four things
Why DNS Changes Are Not Instant
DNS is a distributed caching system, not a single database. When you update a record at your nameserver, the new value is immediately available there, but every other resolver that previously looked up your domain still holds the old answer in its cache. Those caches expire based on the TTL (Time to Live) value that was attached to the previous record. If the old TTL was 86400 seconds, some resolvers will serve the stale answer for up to 24 hours.
ISP resolvers are the most common source of visible delay. Large consumer ISPs cache aggressively and sometimes honour TTLs loosely, occasionally holding records slightly beyond the stated TTL. Public resolvers like those operated by Cloudflare (1.1.1.1) and Google (8.8.8.8) tend to respect TTLs precisely and flush faster. This is why you might see the new address from one network while a colleague on a different ISP still sees the old one.
How to Speed Up and Verify Propagation
The single most effective step is lowering your TTL well before you make the change. Drop it to 300 seconds at least 24 hours in advance. Once the old high-TTL caches have expired and resolvers are fetching with the short TTL, your actual change will propagate in minutes rather than hours.
To verify propagation, the tool on this page queries multiple resolver networks across regions and shows which ones have picked up the new record. If a few holdouts remain after several hours, those are almost always ISP resolvers with aggressive caching policies — they will catch up once the TTL expires.
Flushing your own local DNS cache can help you see changes faster on your own machine. On most systems this involves a single command, but it only affects your device. You cannot force a remote resolver to flush — you have to wait for its cache to expire naturally.
The common claim that propagation always takes 48 hours dates from an era when long TTLs were the default. With a short TTL set in advance, most changes are globally visible within one to two hours.
Next in this cluster
Related guides and tools
Sources
-
DNS caching behaviour per RFC 1035 and RFC 2308 (negative caching). TTL-based expiry mechanism per IETF standards.
- Every figure in the calculators on this site is typed in by you. No price, allowance or renewal rate is stored in the page.