Introduction

A domain can point to the wrong website after a hosting change even when the migration itself looked successful. The usual problem is not the content. It is routing. DNS may still resolve to the old server, the new server may not be configured for the domain, or a CDN may still send traffic to the wrong origin. The fix is to verify the full path from DNS to web server host mapping instead of assuming the nameserver change completed the cutover.

Symptoms

  • Your domain loads another website, a default server page, or an old copy of the site
  • One hostname works while another shows the wrong content
  • The issue started after moving hosting, changing IPs, or updating nameservers
  • Some users reach the correct site while others still see the old one
  • CDN or control panel settings show the new destination, but the browser does not

Common Causes

  • The domain still resolves to the old IP address on authoritative DNS or cached resolvers
  • The new hosting account does not have the domain mapped to the correct site root
  • A CDN, proxy, or load balancer still routes requests to the previous origin
  • The server responds with a default virtual host because the hostname is not configured correctly
  • DNS cutover finished for one record but not for related hostnames like www or the apex domain

Step-by-Step Fix

  1. Query the authoritative DNS records for the domain and compare them with the intended hosting destination.
  2. Check both the apex domain and www hostname because mismatched records often make only part of the site appear wrong.
  3. Confirm the new hosting environment has the domain attached to the correct site, document root, or virtual host configuration.
  4. Review CDN or reverse proxy settings to make sure the domain is routing to the new origin rather than the old server.
  5. Test the origin directly with the correct host header if needed so you can separate DNS issues from server host-mapping issues.
  6. Clear or purge edge caches only after you verify DNS and host configuration are actually correct.
  7. Check whether any old redirect rules, parked domains, or default vhosts are catching traffic meant for the migrated site.
  8. Retest from multiple networks or public resolvers once the authoritative state is right to confirm the wrong-site behavior is gone.
  9. Keep a cutover checklist for future hosting moves so DNS, CDN, and hostname mapping are updated together instead of in isolation.