DNS dynamic change system and method based on file synchronization

Abstract

The embodiment of the invention provides a DNS dynamic change system and method based on file synchronization, and the system comprises a database which is used for recording global data; an application programming interface API server which is connected with the database and used for reading and writing data in the database; and a domain name resolution system DNS server which is connected with the API server, is used for synchronously updating the data in the database and the content of the local configuration file. According to the technical scheme, the global database and the method for synchronizing the database and the local configuration file are utilized, stable DNS dynamic updating is achieved, and the final consistency and availability of the DNS server can be guaranteed even under the condition that the network quality is not stable.

Description

technical field [0001] The invention relates to the field of computer technology, in particular to a system and method for dynamically changing DNS based on file synchronization. Background technique [0002] The current Internet access method relies on the domain name system. The DNS (Domain Name System) server provides services for users according to the domain name-IP address binding relationship set, and returns the IP address corresponding to the domain name according to the queried domain name. [0003] In general, a DNS server consists of a group of multiple machines. In general, DNS server records can be placed in a local database or configuration file; or, all servers share a remote database to provide services. [0004] When the domain name needs to be changed, if the remote database is shared, the data in the database can be directly modified, and the DNS return results of all servers can be updated at this time. [0005] In the case of a local database, in gener...

AI Technical Summary

Problems solved by technology

[0007] In the case of the above-mentioned shared database, there will be a single point problem, because the database is a single point in the entire architecture. If there is a problem with the public database, all DNS servers will fail to connect to the database and cause all queries to fail, resulting in catastrophe. Consequences, at the same time, the network delay problem to the database will also cause the query speed to slow down, and there are very few similar deployment situations in actual production

[0008] In the case of local databases, because each update needs to send an update command, it is easy to cause some machines to fail to update due to network problems, and complex result judgment and retry logic need to be added. In addition, order issues also need to be considered. If executed in parallel Update commands, there may be a sequence error due to network reasons, and the update commands sent later will be executed first, so they must be executed sequentially, which is very inefficient

Therefore, in the case of unstable network quality, it is difficult to ensure that the database of each DNS server maintains the final consistent state, which will seriously affect the service stability of the DNS server

Images