Introduction

After a cPanel transfer, a subdomain can start loading the main site instead of its own content. The files may still be present, but the new server is handling that hostname with the wrong document root or falling back to the primary site configuration.

Treat this as a hostname-binding problem before assuming the application itself is broken. Start by proving where the subdomain should point on the destination server and whether the new host is actually serving that path for the subdomain request.

Symptoms

  • The subdomain loads the main website after migration
  • Requests to the subdomain show the wrong content or a fallback site
  • DNS points to the new server, but the subdomain still resolves to the main document root
  • The subdomain files exist on disk, but they are not what the browser shows
  • Only the primary domain works correctly while one subdomain is wrong
  • The issue began immediately after cPanel account transfer or restore

Common Causes

  • The subdomain was not restored cleanly in the destination cPanel account
  • The subdomain’s document root points to the main site directory
  • A fallback virtual host is handling the subdomain request
  • DNS was updated before the subdomain binding was rebuilt on the new server
  • A leftover alias or wildcard rule now catches the subdomain unexpectedly
  • The subdomain files were restored, but the hostname-to-path mapping was not

Step-by-Step Fix

  1. Confirm which document root the subdomain is supposed to use on the destination server, because you need the intended path before you can verify whether the host mapping is wrong.
  2. Check the subdomain entry in the destination cPanel account and make sure it still exists there, because migrations can transfer files while failing to recreate the subdomain definition itself.
  3. Compare the configured subdomain document root with the actual directory that contains the intended site, because a wrong root path will make the server serve the main site or another fallback instead.
  4. Verify that the subdomain’s DNS resolves only to the destination server you are testing, because mixed or stale DNS can make a correct local binding look wrong.
  5. Review the active virtual-host handling for the subdomain if the cPanel mapping appears correct, because a fallback vhost can intercept the hostname before the intended subdomain path is used.
  6. Check for wildcard, alias, or inherited rewrite behavior that may now catch the subdomain, because one leftover rule can force requests into the main site even when the files are present.
  7. Test the subdomain with a unique file in the expected document root after each correction, because a direct content check proves whether the hostname is finally serving the right directory.
  8. Compare one working hostname binding and one broken subdomain binding on the same account, because differences in root path or hostname registration usually reveal what the transfer missed.
  9. Document every migrated subdomain and its final document root after recovery, because secondary hostname mappings are often the part that cPanel transfers leave incomplete.