Shulou(Shulou.com)06/01 Report--

From the first two articles, I believe you already have some understanding of the powerful subdivision lines, high-end private lines, and unique load balancing records in CloudXNS. Recently, many people have asked about the X optimization feature that was launched not long ago, although it is explained in our help documentation (what is X optimization? ), but still can not satisfy the strong curiosity of my friends.

Therefore, the last article in this series will reveal the meaning of X optimization.

4: the sharp weapon of the lazy in the new era-- X optimization

In the last week of March 2015, we launched the X Optimization feature, and many of our friends are confused about this feature. In fact, X optimization is a feature that makes it easier to configure multiple ip domain names. Some may have a headache when managing a bunch of domain names and ip. When there are too many lines and enough IP, they want to set up a little more fine, but because there are too many domain names and IPs to manage and can not remember the specific source of each ip, it is not only troublesome but also prone to errors.

With the X optimization feature, you can fill all the ip into the default line of the whole network, and then turn on X optimization, and everything will be at ease. X optimization has two settings, the sensitivity is used to control the range of candidate ip, the higher the sensitivity is, the less the number of candidate ip is; the maximum number of returns controls the maximum number of ip returned by DNS, and when the candidate ip exceeds the maximum number of returns, the specified number is sorted according to sensitivity, and if the maximum number of returns is less than the maximum number of returns, all candidate ip is returned.

Let's do another test. The editor randomly found ip from six different regions and operators on the Internet (these ip are pure fiction, if any similarities, pure coincidence): 27.30.100.54 (Hubei Telecom), 117.135.192.43 (Guizhou Mobile), 1.0.63.201 (Guangdong Telecom), 1.15.103.220 (Beijing Unicom), 1.85.14.56 (Shaanxi Telecom) and 3.66.21.17 (USA). All are configured to the domain name www.chinatesters.cn network default line, as shown in the figure:

One button turns on X optimization, setting low sensitivity and a maximum of 3 returns, when simulating the access of Wuhan Telecom users:

We see that three ip are returned from Hubei Telecom, Guangdong Telecom and Shaanxi Telecom.

Then modify the setting to high sensitivity and the maximum return number of 5, also through the dig command test to simulate Wuhan Telecom user access, can only get one result from Hubei Telecom.

Then some people may ask, what if there is no A record for the carrier or region that happens to correspond to the user's ip? Let's do the final verification, keep the above configuration with high sensitivity and a maximum of 5 returns unchanged, delete the A records of Hubei Telecom, Guangdong Telecom and Shanxi Telecom and test them again. The resolution record is as shown in the figure:

The test results are shown in the figure below. Since the ip from Guizhou Mobile and Beijing Unicom is the fastest of the three records from the client ip that initiated the request to the server ip network link, you will get these two A record results.

Summary

How's it going? Seeing here, do you have a new understanding of our CloudXNS? Is there a way to subvert your previous understanding of intelligent DNS parsing? Will you expect more useful and intimate features? If your answer is yes, then come to CloudXNS to register your account and start a magical journey of domain name resolution.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.