RECOMMENDED: Click here to fix Windows errors and optimize system performance
A name collision occurs when an attempt to resolve a name used in a private namespace, such as a top-level domain or an unqualified name, results in a request to the Public Domain Name System (DNS). If the administrative boundaries between private and public namespaces overlap, name resolution can lead to unintended or harmful results.
The problem is the fake SSL certificate that Local and/or DesktopServer adds to your system.
Problems with the fake SSL certificate prevent Chrome from accessing my local websites, for example with ERR_ICANN_NAME COLLISION or another error message indicating that the website is unavailable.
Until problems with fake SSL certificates are resolved, avoid using the local function for fake SSL certificates or continue to delete certificates if you have a problem.
Of course, this situation is a security issue for users of the private namespace who have not dealt with the new TLDs.
To minimize these risks and help network administrators detect these types of configuration issues, ICANN needs new TLD registrars to work in “controlled interruption” mode for 90 days. During the “controlled interruption”, DNS resolutions for the new TLD return the IPv4 address 127.0.0.53 instead of NXDOMAIN to increase the probability of such problems occurring.
127.0.53.53 is a localhost address, so it can be searched in network protocols, and in the case of browsing a web page, it will most likely lead to a connection error.
Checking for Whitespace
A single space, even at the empty entrance between two lines, can ruin everything. Notepad++ can help you display characters and check the number of spaces. If you have copied the host entries from another location, there may be more than one space. To make sure that spaces do not damage things, simply use spaces or tabs, not both, and end the file with a blank line.
Flush / Renew DNS
The first thing you should try is to eliminate and renew the DNS. 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
This clears the DNS cache and registers a new DNS that solves problems with non-reactive DNS servers.
RECOMMENDED: Click here to troubleshoot Windows errors and optimize system performance
CCNA, Web Developer, PC Troubleshooter
I am a computer enthusiast and a practicing IT Professional. I have years of experience behind me in computer programming, hardware troubleshooting and repair. I specialise in Web Development and Database Design. I also have a CCNA certification for Network Design and Troubleshooting.