"This site can’t be reached" issue after migration (DNS Cache)

After a migration, you might find that your site is inaccessible from Copilhost, even though you thought the process was complete.

You might encounter a generic "This site can't be reached" message or a specific DNS error screen like this:

These are common caching issues, and we are here to help you resolve them.

Generally, your site has been successfully migrated and is live for the rest of the world, but it remains temporarily inaccessible to you specifically because of a cache stored on your device or network.

Option 1: The simplest solution... wait! 😊

The easiest way to resolve this is simply to wait.

Managing local cache issues can be tedious, and in most cases, the problematic cache will expire on its own within a few minutes to a few hours.

If you are not in a hurry, we strongly recommend doing nothing and letting the cache refresh naturally.

How to confirm it's a caching issue:

To verify that the site is actually live and only blocked for you, try the following:

• Switch browsers: Try opening your site in a different browser (e.g., Firefox instead of Chrome).
• Switch networks: Switch from your Wi-Fi to your mobile data (4G/5G).
• Switch devices: Check the site on another PC or your smartphone.

Option 2: Clearing your caches

If the site works on your phone but not your computer, you'll need to clear your local caches to identify the culprit.

1. Clear your browser cache

Start by clearing the cache and cookies in your browser settings (Chrome, Firefox, Safari, etc.).

2. Flush your local DNS cache

If your browser is clean but the site is still down, you may need to clear the DNS cache stored on your computer's operating system.

This is done via a simple terminal command.

• On Windows: Search for "Terminal" or "Command Prompt" in your search bar, then copy and paste the following command: ipconfig /flushdns

• On macOS: Open the Terminal and enter the following command: sudo killall -HUP mDNSResponder

Congratulations! Your local DNS cache is now cleared. 🎉

3. Router/ISP Cache

If you still see an error, the problem likely lies in your router's DNS cache.

To confirm this, switch to your phone's mobile data; if the site loads, your Wi-Fi network is the one "holding onto" the old data.

In this case, the best solution is to wait for the router's cache to expire, as clearing a router's DNS manually can be quite technical and varies by provider.

Updated on: 27/04/2026