After moving to new hosting, it is common to find the website still showing the old site, or showing it on one device but not another. The domain is still resolving to the old server's IP somewhere along the way – in DNS records, a resolver cache, your hosts file or a CDN. This guide shows how to find out which, and fix it.
Before you start
- Your new server IP from cPanel → General Information (open cPanel from Services in the MdmHost dashboard).
- Where your DNS is managed: MdmHost nameservers, your registrar, or Cloudflare. Check with our WHOIS checker.
Check which IP the domain resolves to
- Run
nslookup example.comandnslookup www.example.comon your computer. - Compare with a public resolver:
nslookup example.com 8.8.8.8andnslookup example.com 1.1.1.1. - Ask the authoritative nameserver directly:
dig example.com @ns1.yournameserver.com +short.
If the authoritative answer is the old IP, the DNS records are wrong. If it is the new IP but your computer shows the old one, it is caching.
Fix the DNS records
- Nameservers not changed: if the domain still uses the old host's nameservers, either update the nameservers at your registrar or update the A records at the old DNS host.
- Leftover A records: update both
@andwww(and any other subdomains) to the new IP. AwwwCNAME pointing to an old hostname is a common miss. - Cloudflare: edit the A records inside Cloudflare; changing nameservers at the host does nothing while Cloudflare is in front.
- AAAA records: delete old IPv6 records, or IPv6 users keep reaching the old server.
Clear caches
- Hosts file: remove any line for the domain you added while testing the migration (
C:\Windows\System32\drivers\etc\hostsor/etc/hosts). - DNS cache:
ipconfig /flushdnson Windows, and Chrome'schrome://net-internals/#dns. - Browser cache: test in a private window.
- CDN cache: purge everything in Cloudflare or your CDN.
- Old TTLs: if the record had a long TTL, some resolvers keep the old IP until it expires. See DNS propagation and TTL.
Tip: Leave the old hosting active for a few days after the switch. Visitors on slow-updating resolvers still see a working site, and you can copy over any late emails or orders.
Check email too
MX records may also point to the old host. In cPanel → Domains → Zone Editor, confirm MX and the mail record use the new server, and update mail client settings if the hostname changed.
FAQ
How long does it take for a migrated site to show everywhere?
Usually minutes to a few hours; up to 48 hours if nameservers changed or TTLs were long.
Why does my phone show the new site but my PC the old one?
Your PC has a cached DNS answer or a hosts file entry.
Can I check the new site before DNS switches?
Yes, with a temporary hosts file entry. Remember to remove it afterwards.