Solution to the failure to find the server or DNS error on the webpage

1. Use nslookup to determine whether a DNS resolution fault is true: (This step is to confirm whether a DNS error is caused ), to fully determine whether a DNS resolution fault exists, you must use the NSLOOKUP provided by the system.

1. Choose Start> Run> enter CMD and press enter to enter the command line mode;

2. Enter the nslookup command and press enter to go to the DNS resolution query interface;

3. The command line window displays the DNS server address used by the current system, for example, 202.106.0.20;

4. Enter the domain name of the site you cannot access. If it cannot be accessed, DNS resolution may fail. We will receive a prompt message for DNS request timed out and timeout was 2 seconds. This shows that our computer does have a DNS resolution fault.

Tip: If DNS resolution is normal, the correct IP address will be returned.

2. Check whether the DNS server is working properly: (This step is to query your DNS and remember to connect to the broadband). At this time, we need to check the DNS address used by our computer, and query the running status of the instance.

1. Open start> Run> enter CMD in win7 and press enter to enter command line mode;

2. Enter the ipconfig/all command to query network parameters.

3. In the ipconfig/all display information, we can see that "DNS server" is the address of our DNS server. Step 4: If your company's internal network address is displayed at the DNS server, it means that your company's DNS resolution work is handed over to the internal DNS server, in this case, we need to check the DNS server and perform the nslookup operation on the DNS server to check whether the resolution can be normal. The DNS service fault on the DNS server can be solved in general.

(3) clear DNS cache information:

When a computer accesses a domain name, it does not need to seek help from the DNS server every time it accesses the domain name. Generally, after the resolution is completed once, this resolution entry is saved in the DNS cache list of the computer. If the DNS resolution changes, the DNS cache list information does not change, when the computer accesses this domain name, it still does not connect to the DNS server to obtain the latest resolution information. It will be resolved based on the cache correspondence saved on its computer, so that DNS resolution will fail. In this case, we should clear the DNS cache command to solve the fault.

Step 1: Choose Start> Run> enter CMD to enter the command line mode.

Step 2: in command line mode, we can see in ipconfig /? There is a parameter named/flushdns, which is the command to clear DNS cache information.

Step 3: run the ipconfig/flushdns command. When "successfully flushed the dns resolver cache" appears (the DNS resolution cache has been successfully refreshed) the prompt indicates that the cache information of the current computer has been cleared successfully.

Step 4: When we access the domain name again, we will get the latest resolution address on the DNS server, and there will no longer be a resolution error caused by the previous cache.

(4) modify the HOSTS file method: (I have not tried this method, but you can try software such as 360 or master optimization to modify the Hosts file)

The modification of the HOSTS method is to modify the DNS resolution correspondence in the HOSTS file to achieve correct resolution. When accessing a domain name on the local computer, the HOSTS file in the local system will be checked first. The priority of the resolution relationship in the HOSTS file is higher than that on the DNS server.

In this way, if you want to bind a domain name to an IP address, you can add a resolution entry to the HOSTS file.

Step 1: Use "Start-> Search" to search for a file named hosts.

Step 2: Of course, readers who already know the path can directly find the HOSTS file in the c: \ windows \ system32 \ drivers \ etc directory. If your system is windows 2000, search for it in the c: \ winnt \ system32 \ drivers \ etc directory.

Step 3: Double-click the HOSTS file and select to open it with the "notepad" program.

Step 4: We will see all the content in the HOSTS file. By default, there is only one line of content "127.0.0.1 localhost ". (Other rows with # in front of them are not real content, but help information)