Nameservers Changed But Old Site Still Showing? Fix

If you changed your nameservers but still see the old site, the most likely reason is DNS propagation delay—the global network of DNS servers hasn’t yet refreshed its cached records. This typically resolves within 24–72 hours, but you can speed it up or verify the issue by flushing your local DNS cache, checking the authoritative nameservers, and using online propagation checkers.

Why DNS Propagation Takes Time

When you change nameservers, you’re updating the records that tell the internet where your domain’s website and email live. These records are distributed across a hierarchical system of DNS servers worldwide. Each server caches the old information for a period called the TTL (Time to Live), which is set by your previous DNS provider. Until that cache expires, some users will be directed to the old server. The TTL can range from minutes to 48 hours, and many ISPs override it with their own caching policies, so the actual propagation time varies.

How to Check If Your Nameservers Are Correct

First, confirm that your domain registrar actually processed the change. Log into your registrar’s control panel and look for the DNS or Nameservers section. The new nameservers should be listed exactly as provided by your hosting company—typos are a common cause of failure. You can verify the current authoritative nameservers using a public DNS lookup tool like whois or an online lookup service. If the registrar still shows the old nameservers, the change wasn’t saved or hasn’t propagated at the registrar level.

Flushing Your Local DNS Cache

Your own computer also caches DNS results. Even after the global DNS updates, your machine might keep showing the old site until the cache expires. To force a refresh, flush the cache:

Windows: Open Command Prompt as administrator and run ipconfig /flushdns.
macOS: Open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder (for recent versions).
Linux: Depending on your distribution, use sudo systemd-resolve --flush-caches or sudo service nscd restart.

After flushing, try visiting your site again. If it still shows the old version, try a different network (like your phone’s mobile data) to rule out your ISP’s cache.

Using Online Propagation Checkers

Online tools like What’s My DNS or DNS Checker let you query DNS servers in different locations around the world. They show you which servers still have the old records and which have the new ones. This helps you determine if the problem is global or just local to your network. If most locations show the new nameservers, the propagation is nearly complete, and you just need to wait a bit longer or clear your local cache.

Common Mistakes That Cause the Old Site to Persist

Besides propagation, several errors can cause the old site to remain visible:

Incorrect nameserver values: A missing dot at the end or a wrong hostname (e.g., ns1.example.com instead of ns1.example.net).
Registrar lock: Some registrars require you to unlock the domain before changing nameservers.
Old DNS records still active: If you changed nameservers but the new provider doesn’t have the correct A records, the site may fail to load or show an error.
Browser cache: Browsers also cache DNS and page content. Try a hard refresh (Ctrl+F5 on Windows, Cmd+Shift+R on Mac) or open the site in an incognito window.

What to Do If It’s Been More Than 72 Hours

If the old site persists after three days, the issue is likely not just propagation. Check the following:

Verify the nameservers at your registrar are exactly what your hosting provider gave you.
Confirm that the new DNS provider (usually your host) has the correct A record pointing to your server’s IP address.
Test with a different device and network to see if it’s only your local ISP caching.
Contact your hosting provider’s support—they can check if the nameservers are resolving correctly from their side.

Frequently Asked Questions

How long does DNS propagation really take?

Most changes propagate within 24 to 48 hours, but some ISPs may take up to 72 hours. The TTL you set before the change affects the maximum time, but many providers cap it at 48 hours. After 72 hours, if the old site still shows, it’s likely a configuration error.

Can I speed up DNS propagation?

Not directly—propagation depends on the TTL set by your old DNS provider. However, you can lower the TTL before making the change (if you planned ahead) to minimize the cache duration. After the change, you can only wait and flush your local cache.

Why does my site show the old version on my phone but the new version on my computer?

Different devices and networks use different DNS servers. Your phone might be using your mobile carrier’s DNS, which hasn’t updated yet, while your computer uses your ISP’s DNS that has. This is normal during propagation.

What if I see the old site but the nameservers are already correct?

Then the issue is likely your local DNS cache or your ISP’s cache. Flush your local cache, try a different network, or use a public DNS like Google (8.8.8.8) or Cloudflare (1.1.1.1) to see if that helps.

Should I clear my browser cache to see the new site?

Yes, browsers cache DNS and page content. A hard refresh (Ctrl+F5) or clearing your browser cache can force it to re-fetch the site. If that doesn’t work, try incognito mode, which usually bypasses the cache.

Could the old site be cached by my hosting provider?

If you’re using a hosting provider with a CDN or caching layer, they might serve a cached version. Check with your host if they have a cache purge option, or wait for the cache to expire (usually within a few hours).

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →