A blockchain-based zone transmission system and method

Abstract

The application discloses a kind of based on blockchain's area transmission system and method, introduce the area blockchain network and decision control module composed of several main area agent servers, decision control module according to the position distance of auxiliary area server and main area agent server and the pressure condition of main area agent server, auxiliary area server is assigned main area agent server, improve the efficiency of area synchronization;Auxiliary area server is synchronized to the assigned main area agent server, instead of directly from main area server synchronization;When main area server has update, it initiates notification to main area agent server actively, and triggers synchronization actively, so as to guarantee the consistency of data between main area server and main area agent server;And by blockchain technology, each main area agent server area data is also synchronized, also play the effect of tamper-proof, improve the trustworthiness of area data.

Description

Technical Field

[0001] The present application belongs to the technical field of DNS query services, and specifically relates to a system and method for synchronizing data between a secondary zone server and a primary zone server. Background Art

[0002] A DNS server can act as a primary zone server or a secondary zone server. The secondary zone server ensures the consistency of the configuration of the two by synchronizing the data of the primary zone server. Currently, DNS primary and secondary zone synchronization supports incremental synchronization (IXFR) and full synchronization (AXFR). When the secondary zone server initiates a synchronization request to the primary zone server, it also submits the SOA number (Start of Authority, a record used to identify the version of the zone data) of the secondary zone server's current zone configuration. If the primary zone server has an SOA number, the configuration that has changed since the last synchronization will be passed to the secondary zone server, which is incremental synchronization (IXFR). If the primary zone server does not have an SOA number, the full zone configuration will be passed to the secondary zone server, which is full synchronization (AXFR).

[0003] The existing technology mainly has the following problems:

[0004] 1. When there are many servers in the secondary zone, the primary zone server will be under great pressure when the secondary zone servers send requests to the primary zone server concurrently;

[0005] 2. When the primary zone server is far away from the secondary zone server, transmitting large amounts of data will cause serious network bandwidth usage. At the same time, network failures can easily lead to synchronization failures and high synchronization delays.

[0006] 3. The primary zone server is directly exposed to the secondary zone server and is vulnerable to attacks, such as DDoS attacks, which will affect the stability and reliability of the DNS service. Summary of the Invention

[0007] The present application provides a blockchain-based zone transmission system and method, which mainly solves the problems of concurrent synchronization requests from auxiliary zone servers in the existing technology and the great pressure on the primary zone server when the primary zone server is far away from the auxiliary zone server, serious network bandwidth occupancy, and possible synchronization failure and high synchronization delay.

[0008] In a first aspect, a blockchain-based zone transmission system includes a primary zone server and a secondary zone server; the system further includes a decision control module and a blockchain network composed of a plurality of primary zone proxy servers; the decision control module establishes communication connections with the secondary zone servers and the blockchain network, respectively, and the blockchain network establishes communication connections with the primary zone server;

[0009] The decision control module is used to allocate a primary-area proxy server to the secondary-area server based on the distance between the secondary-area server and each primary-area proxy server and the load of each primary-area proxy server; the currently allocated primary-area proxy server is recorded as the first primary-area proxy server, and the decision control module sends the information of the secondary-area server to the first primary-area proxy server, and simultaneously synchronizes the node information of the first primary-area proxy server to the secondary-area server;

[0010] The first primary zone proxy server responds to the zone synchronization request of the secondary zone server on behalf of the primary zone server, thereby indirectly achieving zone data synchronization between the secondary zone server and the primary zone server;

[0011] When the master zone server receives a zone update, it actively initiates synchronization with any master zone proxy server in the blockchain network, so that the zone data in the master zone server is synchronized to the master zone proxy server in a timely manner, and then realizes data synchronization between the master zone proxy server clusters through blockchain technology.

[0012] Optionally, the decision control module also provides authentication of the secondary zone server: in response to a request initiated by the secondary zone server to query the primary zone proxy server, the validity of the secondary zone server is first verified, and after the verification is passed, the node information of the first primary zone proxy server is returned to the secondary zone server.

[0013] In a second aspect, a blockchain-based zone transfer method is applied to the blockchain-based zone transfer system, the method comprising:

[0014] The auxiliary zone server initiates a request to the decision control module to query the primary zone proxy server;

[0015] In response to the request to query the primary-area proxy server, the decision control module allocates a primary-area proxy server to the secondary-area server based on the distance between the secondary-area server and each primary-area proxy server and the load of each primary-area proxy server, and records the currently allocated primary-area proxy server as the first primary-area proxy server. The decision control module then sends the information of the secondary-area server to the first primary-area proxy server and synchronizes the node information of the first primary-area proxy server with the secondary-area server.

[0016] The secondary zone server initiates a zone synchronization request to the first primary zone proxy server;

[0017] The first primary zone proxy server responds to the zone synchronization request from the secondary zone server and checks whether there is a matching SOA record locally;

[0018] If yes, synchronize the latest recorded incremental data to the auxiliary zone server;

[0019] If not, synchronize all data to the auxiliary zone server; there are two specific cases:

[0020] If the first primary zone proxy server has zone data, the first primary zone proxy server will synchronize the full zone data to the secondary zone server;

[0021] If the first primary zone proxy server does not have zone data, the first primary zone proxy server initiates a full zone synchronization request to the primary zone server, and the primary zone server synchronizes the full zone data to the primary zone proxy server; the primary zone proxy server stores the full zone data upon receiving it, and synchronizes the full zone data to the secondary zone server;

[0022] When the master zone server receives a zone update, it actively initiates synchronization with any master zone proxy server in the blockchain network, so that the zone data in the master zone server is synchronized to the master zone proxy server in a timely manner, and then realizes data synchronization between the master zone proxy server clusters through blockchain technology.

[0023] Optionally, in response to the request to query the primary zone proxy server, the decision control module first verifies the signature information of the secondary zone server, and records the IP information of the secondary zone server after the verification is passed; then the decision control module synchronizes the authentication information of the secondary zone server to all primary zone proxy servers in the blockchain network, and the authentication information includes the IP information and token information of the secondary zone server; accordingly, the secondary zone server also carries token information when initiating a zone synchronization request to the first primary zone proxy server; when the first primary zone proxy server receives the zone synchronization request from the secondary zone server, it first verifies the IP address of the secondary zone server, and terminates the synchronization request if there is a match; if there is a match, it continues to verify the token information, and if there is a match, it terminates the synchronization request, and only proceeds to subsequent steps if there is a match.

[0024] Optionally, the node information content of the first primary area proxy server includes: the node IP of the first primary area proxy server, time validity, and token information used for authentication.

[0025] Optionally, when the master zone server receives a zone update, it actively initiates synchronization to any master zone proxy server in the blockchain network. Specifically, the master zone server sends an update notification message to any master zone proxy server in the blockchain network. The master zone proxy server initiates an incremental synchronization request to the master zone server based on the update notification message. The master zone server responds to the incremental synchronization request and synchronizes the zone data to the master zone proxy server, thereby maintaining the consistency of the data of the master zone server and the master zone proxy server.

[0026] Optionally, any one of the primary zone proxy servers may also periodically initiate an incremental synchronization request to the primary zone server.

[0027] Optionally, the blockchain network composed of several main zone proxy servers is pre-configured with trusted authentication and a secure synchronization zone data link is established between the main zone server, the information of the main zone server is filled in the main zone proxy server, and the information of the main zone proxy server is filled in the main zone server.

[0028] Compared with the prior art, this application has at least the following beneficial effects:

[0029] This application introduces a blockchain network composed of several main zone proxy servers and a decision-making control module. The auxiliary zone server synchronizes with the main zone proxy server instead of directly synchronizing from the main zone server, thereby reducing the pressure on the main zone server; when the main zone server has an update, it actively notifies the main zone proxy server and actively triggers synchronization, thereby ensuring the consistency of data between the main zone server and the main zone proxy server; and synchronizes the zone data of each main zone proxy server through blockchain technology, which also has an anti-tampering effect and improves the credibility of the zone data; the decision-making control module allocates the main zone proxy server to the auxiliary zone server according to the location distance between the auxiliary zone server and the main zone proxy server and the pressure of the main zone proxy server, thereby improving the efficiency of zone synchronization and solving the problems of bandwidth occupation, delay and easy failure of long-distance transmission.

[0030] In order to prevent the situation where the primary zone server is unable to initiate notifications to the primary zone proxy server, the primary zone proxy server also regularly initiates incremental synchronization requests to the primary zone server, thereby ensuring the consistency of data between the primary zone server and the primary zone proxy server.

[0031] The decision control module first verifies the auxiliary zone server, filters out illegal servers, and only synchronizes the information of the legal auxiliary zone server to the main zone proxy server, and returns the information of the main zone proxy server to the legal auxiliary zone server. The main zone proxy server also supports security authentication processing accordingly, and the zone synchronization protocol supports carrying authentication information, which solves the security access problem of auxiliary zone synchronization, thereby effectively protecting the main zone proxy server and the main zone server. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 A schematic diagram of the architecture of a blockchain-based zone transmission system provided for one embodiment of the present application. DETAILED DESCRIPTION

[0033] In order to make the purpose, technical solutions and advantages of this application more clear, this application is further described in detail below with reference to the accompanying drawings and embodiments.

[0034] In the description of this application: The terms "first" and "second" in this application are intended to distinguish the objects referred to and do not have any special meaning in terms of technical connotation (for example, they should not be understood as emphasizing the degree of importance or order, etc.). Expressions such as "including", "comprising", and "having" also mean "not limited to" (certain units, components, steps, etc.).

[0035] In one embodiment, Figure 1 As shown, a blockchain-based zone transmission system is provided.

[0036] The functions and relationships of each part are described as follows:

[0037] Auxiliary zone server: Auxiliary zone server in primary-auxiliary zone synchronization, client server in zone synchronization.

[0038] Primary zone server: The server for the original primary zone synchronization and the server for the original primary-secondary zone synchronization.

[0039] Primary zone proxy server: A server that directly provides primary zone synchronization to secondary zone servers. Primary zone proxy servers synchronize data with each other through the blockchain. The data in the primary zone proxy server comes from the primary zone server.

[0040] Decision control module: Provides the node information of the primary zone proxy server to the secondary zone server and provides authentication for the secondary zone server.

[0041] The interaction is described as follows:

[0042] The auxiliary zone server queries the zone management controller for the node information of the primary zone proxy server;

[0043] The secondary zone server synchronizes the zone from the primary zone proxy server;

[0044] The decision control module synchronizes the node information and SOA information of the main zone proxy server from the blockchain network;

[0045] The primary zone server actively or passively synchronizes zone information to the primary zone proxy server.

[0046] The specific functions of the decision control module and the main zone proxy server are as follows:

[0047] The decision-making control module assigns a primary proxy server to a secondary server based on the distance between the secondary server and each primary proxy server and the load of each primary proxy server. The currently assigned primary proxy server is designated as the first primary proxy server. The decision-making control module then sends the secondary server's information to the first primary proxy server and synchronizes the first primary proxy server's node information with the secondary server. The first primary proxy server responds to zone synchronization requests from the secondary server on behalf of the primary server, indirectly synchronizing zone data between the secondary and primary servers. When a primary server receives a zone update, it proactively initiates synchronization with any primary proxy server in the blockchain network, ensuring that the zone data on the primary server is promptly synchronized with the primary proxy server. This, in turn, enables data synchronization between the primary proxy server clusters using blockchain technology.

[0048] In this embodiment, the auxiliary zone server establishes a connection with the main zone proxy server assigned by the decision control module, which is closer and has a smaller load pressure. The main zone proxy server synchronizes data to the auxiliary zone, thereby solving the problem of network bandwidth occupation and synchronization failure caused by the long distance. At the same time, multiple main zone proxy servers are used as the actual synchronizers of the main zone server, thereby reducing the pressure on the main zone server, and data synchronization between the main zone proxy server clusters is carried out through blockchain technology, thereby achieving the goal of anti-tampering and improving the credibility of zone data. In addition, the synchronization decision control module can also first verify the legitimacy of the auxiliary zone server, and then return the information of the main zone proxy server to the auxiliary zone server if it passes, thereby effectively protecting the main zone proxy server and the main zone server.

[0049] In one embodiment, a zone transfer method based on the above system includes the following steps:

[0050] 1. The auxiliary zone server sends a query request to the decision control module for the primary zone proxy server;

[0051] 2. The decision-making control module verifies the legitimacy of the secondary zone server and assigns the node information of the primary zone proxy server to the secondary zone server. The node information includes: the node IP address of the primary zone proxy server, the validity period, and the token used for authentication. The primary zone proxy server is selected based on the distance from the secondary zone server and the current pressure on the primary zone proxy server. The decision-making control module verifies the secondary zone server through the client's signature, such as username / password, zero trust, etc.

[0052] 3. The decision control module synchronizes the authentication information of the auxiliary zone server to the primary zone proxy server. The synchronized information includes the source IP and token information of the auxiliary server.

[0053] 4. The secondary zone server initiates a zone synchronization request to the primary zone proxy server based on the information of the primary zone proxy server, and carries token information;

[0054] 5. When the primary zone proxy server receives a zone synchronization request from the secondary zone server, it first verifies the IP address of the secondary zone server. If it does not match, the synchronization request is terminated. If it does match, it continues to verify the token information. If it does not match, the synchronization request is terminated. Otherwise, it continues with the subsequent steps.

