About the error ERR_NAME_NOT_RESOLVED

When I visit the URL https://blog.csdn.net in the browser, I encounter an error message: blog.csdn.net's server IP address could not be found. The exception code is ERR_NAME_NOT_RESOLVED:

This error ERR_NAME_NOT_RESOLVEDmeans that your computer cannot resolve the IP address of the requested website. When you type in the browser https://blog.csdn.net, your computer will use a system called DNS (Domain Name System) to convert this URL into the server's IP address. This error can appear if the DNS server cannot find an IP address corresponding to the web address you entered, or if your computer cannot connect to the DNS server.

Below are several possible solutions.

First, clear your browser's cache and cookies. Sometimes, old DNS information cached by the browser can cause this error. You can find the option to clear cache and cookies in your browser settings.

Second, change your DNS server. Your computer may be set to use DNS servers provided by your ISP (Internet Service Provider), but sometimes there may be problems with these servers. You can use public DNS servers like Google Public DNS instead. On Windows, you can find the settings in the network settings Internet Protocol Version 4 (TCP/IPv4), then select Use the following DNS server addresses, enter Preferred DNS serverand Alternate DNS serverin and respectively .8.8.8.88.8.4.4

Third, check your hosts file. In some cases, your computer's hosts file may have been modified, causing certain URLs to resolve to the wrong IP address. On Windows, the hosts file is usually located at C:\Windows\System32\drivers\etc\hosts. You can open it with a text editor and see if there are any blog.csdn.netentries related to . If there are, you can try to delete them, then save the file.

Fourth, check your network connection. This error can also be caused if your internet connection is unstable or if your computer cannot reach the DNS server. You can try restarting your router, or connecting directly to the Internet with an Ethernet cable, and see if that fixes the problem.

Fifth, turn off VPN or proxy. If you are using a VPN or proxy, they may interfere with DNS resolution. You can try closing them and revisiting the website.

Guess you like

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