How to solve the DNS server failure

DNS server failure is a very troublesome thing. The most common symptom is that the web page cannot be accessed. Since you know that it is DNS server failure, you should apply the right medicine to solve the problem of DNS server failure. See the specific methods together!

Method steps

1. After opening the network neighborhood, call the local connection and right-click properties

2. Open the IPv4 option and double-click it

3. Click the manually set DNS radio box and fill in 8.8.8.8 below

Note: 8.8.8.8 is Google's DNS server. Generally, there will be no problem.

4. Then, find the local connection, disable it first, and then enable it:

5. After setting, click OK and visit the web page again. You will find that you can visit it.

Supplement: server introduction

Servers, also known as servers, are devices that provide computing services. Since the server needs to respond to service requests and process them, generally speaking, the server should have the ability to undertake services and ensure services.

The composition of the server includes processor, hard disk, memory, system bus, etc., which is similar to the general computer architecture. However, due to the need to provide highly reliable services, it requires high processing capacity, stability, reliability, security, scalability, manageability and so on.

In the network environment, according to the different types of services provided by the server, it is divided into file server, database server, application server, web server, etc.

Related reading: what are the server FAQs

  1. System blue screen, frequent crash, restart, slow response

The of the server is very similar to our ordinary computer, whether it is hardware structure or running system. Therefore, just like our computers, they may be infected with viruses, crash, blue screen, restart and other failures due to system vulnerabilities, software conflicts and hardware failures, and slow response due to too much garbage cache information.

  2. The remote desktop connection exceeds the maximum number of connections

Since the server allows 2 connections by default, if you forget to log off after logging in and directly close the remote desktop, the server recognizes that the login is still on the server side. In this case, the most common is to restart the server. However, if it is the peak period, the loss caused by restarting the server is obvious. At this time, you can use the mstsc / console command to forcibly log in. Open the "run" box and type "mstsc / V: xxx.xxx.xxx.xxx (server IP) / console" to forcibly log in to the remote desktop.

  3. How to clean up files that cannot be deleted

In this case, it may be that the file is still running. You can restart and delete it, or run CMD, enter the name of the folder arrtib-a-s-h-r you want to delete, and finally enter the name of the folder del wants to delete. It cannot be recovered after running this command. Please use it with caution.

  4. Hidden trouble of system port

For the server, the first thing is to ensure stability and security. Therefore, we only need to ensure the most basic functions of the server, just like the sound card is prohibited by default. We don't need too many functions and port support. For example, some unnecessary and high-risk ports can be blocked. For some necessary and risky ports, such as ports 3389 and 80, we can set them as non-special secret ports by modifying the registry, so that the security hidden dangers of server ports no longer exist.