About the ERR_NAME_NOT_RESOLVED error encountered by the browser when accessing the network

I use Chrome to visit the webpage, but the webpage cannot be opened, and I encounter the following error message:

ERR_NAME_NOT_RESOLVED

"ERR_NAME_NOT_RESOLVED" is an error page displayed in the Google Chrome browser, which means that the browser cannot resolve the domain name you entered to find the corresponding IP address, and thus cannot establish a connection to the domain name. This error can prevent you from visiting a particular website because the browser cannot find a server to connect to.

possible reason:

  1. Misspelling domain names: One of the most common mistakes is the misspelling of domain names. If you misspelled a domain name in the address bar, your browser will not be able to resolve the domain name correctly, throwing an "ERR_NAME_NOT_RESOLVED" error.

  2. DNS configuration problem: Domain name resolution is done through DNS (Domain Name System). If the domain name you enter does not have correct DNS configuration, or there is a problem with DNS configuration, the browser cannot resolve the domain name to an IP address.

  3. Internet connection issues: If you have problems with your Internet connection, your browser may not be able to communicate with the DNS server, causing the domain name to be unresolved.

  4. Firewall or proxy settings: Some firewall or proxy settings may affect domain name resolution, causing browsers to be unable to find the correct IP address.

  5. Service Provider Issues: Occasionally, a service provider's DNS servers may have issues resolving domain names correctly.

for example:

Let's say you try to visit a website called "example.com" and your browser displays an "ERR_NAME_NOT_RESOLVED" error.

  1. Misspelled domain name: First, you can check that you have entered the domain name correctly. Make sure there are no typos, such as "exampel.com" instead of "example.com".

  2. DNS configuration issues: You can try using the "nslookup" command in a terminal or command prompt to see if the domain name resolves correctly to an IP address. If no correct IP address is returned, there may be a DNS configuration issue.

  3. Internet connectivity issues: You can try visiting other websites to see if none of them are available, or if the problem is only specific. If the problem is only with a specific website, it may not be an issue with your network connection.

  4. Firewall or proxy settings: If you are using a firewall or proxy, try disabling them and visiting the website again to see if that resolves the issue.

  5. Service provider problem: If other websites can be accessed normally, but only a specific domain name has problems, it may be that the DNS server of the service provider where the domain name is located has failed.

Solution:

  1. Check your domain name spelling: Make sure you've entered your domain name without spelling mistakes and with the correct capitalization.

  2. Clear the DNS cache: Clear the local DNS cache by running "ipconfig /flushdns" (for Windows) or "sudo dscacheutil -flushcache" (for macOS) in a command prompt or terminal.

  3. Change DNS settings: Try changing your DNS settings, you can use public DNS servers such as Google's 8.8.8.8 and 8.8.4.4.

  4. Check your network connection: Make sure your network connection is working properly, try connecting to another website, and check if you can access it.

  5. Check firewalls and proxies: If you use a firewall or proxy, try disabling them and try accessing the website again.

  6. Wait for a while: If the problem is caused by your service provider's DNS servers, sometimes the problem resolves itself after a while.

Guess you like

Origin blog.csdn.net/i042416/article/details/132389794