How to Fix: ERR_ICANN_NAME_COLLISION in Chrome



Updated June 2022: Stop getting error messages and slow down your system with our optimization tool. Get it now at this link
  1. Download and install the repair tool here.
  2. Let it scan your computer.
  3. The tool will then repair your computer.

If you see an ERR_ICANN_NAME_COLLISION error when browsing the Internet with Google Chrome browser on your Windows 10 PC, here are some things you might try to fix. This problem is caused by an error in a private namespace or a random redirection to a wrong proxy server.

  The site can’t be reached, This site on the company, organization or school intranet has the same URL as an external website. Try contacting your system administrator. ERR ICAN NAME COLLISION.

The reason you receive ERR_ICANN_NAME_COLLISION is that the Hosts file is not efficient at the system or browser level. I’m not sure what, but you can probably find out by running a ping command to see if it matches the entry in the hosts file. If it matches, it may be an element related to the browser.



June 2022 Update:

You can now prevent PC problems by using this tool, such as protecting you against file loss and malware. Additionally it is a great way to optimize your computer for maximum performance. The program fixes common errors that might occur on Windows systems with ease - no need for hours of troubleshooting when you have the perfect solution at your fingertips:

  • Step 1 : Download PC Repair & Optimizer Tool (Windows 10, 8, 7, XP, Vista – Microsoft Gold Certified).
  • Step 2 : Click “Start Scan” to find Windows registry issues that could be causing PC problems.
  • Step 3 : Click “Repair All” to fix all issues.

download



If it was correct to use the hosts file entry, then you should at least see an error in the way ERR_CONNECTION_REFUSED or ERR_CONNECTION_TIMED_OUT works.

You also mentioned that you got the error ERR_NAME_NOT_RESOLVED using.local. This also happens because the hosts file does not take effect. The reason why the error is different is that .dev is a TLD. If you ping the.dev domain, you will most likely get 127.0.53.53 in response.

Bypass solutions to fix this bug:

  1. Change your local domain from.dev to another domain that is not yet registered with ICANN, for example.local ;
  2. Use a different browser (Chromium, or another browser really different from Chrome).

Flush / Renew DNS

change-dns

The first thing you should try is to eliminate and renew the DNA. You can do this easily from the Windows command prompt. Click on the Start button, then type cmd in the search box. Right-click on cmd.exe, then click Run as administrator. Once the Command Prompt window appears, type the following lines one at a time and press Enter after each line.

netsh winsock reset
ipconfig /flushdnsnsnsns
ipconfig /registerdns

This clears the DNS cache and registers a new DNS that solves problems with non-reactive DNS servers.

https://github.com/cpriego/valet-linux/issues/55



Expert Tip: This repair tool scans the repositories and replaces corrupt or missing files if none of these methods have worked. It works well in most cases where the problem is due to system corruption. This tool will also optimize your system to maximize performance. It can be downloaded by Clicking Here