[0055] 6. The primary zone proxy server checks whether there is a matching SOA record locally. If so, it synchronizes the matching SOA to the latest record to the secondary zone server. If not, but the primary zone proxy server has zone data, it synchronizes the full zone data to the secondary zone server.

[0056] 7. If the primary zone proxy server does not have zone data, it will initiate a full zone synchronization request to the primary zone server, and the primary zone server will synchronize the full zone data to the primary zone proxy server. When the primary zone proxy server receives the full zone data, it will store it and transfer the zone to the secondary zone server.

[0057] When the master zone server receives a zone update, it actively initiates synchronization with the master zone proxy server (it can initiate synchronization with any master zone proxy server); the master zone proxy server initiates an incremental synchronization request based on the notification of the master zone proxy server, and synchronizes the zone data in the master zone server to the master zone proxy server in a timely manner, thereby maintaining the consistency of the data between the master zone server and the master zone proxy server.

[0058] In order to prevent the situation where the main zone server is unable to initiate notification to the main zone proxy server, the main zone proxy server (can be any main zone proxy server) also regularly initiates incremental synchronization requests to the main zone server to ensure the consistency of data between the main zone server and the main zone proxy server.

[0059] In the above method, the specific example of the data synchronization process between the main zone server and the main zone proxy server is as follows:

[0060] 1) Configure trusted authentication and establish a secure synchronization zone data link between the main zone proxy server network and the main zone server. Fill in the main zone server information to the main zone proxy server, and fill in the main zone proxy server information to the main zone server. This information includes: IP address, signature, etc.

[0061] 2) When the primary zone proxy server network starts, the primary zone proxy server directly initiates a zone synchronization request to the primary zone server using the zone synchronization protocol;

[0062] 3) When the primary zone server receives a zone synchronization request from the primary zone proxy server, if the local server has an SOA record, it will incrementally synchronize the zone data to the primary zone proxy server; otherwise, it will fully synchronize the zone data to the primary zone proxy server to ensure data consistency between the primary zone proxy server and the primary zone server during the initialization phase;

[0063] 4) When the main zone server has zone data updated, it requests to notify the main zone proxy server through https or other methods. When the main zone proxy server receives the notification request, it completes the zone data synchronization through the process of step 3).

[0064] In the above method, a specific example of the process of the auxiliary zone server triggering zone synchronization data is as follows:

[0065] 1) The auxiliary zone server regularly initiates zone synchronization requests, first requesting node information from the decision control server via https;

[0066] 2) When the decision control server receives a request from a secondary server, it first verifies the secondary server's signature information. If the verification is successful, it records the secondary server's IP information and generates a random token. It also records the secondary server's IP information and the generated token information. It then selects a suitable primary proxy server based on the distance between the secondary server and the primary proxy server and the primary proxy server's load. It then synchronizes the secondary server's IP information and the generated token information to the selected primary proxy server, and simultaneously synchronizes the primary proxy server's IP information and token information to the secondary server.

[0067] 3) The secondary zone server initiates a zone synchronization request based on the IP information of the primary zone proxy server, carrying the local SOA information and token information;

[0068] 4) When the primary zone proxy server receives a zone synchronization request, it first checks whether the IP information of the secondary zone server matches the IP information synchronized to the primary zone proxy server by the decision control server. If it passes, it then checks whether it matches the token information. Only after all passes, the zone synchronization is performed;

[0069] 5) The primary zone proxy server checks whether the received SOA exists on the local machine. If so, it returns the incremental data from the SOA to the latest record. Otherwise, it returns the full data of the existing zone. If the zone data does not exist, it goes to the next step.

[0070] 6) The primary zone proxy server initiates a zone synchronization request to the primary server, stores the zone data upon receiving it, and returns the full amount of zone synchronization data to the secondary zone server at the same time; the primary zone proxy server synchronizes the zone data to other primary zone proxy servers through the blockchain network.

[0071] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

Claims

