Scarecrow Intelligent DNS Resolution

1. The best smart DNS should be the most stable, and stability is the first priority.

There are two unstable factors. One is that the DNS cannot be resolved due to server failure, and the other is that the DNS cannot be resolved due to network line failure. The solution is to place multiple servers in different computer rooms to work at the same time, which can completely ensure the stable operation of the entire system, because the DNS service mechanism is that as long as one server is normal, it can provide correct resolution.

Our company has three intelligent DNS servers in the computer room of Qingdao Telecom Center and three intelligent DNS servers in the computer room of Rizhao Netcom Center. They form this intelligent DNS service system. The probability that the computer rooms of these two different service providers will fail at the same time is basically zero. So don't worry about system stability. We can work stably 24 hours a day.

2. Secondly, the standard for evaluating smart DNS should be its "intelligence".

The key to intelligence or not is whether the IP segment data of the system is the latest and most complete. This is the soul of the intelligent DNS service system. We have the latest and most complete IP addresses in China, and we check for updates every week.

3. The third factor is the resolution speed of the system.

In fact, this indicator is not too important. But many smart DNS service providers put this in a particularly important position to promote. Why is this indicator not very important? This should be discussed from the DNS service mechanism. When a user accesses a domain name, he will first send a resolution request to his local DNS server (companies that provide Internet services generally provide DNS resolution servers).

If no one under the same local DNS has visited the domain name before you access the domain name, your request will eventually be sent to the smart DNS server to get the correct IP resolution result. Please note that this result will be returned to your local DNS. , and remain on the DNS for a period of time (usually 1 hour, or 24 hours, this can be defined). During the retention period, when another user (or you) accesses the domain name again, the request will be responded to on the local DNS and no more requests will be sent to the smart DNS server. So if you have many access users, the parsing speed basically does not need to be considered.

4. Other extended functions

We provide a service that automatically transfers servers to normal servers when they are down, and we also provide a multiplication service that automatically alerts Fetion of server failures.