Summary: If a client's domain shows their old site, a cPanel default page, or someone else's site after a migration, the cause is usually DNS caching, a missing domain on the account, or a leftover index file, and this article shows you how to find and fix each one.
Step 1: Figure out what you're seeing
| What you see | Most likely cause |
|---|---|
| The old site, as it was before the migration | DNS still points to the old host, or your computer has cached the old address |
| A generic cPanel or server default page | DNS points to your server, but the domain isn't set up on any account |
| A "coming soon" or placeholder page | A leftover index.html is loading instead of the real site |
| Another client's site | The domain was added to the wrong account, or points to the wrong folder |
| The site works for some people but not others | DNS propagation, or an old IPv6 (AAAA) record |
Step 2: Check where DNS points
Compare public DNS with your server's IP:
dig +short clientdomain.com @8.8.8.8
dig +short www.clientdomain.com @8.8.8.8
dig +short AAAA clientdomain.com @8.8.8.8On Windows, run nslookup clientdomain.com 8.8.8.8 instead.
- If the A records show the old host's IP, update DNS. Nameserver changes can take up to 24 to 48 hours to reach everyone.
- If there's an AAAA record from the old host, delete it. Visitors using IPv6 will keep reaching the old server until you do.
- Make sure
wwwpoints to your server too, not just the root domain.
Clear your own cache
- Windows:
ipconfig /flushdns - Mac:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder - Close and reopen the browser, or try a private window or a phone on mobile data.
Step 3: Test with your hosts file
Your hosts file lets your computer only view a domain on your new server, whatever public DNS says. It's the best way to test before or right after cutover.
- Open the hosts file as an administrator:
- Windows: Open Notepad as Administrator and open
C:\Windows\System32\drivers\etc\hosts - Mac/Linux: Run
sudo nano /etc/hostsin Terminal
- Windows: Open Notepad as Administrator and open
- Add a line at the bottom:
YOUR-SERVER-IP clientdomain.com www.clientdomain.com - Save the file, flush your DNS cache, and load the site.
- Remove the line when you're done testing. If you forget, you won't see real DNS changes later.
If the site looks right through the hosts file, the migration is fine and you're just waiting on DNS. If it still looks wrong, keep going.
Step 4: Make sure the domain is on the right account
- In WHM, go to Account Functions ยป List Accounts and search for the domain.
- If it isn't the main domain of any account, it may need to be added as an addon domain. Open the correct client's cPanel, go to Domains, and add it. Set its document root to the folder that holds the site's files.
- If the domain belongs to the wrong account, remove it there first, then add it to the correct one.
- In the account's Domains page, check that the document root matches where the migrated files actually are.
Step 5: Check the index file
The web server loads the first index file it finds, and index.html takes priority over index.php. A leftover placeholder index.html can hide a WordPress or PHP site.
- Open the site's document root in cPanel's File Manager.
- If both
index.htmlandindex.phpare there, and the real site is PHP-based, renameindex.htmltoindex.html.bak. - Reload the site.
Step 6: Check the app and cache settings
- WordPress: If the site redirects to a temporary URL or the old domain, check the Site Address and WordPress Address settings.
- Caching plugins or a CDN: Purge the cache so old pages aren't served.
- Hard-coded IPs or paths in configuration files from the old host may need updating.
Still stuck? Open a ticket
Our U.S.-based support team is available 24/7. Open a support ticket from the Liberation Client Area and include the domain, the cPanel username, what you expected to see, and what you actually see. Tickets are private, so they are the safe place to share server details. Never post passwords in public forums or chats.
