I've been dealing with this for the first time in the last few days. There is a Web site using the CLOUDXNS DNS resolution services, the recent need for "North Shore", so hope that the process to ensure the normal stability of the site, so the use of resolution when the search engine to resolve the normal server IP address, the default resolution will be suspended, At least at the end of the working day, and then open at night or on weekends.
Because Cloudxns DNS cannot suspend the default a record alone, be sure to keep a default record, so I did not consider that it would be a random resolution of a large IP, but will be replaced by Dnspod, because the old Chiang know that dnspod can be in the resolution of the search engine node will be the default a record pause, There will be no cloudxns conflict issues.
Everything seems to be theoretically so smooth, we have encountered many times in the process of parsing, but this is so scary. After switching to dnspod, Aliyun monitor the continuous sending of alarm information, Tell 613 error (DNS resolution problem), because Aliyun monitoring has 3 monitoring nodes, turns up the alarm, sms + mail, from 613 to 200, and then from 200-613, so the day passed still.
Chiang began to think that the domain name was Qiang, but why the local open sometimes can be opened, and sometimes a DNS error. (pictured above) and through the Ping tool detection, found that there are one-third areas of timeout problem, and monitoring a 613, a 200 hint error, should not be Qing, or local can not open, from 613 error parameters can be seen is the problem of DNS.
Although we are also clear that the full analysis of the effective, need 48-72 hours, especially when the replacement of DNS, this time is really long has not been effective, so searched various tutorials, did not find a solution. However, from the beginning of 48 hours, found that the ping test node timeout less, but still have, it seems to be effective not complete the problem, and Aliyun monitoring alarm frequency is also less.
Then continue to wait, wait until 72 hours, the monitoring alarm is gone, ping test see all areas are also normal. Because these two DNS service providers are also used in peacetime, the first encounter this problem, guess that is the domain name registrars, the domain name registrar of its own DNS resolution is slow to take effect. Let's wait a few days to transfer the domain name to another registrar.
