The Phantom Loading Error
When you type a web address like wikipedia.org into Google Chrome, the browser asks a DNS server to translate that name into an IP address (like 192.168.1.1). To make browsing faster, Chrome locally caches (memorizes) that IP address on your hard drive. The next time you visit the site, Chrome instantly connects to the memorized IP instead of asking the server again. However, if a website recently migrated to a new server with a new IP address, Chrome will stubbornly try to connect to the old, cached IP address, resulting in a “Site cannot be reached” error, even though the website works perfectly fine on your phone. To fix this phantom error, you must manually flush Chrome’s internal DNS cache.
How to Clear the Chrome DNS Cache
You cannot clear the internal DNS cache using the standard “Clear Browsing Data” menu. You must use Chrome’s hidden internal networking dashboard.
- Open the Google Chrome desktop browser.
- Click inside the main address bar, type exactly
chrome://net-internals/#dns, and press Enter. - You will be taken to a stark, text-only developer page.
- Look under the “Host resolver cache” section for a button labeled Clear host cache.
- Click the Clear host cache button once. (Note: The button will not flash, and no confirmation pop-up will appear, but the action is instantaneous).
Flushing the Sockets
To ensure a completely clean slate, you should also flush the active connection sockets.
- Look at the left-hand sidebar on that same page and click on Sockets.
- Click the button labeled Flush socket pools.
Close the internal dashboard tab and navigate back to the broken website. Chrome will now be forced to execute a brand-new DNS lookup, grabbing the correct, updated IP address and successfully loading the page.