How Long Does DNS Propagation Take? 2026 Timing Guide
DNS propagation usually completes within a few hours for most record changes, but it can take up to 48 hours for the update to reach every resolver worldwide. The delay depends on the TTL value of the old record, how aggressively each resolver caches responses, and whether you are changing a simple A record or switching nameservers entirely.
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
What Actually Happens During Propagation
DNS does not broadcast changes. When you update a record, your authoritative nameserver begins serving the new value immediately. The delay comes from caching. Every DNS resolver between your visitors and your nameserver stores a copy of your old record and keeps serving it until the TTL, time to live, expires. TTL is a value you set in seconds that tells resolvers how long to cache the record before checking for a fresh copy (RFC 1035).
If your old A record had a TTL of 3,600 seconds (one hour), most resolvers will pick up the change within an hour after you update it. If the TTL was 86,400 seconds (24 hours), some resolvers will serve the stale record for up to a full day. A few resolvers ignore TTL and cache longer, which is why the theoretical maximum is commonly stated as 48 hours even when your TTL is short.
Nameserver changes, updating NS records at your registrar, propagate through an additional layer of delegation and typically take longer than simple record edits.
How to Reduce the Wait
If you know a DNS change is coming, lower the TTL on the affected record 24 to 48 hours before making the change. Drop it to 300 seconds (five minutes). Once that low TTL has propagated, make your actual change. Resolvers will now cache the old value for only five minutes before fetching the new one, and propagation effectively completes in minutes rather than hours.
After the change is confirmed worldwide, raise the TTL back to a normal value like 3,600 or higher. Low TTLs increase the number of queries your nameserver handles because resolvers re-check more frequently, so keeping them permanently low adds unnecessary load.
To check whether propagation has reached specific regions, use the tool on this page. Enter your domain and record type, and it queries resolvers in multiple locations to show you where the new value has landed and where the old one persists. This replaces guessing with a live answer. For background on what each record type does, see the DNS records reference.
Some ISP resolvers cache DNS responses beyond the specified TTL. In rare cases, clearing your local DNS cache or switching to a public resolver can confirm whether propagation has completed.
Next in this cluster
Related guides and tools
Sources
-
TTL caching behaviour per RFC 1035 (section 3.2.1). 48-hour propagation ceiling per standard DNS resolver behaviour. TTL pre-lowering technique per DNS operations best practice.
- Every figure in the calculators on this site is typed in by you. No price, allowance or renewal rate is stored in the page.