Guides › Hosting, domain & email › Domain, DNS & SSL

Domain Nameservers Changed but Site Still Shows Old Content

Propagation takes time, but wrong zones or cached results also cause confusion.

Reference guide. This guide is written from established practice and the official documentation of the tools involved. We have not yet tested every step on a live demo site. Back up your site before you change anything.
Domain, DNS and SSL

After you change nameservers, it can take hours before everyone sees the new site. If you still see the old one, check these points in order rather than only waiting.

1Check which nameservers are published2Check the new host has the domain3Allow for propagation4Flush your local DNS5Look for a hosts file entry6Purge CDN and site caches7Compare from other networksFixed? Test the site. If not, get help.
The steps in order. Work down the list and stop when the problem is solved.

Step 1: Check which nameservers are published

Illustration for Step 1: Check which nameservers are published

Run dig NS yourdomain.com or use a lookup site. They should list the new provider's nameservers, not the old ones.

Step 2: Check the new host has the domain

Illustration for Step 2: Check the new host has the domain

The new hosting or DNS account must have the domain added, with the site files uploaded and the A records present. Otherwise visitors see a default or empty page.

Step 3: Allow for propagation

Illustration for Step 3: Allow for propagation

Resolvers cache answers. The old nameserver TTL, often 24 to 48 hours, decides how long they keep the old data.

Step 4: Flush your local DNS

Illustration for Step 4: Flush your local DNS

Clear your computer's DNS cache and restart the browser. On Windows run ipconfig /flushdns.

Step 5: Look for a hosts file entry

Illustration for Step 5: Look for a hosts file entry

An old line in your computer's hosts file pins the domain to the old server. Remove it if present.

Step 6: Purge CDN and site caches

Illustration for Step 6: Purge CDN and site caches

An old page may be cached by a CDN or caching plugin even after DNS has moved.

Step 7: Compare from other networks

Illustration for Step 7: Compare from other networks

Test with mobile data and a propagation checker. If others see the new site, it is only your device.

Still stuck?

If these steps do not solve it, we fix it for you for a flat $99. Full refund if we do not solve it within 7 days.

Related guides

Did this solve it? If not, email hello@sitefixlab.org with the exact error text and we will look into it. Try the problem finder.

Last updated 2026-11-22.