How to Fix Chrome ‘Resolving Host’ Slow Loading

Understanding the ‘Resolving Host’ Issue in Chrome

Experiencing slow loading times in Chrome due to ‘Resolving Host’ issues can be frustrating. This problem often results from DNS server delays, causing Chrome to take longer than usual to resolve website addresses. Fortunately, there are several effective methods to fix the Chrome ‘resolving host’ slow loading problem.

Quick Fixes to Try First

  • Restart your router to refresh your internet connection.
  • Close and restart Chrome.
  • Clear your browser cache: Settings > Privacy and Security > Clear Browsing Data.
  • Disable any VPN connections that might be interfering with DNS resolution.

Changing to Faster DNS Servers

Switching to a faster DNS server can significantly reduce the time Chrome takes to resolve hostnames. Here’s how to change DNS settings across different platforms:

Windows

  1. Press Windows + R, type ncpa.cpl, and press Enter.
  2. Right-click on your active network connection and select Properties.
  3. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
  4. Choose Use the following DNS server addresses and enter the preferred DNS server addresses (e.g., Google DNS: 8.8.8.8 and 8.8.4.4).
  5. Click OK to save changes.

macOS

  1. Open System Preferences and select Network.
  2. Select your network connection and click Advanced.
  3. Go to the DNS tab and click the + button to add a new DNS server (e.g., Google DNS: 8.8.8.8, 8.8.4.4).
  4. Click OK and then Apply to save changes.

Linux

  1. Edit the /etc/resolv.conf file with a text editor.
  2. Add or modify the lines to include preferred DNS servers like Google’s: nameserver 8.8.8.8 and nameserver 8.8.4.4.
  3. Save the file and restart your network service.

Flushing DNS Cache

Flushing the DNS cache can clear outdated or corrupted DNS records, helping Chrome resolve hosts more efficiently.

Windows

  1. Press Windows + R, type cmd, and press Enter.
  2. In the command prompt, type ipconfig /flushdns and press Enter.
  3. A confirmation message will appear once the DNS cache is flushed.

macOS

  1. Open Terminal from Applications > Utilities.
  2. Type the command sudo killall -HUP mDNSResponder and press Enter.
  3. Enter your password if prompted and wait for the process to complete.

Linux

  1. Open a terminal window.
  2. Type sudo systemd-resolve --flush-caches and press Enter.

Disabling DNS Prediction

DNS prediction is designed to speed up browsing by resolving DNS entries before you visit them. However, it can sometimes cause issues.

  1. Open Chrome and go to chrome://settings.
  2. Scroll down and click Privacy and Security.
  3. Click on Cookies and other site data.
  4. Toggle off the option labeled Preload pages for faster browsing and searching.

Checking Hosts File

Incorrect entries in the hosts file can interfere with DNS resolution.

Windows

  1. Navigate to C:\Windows\System32\drivers\etc.
  2. Open the hosts file with a text editor like Notepad.
  3. Look for any incorrect or suspicious entries and remove them.
  4. Save the file and restart your computer.

macOS and Linux

  1. Open a terminal window.
  2. Type sudo nano /etc/hosts and press Enter.
  3. Remove any incorrect or suspicious entries.
  4. Press Ctrl + X, then Y, and Enter to save changes.

IPv6 vs IPv4 DNS Issues

Sometimes, using IPv6 DNS can cause resolving host issues. You can configure Chrome to use IPv4 DNS instead.

  1. Open Chrome and go to chrome://settings.
  2. Scroll down to Advanced and click it to expand.
  3. In the System section, toggle the option to use hardware acceleration when available.
  4. Restart Chrome for changes to take effect.

Conclusion

By following these steps, you should be able to resolve the slow loading issue caused by Chrome ‘resolving host’ problems. Whether it’s changing your DNS server, flushing the DNS cache, or adjusting settings in Chrome, each solution targets common causes of this issue. If problems persist, consider consulting the official Google Chrome Help Center for further assistance.