What is DNS propagation?

DNS propagation is the time it takes for recursive DNS servers and ISPs worldwide to update their cached records after a domain's nameservers or IP addresses are changed.

Can I force DNS propagation to happen faster?

You cannot force independent global ISPs to drop their caches, but you can minimize delay by lowering your TTL values 24 to 48 hours before making changes.

Why does my website load on my phone but not on my laptop?

This happens because different devices and cellular networks use different DNS resolvers and cache records for varying lengths of time based on their local TTL expiration.

How long does a full DNS propagation usually take?

Complete global propagation typically takes between 2 to 48 hours, depending largely on the TTL value set on your previous DNS records.

Should I keep my old hosting account active during propagation?

Yes, you should keep your old hosting active for at least 48 hours to ensure visitors whose DNS has not yet propagated can still access your website without encountering errors.

How to Fix DNS Propagation Delay After Changing Nameservers

DNS propagation delay happens when you update your nameservers, but global resolvers still point visitors to your old hosting provider. This delay occurs because recursive DNS servers and local operating systems cache your old records to improve browsing speed, meaning they do not query your new authoritative nameservers immediately. Fortunately, you can minimize downtime and troubleshoot caching issues using proper administrative techniques and diagnostic utilities.

Why DNS Propagation Takes Time

When you change your domain's nameservers at your registrar, the registry updates its root servers almost instantly. However, the rest of the internet does not check the root servers for every single website visit. Instead, internet service providers (ISPs), public resolvers like Google and Cloudflare, and individual operating systems cache DNS records based on a value called Time to Live (TTL).

If your previous TTL was set to 86400 seconds (24 hours), recursive resolvers around the world will store your old A record or nameserver records for a full day before asking for an update. This hierarchical caching structure is the primary reason why different locations load different versions of your website during a migration.

How to Check Current Propagation Status

Before you start troubleshooting, you need to see how far along your propagation process is across the globe. Instead of relying on your own browser, which is likely serving a cached version of the site, you should query geographically diverse recursive nameservers.

You can use the dns propagation checker to instantly query your domain's records against multiple international DNS servers and verify whether your new nameservers or IP addresses are resolving correctly worldwide.

Step-by-Step Guide to Fixing and Reducing Delay

If your website is inaccessible or visitors are hitting the wrong server, follow these practical steps to diagnose and mitigate propagation delays.

Step 1: Pre-Configure Lower TTLs

If you have not yet changed your nameservers, you can prevent long delays by lowering the TTL on your existing DNS records 24 to 48 hours in advance. Drop values from 86400 (24 hours) down to 300 (5 minutes).

; Old record with high TTL
example.com.   86400   IN   A   192.0.2.1

; Updated record prior to migration
example.com.   300     IN   A   192.0.2.1

By reducing the TTL, caching servers will drop the old records quickly, forcing them to look up your new nameservers much faster once the migration begins.

Step 2: Verify Registrar and Registry Nameservers

A common mistake during nameserver updates is a typo in the hostname or a failure to save changes at the domain registrar. You can verify that your registrar successfully pushed the changes to the top-level registry by running a whois lookup from your terminal.

whois example.com

Look for the Name Server fields in the output. They must match the exact nameservers provided by your new hosting or DNS provider, such as ns1.examplehosting.com and ns2.examplehosting.com.

Step 3: Test Direct Resolution with Dig

To bypass your local ISP cache and query your new authoritative nameservers directly, use the dig command-line utility. This tells you definitively whether your new nameserver configuration is returning the correct records.

dig @ns1.examplehosting.com example.com A

If this command returns your new IP address, your backend configuration is correct, and any remaining delay is strictly due to global caching.

Step 4: Clear Local Operating System and Browser Caches

Even when global propagation is complete, your personal computer or browser might still hold onto the old DNS mapping. You should clear your local caches to see your live site.

Windows (Command Prompt): ipconfig /flushdns
macOS (Terminal): sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Linux (systemd-resolved): sudo systemd-resolve --flush-caches

Additionally, clear your browser cache or open an incognito/private browsing window.

Pre-Migration Checklist

Review this checklist before updating your domain's nameservers to ensure a seamless transition with minimal downtime:

Lower the TTL on all existing DNS records to 300 seconds at least 24 hours prior.
Replicate all existing DNS records (MX, TXT, CNAME) on the new DNS provider before switching.
Verify the spelling of the new nameservers provided by your host.
Keep your old hosting active for at least 48 hours after changing nameservers.
Flush your local DNS cache after making updates.