1. A blockchain-based zone transmission system, comprising a primary zone server and a secondary zone server; characterized in that: It also includes a decision control module and a blockchain network composed of several primary zone proxy servers; the decision control module establishes communication connections with the secondary zone servers and the blockchain network respectively, and the blockchain network establishes communication connections with the primary zone servers; The decision control module is used to allocate a primary-area proxy server to the secondary-area server based on the distance between the secondary-area server and each primary-area proxy server and the load of each primary-area proxy server; the currently allocated primary-area proxy server is recorded as the first primary-area proxy server, and the decision control module sends the information of the secondary-area server to the first primary-area proxy server, and simultaneously synchronizes the node information of the first primary-area proxy server to the secondary-area server; The first primary zone proxy server responds to the zone synchronization request of the secondary zone server on behalf of the primary zone server, thereby indirectly achieving zone data synchronization between the secondary zone server and the primary zone server; When the master zone server receives a zone update, it actively initiates synchronization with any master zone proxy server in the blockchain network, so that the zone data in the master zone server is synchronized to the master zone proxy server in a timely manner, and then realizes data synchronization between the master zone proxy server clusters through blockchain technology.

2. The blockchain-based zone transmission system according to claim 1, characterized in that The decision control module also provides authentication for the secondary zone server: in response to a request initiated by the secondary zone server to query the primary zone proxy server, the module first verifies the legitimacy of the secondary zone server, and then returns the node information of the first primary zone proxy server to the secondary zone server after the verification is passed.

3. A block chain-based zone transmission method, characterized in that: Applied to the blockchain-based zone transmission system of claim 1, the method comprises: The auxiliary zone server initiates a request to the decision control module to query the primary zone proxy server; In response to the request to query the primary-area proxy server, the decision control module allocates a primary-area proxy server to the secondary-area server based on the distance between the secondary-area server and each primary-area proxy server and the load of each primary-area proxy server, and records the currently allocated primary-area proxy server as the first primary-area proxy server. The decision control module then sends the information of the secondary-area server to the first primary-area proxy server and synchronizes the node information of the first primary-area proxy server with the secondary-area server. The secondary zone server initiates a zone synchronization request to the first primary zone proxy server; The first primary zone proxy server responds to the zone synchronization request from the secondary zone server and checks whether there is a matching SOA record locally; If yes, synchronize the latest recorded incremental data to the auxiliary zone server; If not, synchronize all data to the auxiliary zone server; there are two specific cases: If the first primary zone proxy server has zone data, the first primary zone proxy server will synchronize the full zone data to the secondary zone server; If the first primary zone proxy server does not have zone data, the first primary zone proxy server initiates a full zone synchronization request to the primary zone server, and the primary zone server synchronizes the full zone data to the primary zone proxy server; the primary zone proxy server stores the full zone data upon receiving it, and synchronizes the full zone data to the secondary zone server; When the master zone server receives a zone update, it actively initiates synchronization with any master zone proxy server in the blockchain network, so that the zone data in the master zone server is synchronized to the master zone proxy server in a timely manner, and then realizes data synchronization between the master zone proxy server clusters through blockchain technology.

4. The blockchain-based zone transmission method according to claim 3, characterized in that: The decision control module responds to the request to query the primary zone proxy server by first verifying the signature information of the secondary zone server and recording the IP information of the secondary zone server after the verification is passed; The decision control module then synchronizes the authentication information of the secondary zone server to all primary zone proxy servers in the blockchain network. The authentication information includes the IP information and token information of the secondary zone server. Correspondingly, when the secondary zone server initiates a zone synchronization request to the first primary zone proxy server, it also carries token information; when the first primary zone proxy server receives the zone synchronization request from the secondary zone server, it first verifies the IP address of the secondary zone server, and terminates the synchronization request if it does not match; if it matches, it continues to verify the token information, and terminates the synchronization request if it does not match, and only proceeds to subsequent steps if it matches.

5. The blockchain-based zone transmission method according to claim 4, characterized in that: The node information content of the first primary area proxy server includes: the node IP of the first primary area proxy server, time validity, and token information used for authentication.

6. The blockchain-based zone transmission method according to claim 3, characterized in that: When the master zone server receives a zone update, it actively initiates synchronization to any master zone proxy server in the blockchain network. Specifically, the master zone server sends an update notification message to any master zone proxy server in the blockchain network. The master zone proxy server initiates an incremental synchronization request to the master zone server based on the update notification message. The master zone server responds to the incremental synchronization request and synchronizes the zone data to the master zone proxy server, thereby maintaining the consistency of the data of the master zone server and the master zone proxy server.

7. The blockchain-based zone transmission method according to claim 3, characterized in that: Any of the primary zone proxy servers also actively initiates incremental synchronization requests to the primary zone server periodically.

8. The blockchain-based zone transmission method according to claim 3, characterized in that: The blockchain network composed of several main zone proxy servers is pre-configured with trusted authentication and a secure synchronization zone data link is established between the main zone server, the information of the main zone server is filled in the main zone proxy server, and the information of the main zone proxy server is filled in the main zone server.

Images