Domain name configuration system

Abstract

The invention discloses a domain name configuration system, and relates to the technical field of communication. And the first configuration gateway node receives the domain name configuration information and transmits the domain name configuration information to H configuration gateway nodes in all the configuration gateway nodes contained in other network clusters. Therefore, fast propagation of the domain name configuration information among the network clusters is realized, the network time delay of the domain name configuration information reaching each network cluster is reduced, and a guarantee is provided for each network cluster to receive consistent domain name configuration information. A first configuration gateway node sends domain name configuration information to K control nodes included in a first network cluster, a first control node sends the domain name configuration information to X configuration release nodes included in the first network cluster, and the first configuration release node transmits the domain name configuration information to an authoritative server. Therefore, the transmission efficiency of the domain name configuration information in the network cluster is improved, the network delay of the domain name configuration information reaching the authoritative server is reduced, and a guarantee is provided for the authoritative server to receive consistent domain name configuration information.

Description

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on August 23, 2023, with application number 202311068656.2 and application name “Distributed Domain Name Resolution System”, all contents of which are incorporated by reference in this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a domain name configuration system. Background Art

[0003] The domain name system (DNS) may include multiple authoritative servers. Each authoritative server receives the domain name configuration information sent by the management and control platform, and implements the resolution of the domain name (such as www.xxxx.com.cn) to the Internet protocol (Internet protocol, IP) address (such as xxxx) according to the domain name configuration information received by each server.

[0004] When there is a large network delay or communication failure between the authoritative server and the management and control platform, the domain name configuration information received by multiple authoritative servers may be inconsistent. When multiple authoritative servers with inconsistent domain name configuration information receive the same domain name resolution request sent by the client, these multiple authoritative servers resolve the domain name resolution request according to their own domain name configuration information, which may cause multiple authoritative servers to obtain different resolution results for the same domain name resolution request, affecting the user experience. Summary of the invention

[0005] The present application provides a domain name configuration system for solving the problem that multiple authoritative servers with inconsistent domain name configuration information obtain different resolution results for the same domain name resolution request, which affects the user experience.

[0006] In the first aspect, the present application provides a domain name configuration system. The domain name configuration system includes: M network clusters. Each network cluster includes: N configuration gateway nodes, I control nodes, J configuration publishing nodes, and L authoritative servers, wherein M, N, I, J, and L are all positive integers greater than or equal to 2. The first configuration gateway node included in the first network cluster receives the domain name configuration information input by the user, and sends the domain name configuration information to the H configuration gateway nodes included in the domain name configuration system. Among them, the first network cluster is any one of the M network clusters, the first configuration gateway node is any one of the N configuration gateway nodes included in the first network cluster, and H is a positive integer greater than or equal to 1 and less than or equal to N. The first configuration gateway node also sends the domain name configuration information to the K control nodes included in the first network cluster. Among them, the K control nodes are any K control nodes in the I control nodes included in the first network cluster. The first control node included in the first network cluster sends the domain name configuration information to the X configuration publishing nodes. Among them, the first control node is any one of the K control nodes, and the X configuration publishing nodes are any X configuration publishing nodes in the J configuration publishing nodes included in the first network cluster. The first configuration publishing node included in the first network cluster sends domain name configuration information to its corresponding authoritative server. The first configuration publishing node is any one of the X configuration publishing nodes. The first authoritative server receives the domain name configuration information and performs domain name configuration according to the correspondence between the domain name and the IP address. The domain name configuration information includes: the correspondence between the domain name and the IP address.

[0007] The first configuration gateway node receives the domain name configuration information input by the user, and transmits the domain name configuration information to at least one (such as H) configuration gateway node among all the configuration gateway nodes included in other network clusters. In this way, the rapid propagation of domain name configuration information between network clusters is achieved, the time for the domain name configuration information to be transmitted to each network cluster is saved, the network delay for the domain name configuration information to reach each network cluster is reduced, and a guarantee is provided for each network cluster to receive consistent domain name configuration information. The first configuration gateway node sends the domain name configuration information to multiple control nodes (such as K) included in the first network cluster, the first control node sends the domain name configuration information to multiple (such as X) configuration publishing nodes included in the first network cluster, and the first configuration publishing node transmits the domain name configuration information to the authoritative server. In this way, the efficiency of the domain name configuration information within a single network cluster is improved, the network delay for the domain name configuration information to reach the authoritative server is shortened, and a guarantee is provided for each authoritative server to receive consistent domain name configuration information.

[0008] In a possible implementation, before the first configuration gateway node sends the domain name configuration information to any one of the other configuration gateway nodes included in the domain name configuration system. In the case of a failure of the first configuration gateway node, the second configuration gateway node receives the domain name configuration information input by the user. Wherein, the second configuration gateway node is any one of the configuration gateway nodes in the domain name configuration system except the first configuration gateway node. The second configuration gateway node also sends the domain name configuration information to the K control nodes included in the network cluster where it is located. Wherein, the K control nodes are any K control nodes of the I control nodes included in the first network cluster. The first control node included in the first network cluster sends the domain name configuration information to the X configuration publishing nodes. Wherein, the first control node is any one of the K control nodes, and the X configuration publishing nodes are any X configuration publishing nodes of the J configuration publishing nodes included in the first network cluster. The first configuration publishing node included in the first network cluster sends the domain name configuration information to its corresponding authoritative server. Wherein, the first configuration publishing node is any one of the X configuration publishing nodes. The first authoritative server receives the domain name configuration information and performs domain name configuration according to the corresponding relationship between the domain name and the IP address. The domain name configuration information includes: the corresponding relationship between the domain name and the IP address. In this way, when the first configuration gateway node receiving the domain name configuration information fails, the user can still use the domain name configuration system to configure the domain name. The user does not perceive that the configuration gateway node receiving his input is damaged, which increases the reliability of the domain name configuration system and improves the user experience.

[0009] In another possible implementation, the second configuration gateway node is any one of all the configuration gateway nodes included in other network clusters in the domain name configuration system except the first network cluster. In this way, in the case that the first configuration gateway node that receives the domain name configuration information fails, the configuration gateway nodes in other network clusters of the domain name configuration system receive the domain name configuration information. This can avoid the delay required for the configuration gateway node to receive the domain name configuration information input by the user caused by the failure of the first configuration gateway node, which in turn causes the failure of other configuration gateway nodes included in the first network cluster.

[0010] In another possible implementation, after the first configuration gateway node sends the domain name configuration information to the other configuration gateway nodes included in the domain name configuration system. In the case of a failure of the first configuration gateway node, the second configuration gateway node also sends the domain name configuration information to the K control nodes included in the network cluster where it is located. Among them, the second configuration gateway node is any one configuration gateway node other than the first configuration gateway node in the domain name configuration system. The K control nodes are any K control nodes among the I control nodes included in the first network cluster. The first control node included in the first network cluster sends the domain name configuration information to the X configuration publishing nodes. Among them, the first control node is any one control node among the K control nodes. The X configuration publishing nodes are any X configuration publishing nodes among the J configuration publishing nodes included in the first network cluster. The first configuration publishing node included in the first network cluster sends the domain name configuration information to its corresponding authoritative server. Among them, the first configuration publishing node is any one configuration publishing node among the X configuration publishing nodes. The first authoritative server receives the domain name configuration information and performs domain name configuration according to the corresponding relationship between the domain name and the IP address. The domain name configuration information includes: the corresponding relationship between the domain name and the IP address. In this way, the control node that has not received the information sent by the first configuration gateway node can receive the information transmitted by the second configuration gateway node, thereby reducing the probability of inconsistent domain name configuration information received by each authoritative server in the first network cluster.

[0011] In another possible implementation, the domain name configuration information also includes: a second version number of the correspondence between the domain name and the IP address and a second applicable type of the correspondence between the domain name and the IP address. The first configuration release node stores historical domain name configuration information, and the historical domain name information includes: a first version number and a first applicable type. The first network cluster includes a first configuration release node that receives the domain name configuration information sent by the first control node, including: the first configuration release node compares whether the first applicable type and the second applicable type match. In the case where the first applicable type and the second applicable type match, the first configuration release node determines whether the second version number is updated compared to the first version number. In the case where the second version number is updated, the first configuration release node receives the domain name configuration information. In this way, it provides a guarantee for the configuration release node to receive the domain name configuration information with the latest version number. Furthermore, it provides a guarantee for the configuration release node to send the latest version of the domain name configuration information to the authoritative server, avoiding the problem of inconsistent domain name configuration information caused by the authoritative server not receiving the latest version of the domain name configuration information.

[0012] In another possible implementation, each network cluster further includes: W health detection nodes. W is a positive integer greater than or equal to 2. The correspondence between a domain name and an IP address is: one domain name corresponds to one target address set. The target address set includes: one or more IP addresses. The first configuration gateway node also sends domain name configuration information to the W health detection nodes included in the first network cluster. The first health detection node included in the first network cluster parses the domain name configuration information to obtain the communication status of one or more IP addresses included in the target address set, and sends the communication status of one or more IP addresses to the first control node. The first control node sends the domain name configuration information to the X configuration publishing nodes. The first configuration publishing node sends the domain name configuration information to the first authoritative server corresponding to it. When the first authoritative server receives a request for resolving a domain name sent by the client, the first authoritative server obtains one or more IP addresses whose communication status meets the conditions according to the communication status of one or more IP addresses corresponding to the domain name, and sends one or more IP addresses whose communication status meets the conditions to the client. In this way, the health detection node obtains the communication status corresponding to each IP address, and the communication status corresponding to each IP address is sent to the authoritative server via the control node and the configuration publishing node. When the authoritative server needs to resolve the domain name, it can select the IP address with the best communication status as the resolution result, thereby improving the communication quality and user experience.

[0013] In another possible implementation, the MxN configuration gateway nodes included in the domain name configuration system are located in the first network. The N configuration gateway nodes, I control nodes, J configuration release nodes and W health detection nodes included in each network cluster are all located in the second network, and the network environment of the first network and the second network is different. In this way, all the configuration gateway nodes included in the domain name configuration system are located in the same network (such as the first network), which can shorten the network delay of the domain name configuration information transmitted between the various network clusters included in the domain name configuration system, improve the efficiency of transmission, and reduce the probability of inconsistent domain name configuration information caused by large network delays between the various network clusters. The various nodes included in a single network cluster are located in the same network, which can shorten the network delay of the domain name configuration information transmitted within the network cluster, improve the efficiency of transmission, and reduce the probability of inconsistent domain name configuration information caused by large network delays within the network cluster.

[0014] In another possible implementation, the domain name configuration information further includes: an identifier of a network cluster, the identifier being used to indicate the network cluster in which the domain name configuration information is effective. Thus, when a domain name resolution request is received, the authoritative server with the closest transmission distance to the client that initiated the domain name resolution request is used to resolve the domain name resolution request according to the identifier of the network cluster, thereby improving the resolution efficiency.

[0015] In a second aspect, the present application provides a domain name configuration method. The method is executed by a domain name configuration system, and the domain name configuration system includes: M network clusters. Each network cluster includes: N configuration gateway nodes, I control nodes, J configuration publishing nodes, and L authoritative servers. Among them, M, N, I, J and L are all positive integers greater than or equal to 2. The method includes: the first configuration gateway node included in the first network cluster receives the domain name configuration information input by the user, and sends the domain name configuration information to the H configuration gateway nodes included in the domain name configuration system, and sends the domain name configuration information to the K control nodes included in the first network cluster. Among them, the first network cluster is any one of the M network clusters, the first configuration gateway node is any one of the N configuration gateway nodes included in the first network cluster, and H is a positive integer greater than or equal to 1 and less than or equal to N. The K control nodes are any K control nodes among the I control nodes included in the first network cluster. The first control node included in the first network cluster sends the domain name configuration information to the X configuration publishing nodes. The first control node is any one of the K control nodes, and the X configuration publishing nodes are any X configuration publishing nodes among the J configuration publishing nodes included in the first network cluster. The first configuration publishing node included in the first network cluster sends domain name configuration information to its corresponding authoritative server. The first configuration publishing node is any one of the X configuration publishing nodes. The first authoritative server receives the domain name configuration information and performs domain name configuration according to the correspondence between the domain name and the IP address. The domain name configuration information includes: the correspondence between the domain name and the IP address.

[0016] In a third aspect, the present application provides a domain name configuration device. The domain name configuration device is applied to a domain name configuration system, and the domain name configuration system includes: M network clusters. Each network cluster includes: N configuration gateway nodes, I control nodes, J configuration publishing nodes, and L authoritative servers. Among them, M, N, I, J and L are all positive integers greater than or equal to 2. The domain name configuration device includes: a transceiver module applied to the first configuration gateway node included in the first network cluster, used to: receive the domain name configuration information input by the user, and send the domain name configuration information to the H configuration gateway nodes included in the domain name configuration system; and, send the domain name configuration information to the K control nodes included in the first network cluster. Among them, the first network cluster is any one of the M network clusters, the first configuration gateway node is any one of the N configuration gateway nodes included in the first network cluster, H is a positive integer greater than or equal to 1 and less than or equal to N; the K control nodes are any K control nodes among the I control nodes included in the first network cluster. The transceiver module is also applied to the first control node included in the first network cluster, used to: send domain name configuration information to X configuration publishing nodes. The first control node is any one of the K control nodes, and the X configuration publishing nodes are any X configuration publishing nodes of the J configuration publishing nodes included in the first network cluster. The transceiver module is also applied to the first configuration publishing node included in the first network cluster, and is used to: send domain name configuration information to the authoritative server corresponding to the first configuration publishing node. The first configuration publishing node is any one of the X configuration publishing nodes. The first authoritative server receives the domain name configuration information, and performs domain name configuration according to the correspondence between the domain name and the IP address, and the domain name configuration information includes: the correspondence between the domain name and the IP address.

[0017] In a fourth aspect, the present application provides a processor, which is used to implement the functions implemented by the domain name configuration method in the second aspect or any possible design of the second aspect.

[0018] In a fifth aspect, the present application provides a computing device cluster. The computing device cluster includes at least one computing device, each computing device includes a processor and a memory. The processor of at least one computing device is used to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster performs the functions implemented by the domain name configuration method in the second aspect or any possible design of the second aspect.

[0019] In a sixth aspect, the present application provides a computer-readable storage medium, including: computer program instructions; when the computer program instructions are executed in a computing device cluster, the computing device cluster executes the functions implemented by the domain name configuration method in the second aspect or any possible design of the second aspect.

[0020] In a seventh aspect, the present application provides a computer program product. When the computer program product is run on a computing device cluster, the computing device cluster executes the functions implemented by the domain name configuration method in the second aspect or any possible design of the second aspect.

[0021] The beneficial effects of the second to seventh aspects above can refer to the description of the first aspect or any implementation of the first aspect, and will not be repeated here. Based on the implementations provided by the above aspects, this application can also be further combined to provide more implementations. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 A schematic diagram of the structure of the first domain name configuration system;

[0023] Figure 2 A schematic diagram of the structure of the second domain name configuration system;

[0024] Figure 3 A schematic diagram of the first domain name configuration system provided for this application;

[0025] Figure 4 A schematic diagram of configuring a gateway node to receive information provided by this application;

[0026] Figure 5 A connection diagram of the first configuration gateway node provided in this application;

[0027] Figure 6 A schematic diagram of the structure of a communication model provided for this application;

[0028] Figure 7 A connection diagram of the second configuration gateway node provided in this application;

[0029] Figure 8 A schematic diagram of the first process of determining and configuring a gateway node provided in this application;

[0030] Fig. 9 A schematic diagram of the second process of determining and configuring a gateway node provided in this application;

[0031] Fig.10 A schematic diagram of the transmission of the first type of information provided by this application for configuring a gateway node within a network cluster;

[0032] Fig.11 A schematic diagram of the transmission of the second type of information provided by this application for configuring a gateway node within a network cluster;

[0033] Fig.12 A schematic diagram of the transmission of the first type of information provided in this application between a configuration gateway node and a control node;

[0034] Fig.13 A schematic diagram of the transmission of the second type of information provided in this application between the configuration gateway node and the control node;

[0035] Fig.14 A schematic diagram of the transmission of the first type of information provided in this application between a control node and a configuration publishing node;

[0036] Fig.15 A schematic diagram of the transmission of the second type of information provided in this application between the control node and the configuration publishing node;

[0037] Fig.16A A schematic diagram of the structure of the first network cluster provided for this application;

[0038] Fig. 16B A schematic diagram of the structure of the second network cluster provided for this application;

[0039] Fig.17 A flowchart of a domain name configuration method provided in this application;

[0040] Fig.18 A schematic diagram of the structure of the second domain name configuration system provided for this application;

[0041] Fig.19 A schematic diagram of the structure of the third domain name configuration system provided for this application;

[0042] Fig. 20 A schematic diagram of the structure of a domain name configuration device provided by this application;

[0043] Fig.21 A schematic diagram of the structure of a computing device provided for this application;

[0044] Fig. 22 A schematic diagram of the structure of a computing device cluster provided for this application;

[0045] Fig.23 A schematic diagram of a possible connection method of a computing device cluster provided in the present application. DETAILED DESCRIPTION

[0046] Domain name resolution Domain name configuration system (domain name system, DNS) can include multiple authoritative servers. Each authoritative server receives the domain name configuration information sent by the control platform, and implements the resolution of the domain name (such as www.xxxx.com.cn) to the Internet protocol (Internet protocol, IP) address (such as xxxx) according to the domain name configuration information received by each. The control platform can be an application (application, app) that implements the domain name configuration function. The application can be, but is not limited to, installed on: mobile phones, tablet computers, handheld computers, personal computers (personal computers, PCs), servers, cellular phones, personal digital assistants (personal digital assistants, PDAs), wearable devices (such as smart watches), smart home devices (such as TVs), car computers, game consoles, and augmented reality (augmentedreality, AR)\virtual reality (virtual reality, VR) devices and other processing devices. This embodiment does not impose special restrictions on the specific device form of the processing device on which the control platform is installed. For example, the control platform can be installed on a tablet computer or on a mobile phone. In this application, domain name configuration information is also referred to as information.

[0047] The processing device can use a variety of methods to configure information to the authoritative server. The following are three methods of configuration information commonly used by processing devices.

[0048] Method ①

[0049] Figure 1 The structural diagram of the first domain name configuration system is as follows: Figure 1 As shown, the domain name configuration system includes network clusters 1 to n. Each network cluster includes: a master node, a backup node and an authoritative server for information to be configured.

[0050] Taking the process of configuring network cluster 1 included in the domain name configuration system as an example, the process of configuring the domain name configuration system to the authoritative server included in the domain name configuration system is described. The process is specifically: the master node of network cluster 1 receives the information transmitted by the management and control platform, and transmits the information to the backup node of network cluster 1 and the authoritative server of network cluster 1 respectively.

[0051] When the master node of network cluster 1 receives information 1 transmitted by the control platform, and does not transmit information 1 to the standby node of network cluster 1 and the authoritative server of network cluster 1, the master node of network cluster 1 fails. In this case, the control platform starts the next information transmission process, and transmits information 2 to the standby node of network cluster 1, and the standby node of network cluster 1 transmits information 2 to the authoritative server of network cluster 1. In the above process, the authoritative server of network cluster 1 does not receive information 1, and the authoritative servers included in other normally working network clusters in the domain name configuration system receive information 1, resulting in inconsistent information received by each authoritative server included in the domain name configuration system.

[0052] Method ②

[0053] The structure of the domain name configuration system in this method is the same as that of the domain name configuration system in method ①, except that the domain name configuration system includes the process of configuring network cluster information.

[0054] Still taking the process of configuring network cluster 1 included in the domain name configuration system as an example, the process of configuring the domain name configuration system to the authoritative server included in the domain name configuration system is described. The specific process is: the master node and the backup node of network cluster 1 receive the information transmitted by the management and control platform. When the master node and the backup node of network cluster 1 successfully receive the information, the master node of network cluster 1 transmits the information to the authoritative server of network cluster 1. When at least one of the master node and the backup node of network cluster 1 fails to successfully receive the information, the master node of network cluster 1 does not transmit the information to the authoritative server of network cluster 1.

[0055] In the above process, the authoritative server included in the network cluster where at least one of the primary node and the backup node fails cannot receive information, while the authoritative server in the network cluster where both the primary node and the backup node in the domain name configuration system are working normally can receive information, resulting in inconsistent information received by the authoritative servers included in the domain name configuration system.

[0056] Method 3

[0057] Figure 2 The structural diagram of the second domain name configuration system is as follows: Figure 2 As shown, the domain name configuration system includes network clusters 1 to n. Each network cluster includes: a message middleware and an authoritative server for information to be configured.

[0058] Still taking the process of configuring network cluster 1 included in the domain name configuration system as an example, the process of configuring the domain name configuration system to the authoritative server included in the domain name configuration system is described. The process is specifically: the message middleware of network cluster 1 receives the information transmitted by the management and control platform, and transmits the information to the authoritative server of network cluster 1.

[0059] In the above process, the authoritative server of the network cluster with a faulty message middleware cannot receive information, while the authoritative server included in the network cluster with normal message middleware can receive the information, resulting in inconsistent information received by the authoritative servers included in the domain name configuration system.

[0060] Methods ① to ③ described above may cause the authoritative servers included in the domain name configuration system to receive inconsistent information. When multiple authoritative servers with inconsistent information receive the same domain name resolution request sent by the client, these multiple authoritative servers resolve the domain name resolution request according to their own information. This may cause multiple authoritative servers to obtain different resolution results for the same domain name resolution request, affecting the user experience.

[0061] To this end, this application provides a domain name configuration system. Figure 3 This is a schematic diagram of the first domain name configuration system provided by this application. Figure 3 As shown, the domain name configuration system 300 includes: network cluster 1 to network cluster M, where M is a positive integer greater than or equal to 2. The network cluster 1 to network cluster M included in the domain name configuration system 300 may have different deployment modes, which are described below respectively.

[0062] In a first possible scenario, network clusters 1 to M included in the domain name configuration system 300 are deployed in the same geographical location.

[0063] Exemplarily, the domain name configuration system 300 includes network clusters 1 to M, all of which are deployed in geographic location 1, as shown in Table 1.

[0064] Table 1

[0065] Serial number Network cluster name Geographic location of deployment 1 Network cluster 1 to network cluster 3 Location 1

[0066] In a second possible scenario, network clusters 1 to M included in the domain name configuration system 300 are deployed in different geographical locations.

[0067] In this case, one network cluster 310 can be deployed in the same geographical location, and multiple network clusters 310 can also be deployed in the same geographical location. Taking M equal to 3 as an example, the domain name configuration system 300 includes the deployment of network clusters 1 to 3. As shown in Table 2, network clusters 1 and 2 are deployed in geographical location 1, and network cluster 3 is deployed in location 2.

[0068] Table 2

[0069] Serial number Network cluster name Geographic location of deployment 1 Network Cluster 1 and Network Cluster 2 Location 1 2 Network Cluster 3 Location 2

[0070] According to the needs of actual applications, the domain name configuration system 300 may include 4 or more network clusters, and deploy the 4 or more network clusters to 3 or more geographical locations, and deploy one or more network clusters in each geographical location, which is not limited in this application.

[0071] According to the needs of actual applications, a geographical location can be further divided into multiple regions, and one or more network clusters can be deployed in each region. For example, geographical location 1 is divided into regions 1 to n, network cluster 1 is deployed to region 1, and network cluster 2 and network cluster 3 are deployed to region 2. In some possible scenarios, a region can be further divided into multiple parts, and one or more network clusters can be deployed on each part. For example, region 2 is divided into part 1 and part 2, network cluster 2 is deployed to part 1, and network cluster 3 is deployed to part 2. According to the needs of actual applications, different deployment methods of network clusters can be selected, and this application does not limit this.

[0072] Please continue to see Figure 3 , each network cluster may include: N configuration gateway nodes, I control nodes, J configuration publishing nodes and L authoritative servers, where N, I, J and L are all positive integers greater than or equal to 2.

[0073] In one possible scenario, the configuration gateway node included in each network cluster in the domain name configuration system is located in the first network. In this way, the network delay of information transmission between the network clusters included in the domain name configuration system is shortened, the transmission efficiency is improved, and the probability of information inconsistency caused by large network delays between the network clusters is reduced.

[0074] The information may include: domain name information and geographic location information. Domain name information includes: the correspondence (value) between one or more domain names and the first target address set, the version number (version) of the correspondence, and the applicable type (key) of the correspondence. Geographic location information includes: the correspondence (value) between one or more geographic locations and the second target address set, the version number (version) of the correspondence, and the applicable type (key) of the correspondence. The applicable type (key) is used to indicate whether the information is domain name information (dns / cfg) or geographic location information (dimp / geomapdb-intranet), etc. The first target address set may include: one or more IP addresses. The second target address set may include: one or more IP address segments.

[0075] Taking the domain name information including the correspondence between multiple domain names and the first target address set as an example, information 1 is the domain name information, and information 1 includes: correspondence 1, version number 1 and domain name information. Correspondence 1 includes: the correspondence between domain name 1 and target address set 11 to the correspondence between domain name i and target address set 1i, where i is a positive integer greater than or equal to 2. Table 3 gives the correspondence between 2 domain names and the first target address set, as shown in Table 3, and the rows corresponding to sequence numbers 1 to 4 in Table 3 give the domain name information with version number 100, including: the correspondence between domain name 1 and ip1, ip2, and the correspondence between domain name 2 and ip3, ip4.

[0076] Taking the geographical location information including the correspondence between multiple geographical locations and the second target address set as an example, information 2 is the geographical location information, and information 2 includes: correspondence 2, version number 2 and geographical location information. Correspondence 2 includes: the correspondence between geographical location 1 and target address set 21 to the correspondence between geographical location j and target address set 2j, where j is a positive integer greater than or equal to 2. Table 3 gives the correspondence between 2 geographical locations and the second target address set, as shown in Table 3, and the rows corresponding to sequence numbers 5 and 6 of Table 3 give the geographical location information with version number 30, including: the correspondence between geographical location 1 and IP address segment 1, and the correspondence between geographical location 2 and IP address segment 1.

[0077] Table 3

[0078]

[0079] Exemplarily, the gateway node is configured to verify the information input by the user as shown in Table 3, and to determine that the content of the rows corresponding to sequence numbers 1, 3 to 6 conform to the DNS structure, and the verification passes. The gateway node is configured to encapsulate the information that passes the verification into a message format that can be transmitted in the p2p network, and transmit the encapsulated information to the control node. For the message format that can be transmitted in the p2p network, please refer to the description of the general technology, which will not be repeated here.

[0080] In some possible situations, the information input by the user may also include: a network cluster identifier (namespace), which is used to indicate: the network cluster in which the domain name configuration information is effective. If the domain name configuration system includes network clusters 1 to M, as shown in the last column of Table 4, the information input by the user includes a network cluster identifier (namespace), and the last column of the row corresponding to sequence number 1 to sequence number 3 in Table 4 indicates the correspondence between domain name 1 and ip1, and the correspondence between domain name 2 and ip3 and ip4 is effective in network cluster 1.

[0081] Table 4

[0082]

[0083] Figure 4 A schematic diagram of configuring a gateway node to receive information provided by this application, such as Figure 4 As shown, the management and control platform receives information input by the user, and calls the remote call interface of the configuration gateway node to send information to the first configuration gateway node included in the first network cluster, and the first configuration gateway receives the information input by the user. The first configuration gateway node sends information to H configuration gateway nodes among all configuration gateway nodes included in other network clusters. Among them, H is a positive integer greater than or equal to 1 and less than or equal to N. The first configuration gateway node is: one of the N gateway nodes included in the first network cluster. In this way, the rapid propagation of information between network clusters is achieved, the time for information transmission to each network cluster is saved, the network delay for information to reach each network cluster is reduced, and a guarantee is provided for each network cluster to receive consistent information.

[0084] Based on the above embodiments, the domain name configuration method provided by the present application is exemplarily described below in conjunction with the accompanying drawings. The domain name configuration method provided by the embodiment of the present application includes: the information transmission process between different network clusters and the information transmission process between nodes within the network cluster. The above two processes are described below respectively.

[0085] 1. The information transmission process between different network clusters.

[0086] Depending on the value of H, the information is propagated differently between network clusters, which are explained below.

[0087] Scenario 1: Information is transmitted one-to-one between network clusters (i.e., H is equal to 1).

[0088] The first configuration gateway node of the first network cluster receives information input by the user, determines the second configuration gateway node of the second network cluster from all configuration gateway nodes included in other network clusters except the first network cluster included in the domain name configuration system, and transmits information to the second configuration gateway node. The second configuration gateway node receives information, and determines the third configuration gateway node of the third network cluster from all configuration gateway nodes included in other network clusters except the first network cluster and the second network cluster included in the domain name configuration system, and repeats the above process until all network clusters included in the domain name configuration system receive information.

[0089] For example, Figure 5 The connection diagram of the first configuration gateway node provided in this application is as follows: Figure 5As shown, the domain name configuration system includes network clusters 1 to M, each of which includes N configuration gateway nodes. Network cluster i includes configuration gateway nodes i1 to iN, where i is a positive integer from 1 to M. Configuration gateway node 11 of network cluster 1 receives information input by the user, and configuration gateway node 11 determines configuration gateway node 21 from all configuration gateway nodes included in network clusters 2 to M, and transmits information to configuration gateway node 21. The above process is repeated until the information is transmitted to all network clusters included in the domain name configuration system.

[0090] The gateway node may be configured to determine whether to receive information in the manner described below.

[0091] In case a, the information is domain name information.

[0092] The information also includes: a second version number of the correspondence between the domain name and the IP address and a second applicable type of the correspondence between the domain name and the IP address. The first configuration release node stores historical domain name configuration information, and the historical domain name information includes: a first version number and a first applicable type. The first network cluster includes a first configuration release node that receives domain name configuration information sent by the first control node, including: the first configuration release node compares whether the first applicable type and the second applicable type match. In the case where the first applicable type and the second applicable type match, the first configuration release node determines whether the second version number is updated compared to the first version number. In the case where the second version number is updated, the first configuration release node receives the domain name configuration information. The first applicable type and the second applicable type both indicate: domain name information.

[0093] The above text takes the first applicable type and the second applicable type matching (such as both indicating domain name information) as an example to illustrate the situation where the first configuration gateway node receives information. In some possible examples, the first applicable type and the second applicable type do not match (such as the first applicable type indicates domain name information, and the second applicable type indicates geographic location information). In this case, the first configuration gateway node directly receives the information. In other possible situations, the first applicable type and the second applicable type match, and the second version number is not updated compared to the first version number. In this case, the first configuration gateway node does not receive information.

[0094] Depending on the different representation forms of the version number, the first configuration gateway node determines in different ways whether the second version number is updated compared to the first version number. Several possible examples are given below.

[0095] Example 1: The version number is represented by a numerical value, such as the first version number is 30 and the second version number is 32. In this case, the first configuration gateway node compares the numerical value representing the first version number (i.e., 30) and the numerical value representing the second version number (i.e., 32). If the numerical value representing the second version number is greater than the numerical value representing the first version number, the first configuration gateway node determines that the second version number is updated compared to the first version number, otherwise, there is no update.

[0096] Example 2: The version number is represented by symbols, such as the first version number is v1.0 and the second version number is. In this case, the first configuration gateway node compares the value of the last digit of the symbol representing the first version number (i.e. v1.0) and the symbol representing the second version number (i.e. v1.1). If the value of the last digit of the symbol representing the second version number is greater than the last digit of the symbol representing the first version number, the first configuration gateway node determines that the second version number is updated compared to the first version number, otherwise there is no update.

[0097] Two examples of determining whether a version number is updated are given above. In actual applications, other methods can be used to represent the version number, and methods for determining whether a version number is updated corresponding to the representation method of the version number can be defined. This application does not limit this.

[0098] In case b, the information is geographic location information.

[0099] The information also includes: a fourth version number of the correspondence between the geographic location and the IP address and a fourth applicability type of the correspondence between the domain name and the IP address. The first configuration release node stores historical domain name configuration information, and the historical domain name information includes: a third version number and a third applicability type. The first network cluster includes a first configuration release node that receives domain name configuration information sent by the first control node, including: the first configuration release node compares whether the third applicability type and the fourth applicability type match. In the case where the third applicability type matches the third applicability type, the first configuration release node determines whether the fourth version number is updated compared to the third version number. In the case where the fourth version number is updated, the first configuration release node receives the domain name configuration information. The third applicability type and the fourth applicability type both indicate: geographic location information. In this case, the first configuration gateway node can use the method described in case a to determine whether the version number is updated, which will not be repeated here.

[0100] Scenario 2: Information is transmitted between network clusters in a one-to-many manner (i.e., H is greater than 1).

[0101] For example, information is transmitted between each network cluster in a one-to-two manner (i.e., H is equal to 2). In this case, the following can be formed: Figure 6 The communication model shown, Figure 6 A schematic diagram of the structure of a communication model provided in this application. Figure 6 As shown, node 11 sends information to node 21 and node 22, node 21 sends information to node 31 and node 32, and node 22 sends information to node 33 and node 34.

[0102] Information is transferred between various network clusters Figure 6 The communication model transmission shown in FIG. 1 is taken as an example to illustrate the information transmission process between various network clusters.

[0103] The first configuration gateway node of the first network cluster receives information input by the user, determines the second configuration gateway node of the second network cluster and the third configuration gateway node of the third network cluster from all configuration gateway nodes included in other network clusters except the first network cluster included in the domain name configuration system, and transmits information to the second configuration gateway node and the third configuration gateway node. The second configuration gateway node and the third configuration gateway node receive information, and determine the fourth configuration gateway node of the fourth network cluster and the fifth configuration gateway node of the fifth network cluster from all configuration gateway nodes included in other network clusters except the first network cluster, the second network cluster and the third network cluster included in the domain name configuration system, and repeats the above process until all network clusters included in the domain name configuration system receive information.

[0104] For example, Figure 7 The connection diagram of the second configuration gateway node provided in this application is as follows: Figure 7 As shown, the domain name configuration system includes network clusters 1 to M, and each network cluster includes N configuration gateway nodes. Network cluster i includes configuration gateway nodes i1 to configuration gateway nodes iN, where i is equal to a positive integer from 1 to M. The configuration gateway node 11 of network cluster 1 receives information input by the user, and the configuration gateway node 11 determines the configuration gateway node 21 of network cluster 2 and the configuration gateway node 31 of network cluster 3 from all the configuration gateway nodes included in network clusters 2 to network cluster M, and transmits information to the configuration gateway node 21 and the configuration gateway node 31 respectively. The configuration gateway node 21 determines the configuration gateway node 41 and the configuration gateway node 42 of network cluster 4 from all the configuration gateway nodes included in network clusters 3 to network clusters M, and sends information to the configuration gateway node 41 and the configuration gateway node 42. Repeat the above process until all network clusters included in the domain name configuration information receive the information.

[0105] In this case, the process of configuring the gateway node to receive information is the same as the process of configuring the gateway node to receive information described in Scenario 1. For related descriptions, please refer to the above text and will not be repeated here.

[0106] Scenario 2 takes H equal to 2 as an example to illustrate the process of information transmission between network clusters. According to the needs of actual applications, information can also be transmitted between each network cluster in a one-to-three or more manner. Scenario 1 and Scenario 2 both take the example that the number of configuration gateway nodes contained in network cluster 1 to network cluster M is the same and is N, to illustrate the transmission method of domain name configuration information between each network cluster. According to the needs of actual applications, the number of configuration gateway nodes contained in network cluster 1 to network cluster M can also be different, and this application does not limit this.

[0107] The first configured gateway node may determine one or more configured gateway nodes from other configured gateway nodes in a variety of ways. Two examples of determining the configured gateway nodes are given below.

[0108] Example A: The first configuration gateway node determines one or more configuration gateway nodes according to the communication status with each of the other configuration gateway nodes. Figure 8 The first flow chart of determining and configuring a gateway node provided in this application is as follows: Figure 8 The process may include the following steps ① to ③.

[0109] In step ①, the first configuration gateway node determines the communication status with each of the other configuration gateway nodes. The first configuration gateway node can determine the communication status with the other configuration gateway nodes in different ways, such as network delay, network bandwidth, etc.

[0110] For example, the domain name configuration system includes configuration gateway nodes 1 to configuration gateway nodes n. Configuration gateway node 1 transmits the same data to configuration gateway nodes 2 to configuration gateway nodes n respectively, obtains the network delay of configuration gateway nodes 2 to configuration gateway nodes n receiving the data, and uses the network delay to determine the communication status of configuration gateway node 1 and each configuration gateway node in configuration gateway node 2 to configuration gateway node n.

[0111] For another example, the domain name configuration system includes configuration gateway node 1 to configuration gateway node n. Configuration gateway node 1 obtains the network bandwidth between configuration gateway node 2 to configuration gateway node n and each configuration gateway node, and uses the network bandwidth to determine the communication status between configuration gateway node 1 and each configuration gateway node in configuration gateway node 2 to configuration gateway node n.

[0112] In step ②, the first configuration gateway node sorts the communication states of the other configuration gateway nodes to obtain a communication state sequence.

[0113] For example, the first configured gateway node sorts the other configured gateway nodes in the order of increasing network delay to obtain the network delay sequence (ie, communication state sequence) of the other configured gateway nodes.

[0114] For another example, the first configured gateway node sorts the other configured gateway nodes in descending order of network bandwidth to obtain a network bandwidth sequence (ie, a communication state sequence) of the other configured gateway nodes.

[0115] In step ③, the first configured gateway node determines one or more configured gateway nodes according to the communication state sequence. For example, the first configured gateway node determines one or more configured gateway nodes that are ranked first in the communication state sequence (such as the network delay sequence and the network bandwidth sequence).

[0116] Example B: The first configuration gateway node determines one or more configuration gateway nodes according to the relationship between the communication status with each of the other configuration gateway nodes and the set threshold. Fig. 9 A schematic diagram of the second process of determining and configuring a gateway node provided in this application, such as Fig. 9 The process may include the following steps ① to ②.

[0117] Step ① in this example is the same as step ① in example A, and the difference is step ②. Step ② is specifically described as follows: the first configured gateway node compares the set threshold and the communication status of each configured gateway node respectively, and when the communication status of the configured gateway node is better than the set threshold, determines that the configured gateway node is one of the one or more configured gateway nodes.

[0118] Example C: The first configuration gateway node randomly determines one or more configuration gateway nodes from other configuration gateway nodes.

[0119] The above scenarios 1 and 2, combined with the accompanying drawings, describe the information transmission process in the domain name configuration system when the first configuration gateway node that receives the information input by the user operates normally. In some possible scenarios, the first configuration gateway node that receives the information input by the user fails or all the configuration gateway nodes included in the first network cluster where the first configuration gateway node that receives the information input by the user is located fail. The failure may be caused by power outages, the control platform cannot operate normally, the medium that transmits information cannot operate normally, etc. This application does not limit the cause of the failure.

[0120] Depending on the configuration gateway node that fails, the process of transmitting the information input by the user to the domain name configuration system is different, which is described below.

[0121] Scenario A: Before the first configuration gateway node sends domain name configuration information to any one of the other configuration gateway nodes included in the domain name configuration system, the first configuration gateway node fails.

[0122] In this case, the second configuration gateway node receives the domain name configuration information input by the user. The second configuration gateway node is any configuration gateway node in the domain name configuration system except the first configuration gateway node. In this way, in the case that the first configuration gateway node that receives the domain name configuration information fails, the user can still use the domain name configuration system to configure the domain name. The user does not perceive that the configuration gateway node that receives his input is damaged, which increases the reliability of the domain name configuration system and improves the user experience.

[0123] The second configuration gateway node may be any one of all the configuration gateway nodes included in other network clusters other than the first network cluster in the domain name configuration system. The management and control platform may determine the second configuration gateway node using any of the methods given in Examples A to C, and this application is not limited thereto. In this way, in the case where the first configuration gateway node that receives the domain name configuration information fails, the configuration gateway nodes in other network clusters of the domain name configuration system receive the domain name configuration information. It is possible to avoid causing the failure of the first configuration gateway node, and again causing the failure of other configuration gateway nodes included in the first network cluster, resulting in the delay required for the configuration gateway node to receive the domain name configuration information input by the user. Exemplarily, the domain name configuration system includes network clusters 1 to network clusters M. Network cluster i includes configuration gateway nodes i1 to configuration gateway nodes iN, where i is a positive integer from 1 to M. Configuration gateway node 11 receives information input by the user, and sends a fault before sending information to configuration gateway nodes other than configuration gateway node 11 included in the domain name configuration system. In this case, other configuration gateway nodes (such as configuration gateway node 21) included in the domain name configuration system except configuration gateway nodes 12 to configuration gateway nodes 1N can receive information input by the user.

[0124] The second configuration gateway node may be any one of the other configuration gateway nodes included in the first network cluster except the first configuration gateway node. The management and control platform may determine the second configuration gateway node using any of the methods given in Examples A to C, and this application is not limited thereto. Exemplarily, the domain name configuration system includes network clusters 1 to M. Network cluster i includes configuration gateway nodes i1 to configuration gateway nodes iN, where i is a positive integer from 1 to M. Configuration gateway node 11 receives information input by the user, and sends a fault before sending information to configuration gateway nodes other than configuration gateway node 11 included in the domain name configuration system. In this case, configuration gateway nodes 12 to configuration gateway nodes 1N (such as configuration gateway node 12) included in the domain name configuration system can all receive information input by the user.

[0125] Scenario B: After the first configuration gateway node sends domain name configuration information to other configuration gateway nodes included in the domain name configuration system, the first configuration gateway node fails.

[0126] In this case, the management and control platform can use the method described in Scenario A to transmit information to the domain name configuration system. Please refer to the above for the relevant description, which will not be repeated here.

[0127] When any of the configuration gateway nodes included in the first network cluster resumes normal operation, the resumed configuration gateway node receives information sent by other configuration gateway nodes. For example, configuration gateway node 11 of network cluster 1 resumes operation, and configuration gateway node 11 receives information sent by configuration gateway node 21.

[0128] The above text, combined with the accompanying drawings, describes the process of using configuration gateway nodes to realize information transmission between network clusters included in the domain name configuration system. The following text, combined with the accompanying drawings, describes the process of information transmission within the network cluster. The configuration gateway node, control node, configuration publishing node, authoritative server and health detection node within the network cluster receive information in the same way as the configuration gateway node described in the first scenario above. For related descriptions, please refer to the above text and will not be repeated here. The following only describes the process of how various nodes send information to the next node.

[0129] In one possible scenario, the configuration gateway node, control node, and configuration publishing node included in the network cluster are located in the second network. The first network and the second network are different. In this way, the network delay of information transmission within the network cluster is shortened, the transmission efficiency is improved, and the probability of inconsistent domain name configuration information due to large network delay within the network cluster is reduced.

[0130] 2. The information transmission process between nodes within the network cluster.

[0131] The information transmission process within the network cluster may include: information transmission between configuration gateway nodes within the network cluster, information transmission between configuration gateway nodes and control nodes, information transmission between control nodes and configuration publishing nodes, and information transmission between configuration publishing nodes and authoritative servers.

[0132] The following takes network cluster 1 as an example to illustrate the above transmission processes.

[0133] The first type is the process of transmitting information between the configuration gateway node 11 and the configuration gateway node 1N included in the network cluster 1.

[0134] The first configuration gateway node sends domain name configuration information to G of the other configuration gateway nodes included in the first network cluster. Wherein, G is a positive integer less than or equal to N-1. Depending on the value of G, the information transmission process between the configuration gateway nodes included in the network cluster is also different, which is described below.

[0135] In a first possible scenario, the configuration gateway node 11 receives information input by the user, and sends information to one or more of the configuration gateway nodes 12 to 1N (ie, G is equal to 1).

[0136] Configuration gateway node 11 sends information to one of configuration gateway node 12 to configuration gateway node 1N, and the configuration gateway node receiving the information sends the information to other configuration gateway nodes until each of configuration gateway node 11 to configuration gateway node 1N receives the information. Fig.10 The first type of information provided in this application is a transmission diagram of a configuration gateway node in a network cluster, such as Fig.10 As shown, the configured gateway node 11 sends information to the configured gateway node 12 to the configured gateway node 1N. The configured gateway node 12 sends information to the configured gateway node 13 to the configured gateway node 1N, and the process is repeated until all the configured gateway nodes included in the network cluster 1 receive the information. The configured gateway node can adopt the method given in Examples A to C, and the target configured gateway node from the other configured gateway nodes included in the network cluster 1 is selected as the object of information transmission. The target configured gateway node can be the configured gateway node with the best communication status, or any randomly determined configured gateway node.

[0137] In a second possible scenario, the configuration gateway node 11 receives information input by the user, and sends information to a plurality of configuration gateway nodes 12 to 1N (ie, G is greater than or equal to 2).

[0138] Taking G equal to 2 as an example, the configuration gateway node 11 sends information to two of the configuration gateway nodes 12 to the configuration gateway node 1N. Fig.11 The second information provided by this application is a transmission diagram of a configuration gateway node in a network cluster, such as Fig.11As shown, the configuration gateway node 11 sends information to the configuration gateway nodes 12 and the configuration gateway nodes 13 in the configuration gateway nodes 12 to the configuration gateway nodes 1N. The configuration gateway node 12 sends information to the configuration gateway nodes 13 and the configuration gateway nodes 14 in the configuration gateway nodes 13 to the configuration gateway nodes 1N, and repeats the process until all the configuration gateway nodes included in the network cluster 1 receive the information. The configuration gateway node can adopt the method given in Examples A to C to determine two target configuration gateway nodes from other configuration gateway nodes as the objects of information transmission. The two target configuration gateway nodes can be determined randomly, or according to the communication status, or can be determined jointly according to the communication status and randomly (such as the configuration gateway node 13 is determined according to the communication status, and the configuration gateway node 14 is randomly determined), which is not limited in this application.

[0139] When G is greater than or equal to 3, the configuration gateway node 11 can adopt the method of G equal to 2 to send information to three or more target configuration gateway nodes from the configuration gateway node 12 to the configuration gateway node 1N, which will not be repeated here.

[0140] The second type is the information transmission process between the configuration gateway node and the control node included in the network cluster 1.

[0141] The first configuration gateway node sends domain name configuration information to K control nodes in the first network cluster, where K is a positive integer less than or equal to 1. Depending on the value of K, the information transmission process between the configuration gateway node and the control node is also different, which are described below.

[0142] In a first possible scenario, the first configuration gateway node sends information to one of I control nodes included in the first network cluster (ie, K is equal to 1).

[0143] Fig.12 The first information provided in this application is a schematic diagram of transmission between the configuration gateway node and the control node, such as Fig.12 As shown, the configuration gateway node 11 sends information to the control node 11 in the control node 11 to the control node 1I. The control nodes 12 to the control node 1I that have not received the information receive the information sent by the configuration gateway node 12 to the configuration gateway node 1N, such as the control node 12 receiving the information sent by the configuration gateway node 12. The configuration gateway node can use the method given in Examples A to C to determine the target control node from the control node 11 to the control node 1I as the object of information transmission.

[0144] In a second possible scenario, the first configuration gateway node sends information to two of the I control nodes included in the first network cluster (ie, K is equal to 2).

[0145] Fig.13The second information provided in this application is a schematic diagram of transmission between the configuration gateway node and the control node, such as Fig.13 As shown, the configuration gateway node 11 sends information to the control nodes 11 and 12 in the control nodes 11 to 1I. The control nodes 13 to 1I that have not received the information receive the information sent by the configuration gateway node 12 to the configuration gateway node 1N, such as the control nodes 13 and 14 receiving the information sent by the configuration gateway node 12. The configuration gateway node can use the method given in Examples A to C to determine two target control nodes from the control nodes 11 to 1I as the objects of information transmission.

[0146] When K is greater than or equal to 3, the gateway node may be configured to send information to three or more target control nodes from the control node 11 to the control node 1I by using the method of K being equal to 2, which will not be described in detail here.

[0147] The third type is the information transmission process between the control node and the configuration release node included in the network cluster 1.

[0148] The first control node sends domain name configuration information to X configuration publishing nodes included in the first network cluster. The first control node is used to indicate one of the K control nodes. X is a positive integer less than or equal to J. Depending on the value of X, the information transmission process between the control node and the configuration publishing node is also different, which is described below.

[0149] In a first possible scenario, the first control node sends information to one of L configuration publishing nodes included in the first network cluster (ie, X is equal to 1).

[0150] Fig.14 The first information provided in this application is transmitted between the control node and the configuration release node, such as Fig.14 As shown, the control node 11 sends information to the configuration publishing node 11 among the configuration publishing nodes 11 to the configuration publishing node 1L. The configuration publishing nodes 12 to the configuration publishing node 1L that have not received the information receive the information sent by the control node 12 to the control node 1I, just as the configuration publishing node 12 receives the information sent by the control node 12. The control node can use the methods given in Examples A to C to determine the target configuration publishing node from the configuration publishing nodes 11 to the configuration publishing nodes 1L as the object of information transmission.

[0151] In a second possible scenario, the first control node sends information to two of the L configuration publishing nodes included in the first network cluster (ie, X is equal to 2).

[0152] Fig.15The second information provided in this application is transmitted between the control node and the configuration release node, such as Fig.15 As shown, the control node 11 sends information to the configuration publishing node 11 and the configuration publishing node 12 in the configuration publishing node 11 to the configuration publishing node 1L. The configuration publishing node 13 to the configuration publishing node 1L that have not received the information receive the information sent by the control node 12 to the control node 1I, such as the configuration publishing node 13 and the configuration publishing node 14 receiving the information sent by the control node 12. The control node can use the method given in Examples A to C to determine two target control nodes from the configuration publishing node 11 to the configuration publishing node 1L as the objects of information transmission.

[0153] When X is greater than or equal to 3, the control node may adopt the method of X being equal to 2 to send information to three or more target configuration publishing nodes from the configuration publishing node 11 to the configuration publishing node 1L, which will not be repeated here.

[0154] The fourth type is the process of information transmission between the configuration publishing node and the authoritative server included in the network cluster 1.

[0155] The first configuration publishing node receives the domain name configuration information, parses the domain name configuration information to obtain the correspondence between the domain name and the IP address, and sends the correspondence between the domain name and the IP address to the first authoritative server included in the first network cluster. The first configuration publishing node is one of the X configuration publishing nodes. The first authoritative server receives the correspondence between the domain name and the IP address, and performs domain name configuration according to the correspondence between the domain name and the IP address.

[0156] Exemplarily, the network cluster 1 includes a configuration publishing node 11 and an authoritative server 1. The configuration publishing node 11 and the authoritative server 1 are deployed on the same processing device. When the configuration publishing node 11 receives the information shown in Table 5, the configuration publishing node 11 transmits the information to the authoritative server 1. When the authoritative server 1 receives a resolution request for the domain name 1, the authoritative server 1 obtains ip1 or ip2 as a resolution result according to the correspondence between the domain name 1 and ip1 and ip2 shown in the information 1 in Table 5, and transmits the resolution result to the client.

[0157] Table 5

[0158]

[0159] In a possible example, authoritative server 1 is deployed at geographic location 1, and authoritative server 2 is deployed at geographic location 2. A client at geographic location 1 initiates a domain name resolution request for domain name 1. In this case, authoritative server 1 receives the domain name resolution request, and authoritative server 1 determines IP address segment 1 corresponding to geographic location 1 based on the received geographic location information. Authoritative server 1 determines that an IP address located in IP address segment 1 is the resolution result of the domain name from the multiple IP addresses based on the correspondence between the domain name and the multiple IP addresses, and sends the IP address to the client.

[0160] The above text gives a situation where the configuration release node and the authoritative server included in the network cluster are deployed on the same processing device in a one-to-one manner. In some possible situations, the configuration release node and the authoritative server can also be deployed on the same processing device in a one-to-many manner. For example, network cluster 1 includes configuration release node 1, authoritative server 1 to authoritative server n. Configuration release node 1, authoritative server 1 to authoritative server n are deployed on the same electronic device. When configuration release node 1 receives information 1 shown in Table 5, configuration release node 1 transmits the information 1 to authoritative server 1 to authoritative server n.

[0161] In some possible scenarios, the network cluster may also include: K health detection nodes, where K is a positive integer greater than or equal to 2. The correspondence between domain names and IP addresses is: one domain name corresponds to a first target address set, and the first target address set includes: one or more IP addresses. The first configuration gateway node sends domain name configuration information to the first health detection node, and the first health detection node is one of the K health detection nodes. The first health detection node receives the domain name configuration information, and parses the domain name configuration information to obtain the communication status of one or more IP addresses included in the first target address set, and sends the communication status of one or more IP addresses to the first control node. In this way, the control node can transmit the communication status corresponding to each IP address to the authoritative server via the configuration publishing node. When the authoritative server needs to resolve the domain name, the IP address with the best communication status can be selected as the resolution result to improve the communication quality and improve the user experience. In this case, the health detection node is located in the second network.

[0162] Fig.16A The structural diagram of the first network cluster provided for this application is as follows: Fig.16AAs shown, the network cluster also includes: health detection nodes 11 to health detection nodes 1K. The gateway node 11 is configured to send information to one of the health detection nodes 11 to health detection nodes 1K (such as health detection node 11). Each health detection node that receives the information parses the information, obtains the communication status of each IP address included in the first target address set corresponding to the domain name in the information, and sends the information to one of the control nodes 11 to control nodes 1I (such as control node 11).

[0163] In some possible cases, Fig. 16B The structural diagram of the second network cluster provided for this application is as follows: Fig. 16B As shown, the gateway node 11 is configured to send information to multiple of the health detection nodes 11 to 1K (such as the health detection node 11 to the health detection node 1i). This process is consistent with the process of sending information to a health detection node described above, and will not be repeated here.

[0164] The above text takes the example that each network cluster in the domain name configuration system includes the same number of configuration gateway nodes, control nodes, configuration publishing nodes, authoritative servers and health detection nodes to illustrate the process of information configuration of the domain name configuration system. In actual applications, the number of various nodes included in each network cluster can be the same or different. For example, network cluster 1 includes N configuration gateway nodes, network cluster 2 includes N+1 configuration gateway nodes, etc. The above text and the accompanying drawings illustrate the information transmission process in the domain name configuration system. Figures 3 to 16B Based on the provided domain name configuration system, the present application also provides a possible specific example of a domain name configuration method, such as Fig.17 As shown, Fig.17 This is a flowchart of a domain name configuration method provided by this application. For an introduction to the domain name configuration system, please refer to the aforementioned Figures 3 to 16B The domain name configuration method provided in this embodiment includes the following steps S1710 to S1750.

[0165] S1710: A first configuration gateway node included in a first network cluster receives domain name configuration information input by a user, and sends the domain name configuration information to H configuration gateway nodes included in a domain name configuration system.

[0166] The first network cluster is any one of the M network clusters, the first configuration gateway node is any one of the N configuration gateway nodes included in the first network cluster, and H is a positive integer greater than or equal to 1 and less than or equal to N.

[0167] S1720: The first configuration gateway node further sends domain name configuration information to the K control nodes included in the first network cluster.

[0168] The K control nodes are any K control nodes among the I control nodes included in the first network cluster.

[0169] S1730: The first control node included in the first network cluster sends domain name configuration information to X configuration publishing nodes.

[0170] The first control node is any one of the K control nodes, and the X configuration publishing nodes are any X configuration publishing nodes among the J configuration publishing nodes included in the first network cluster.

[0171] S1740: The first configuration publishing node included in the first network cluster sends domain name configuration information to its corresponding authoritative server.

[0172] The first configuration publishing node is any one of the X configuration publishing nodes.

[0173] S1750, the first authoritative server receives the domain name configuration information, and performs domain name configuration according to the correspondence between the domain name and the IP address.

[0174] The domain name configuration information includes: the correspondence between the domain name and the IP address.

[0175] The rapid propagation of domain name configuration information between network clusters is achieved, the transmission time of domain name configuration information between network clusters is saved, the network delay of domain name configuration information reaching each network cluster is reduced, and a guarantee is provided for each network cluster to receive consistent domain name configuration information. The first configuration gateway node sends domain name configuration information to multiple control nodes (such as K) included in the first network cluster, the first control node sends domain name configuration information to multiple (such as X) configuration publishing nodes included in the first network cluster, and the first configuration publishing node transmits the domain name configuration information to the authoritative server. In this way, the efficiency of domain name configuration information within a single network cluster is improved, the network delay of domain name configuration information reaching the authoritative server is shortened, and a guarantee is provided for each authoritative server to receive consistent domain name configuration information. For more relevant content about the domain name configuration method, please refer to the above description of the domain name configuration system, which will not be repeated here.

[0176] It is worth noting that the domain name configuration system in the above embodiment can also be used to implement the possible sub-steps of each step included in the domain name configuration method in the embodiment. The contents of these sub-steps can refer to the implementation method of the aforementioned domain name configuration system and will not be repeated here.

[0177] Based on the above description of the domain name configuration system and domain name configuration method provided by the present application, the following takes the example that the domain name configuration system includes two network clusters, each network cluster includes two configuration gateway nodes, two control nodes, two configuration publishing nodes and two authoritative servers, and the various nodes included in the domain name configuration system use a one-to-two manner to transmit information 1 and information 2 to illustrate the complete process of the domain name configuration system configuring information to the authoritative server.

[0178] Fig.18 The structural diagram of the second domain name configuration system provided by this application is as follows: Fig.18 As shown, the domain name configuration system includes: network cluster 1 and network cluster 2. Network cluster 1 includes: configuration gateway node 1 and configuration gateway node 2, control node 1 and control node 2, configuration publishing node 1 and configuration publishing node 2, authoritative server 1 and authoritative server 2. Network cluster 2 includes: configuration gateway node 3 and configuration gateway node 4, control node 3 and control node 4, configuration publishing node 3 and configuration publishing node 4, authoritative server 3 and authoritative server 4. The contents of information 1 and information 2 are shown in Table 6.

[0179] Table 6

[0180]

[0181] Combine the following Fig.18 Taking the domain name configuration system configuration information 1 shown as an example, the process of domain name configuration system configuration information is described, and the process includes the following steps ① and ②.

[0182] In step ①, information 1 with version number 100 is transmitted between network clusters included in the domain name configuration system. The process includes the following ① to ③.

[0183] ①, configuration gateway node 1 transmits information 1 with version number 100 to configuration gateway node 2 and configuration gateway node 3, and configuration gateway node 2 and configuration gateway node 3 receive information 1 with version number 100.

[0184] ②, configuration gateway node 2 transmits information 1 with version number 100 to configuration gateway node 3 and configuration gateway node 4.

[0185] For configuring gateway node 3: configuring gateway node 3 compares the applicable type (key) and version number (version) contained in information 1. When the applicable type is the same and the version number has not been updated, it confirms that the information it has received (such as information 1 with version number 100 sent by configuring gateway node 1 to configuring gateway node 3) and information 1 with version number 100 transmitted by configuring gateway node 2 are the same information. In this case, configuring gateway node 3 no longer receives information 1 with version number 100 transmitted by configuring gateway node 2.

[0186] For configuring gateway node 4: configuring gateway node 4 to compare the applicable type (key) and version number (version) of the received information and information 1, and if at least one of the applicable types is different or the version number is not updated, confirming that it has not received information 1 with version number 100, in this case, configuring gateway node 4 to receive information 1 with version number 100, and using information 1 with version number 100 to overwrite information 1 with other version numbers that the configured gateway node 4 has received.

[0187] ③, configuration gateway node 3 transmits information 1 with version number 100 to configuration gateway node 4.

[0188] For configuring gateway node 4: configuring gateway node 4 compares the applicable type (key) and version number (version) of the information it has received (such as information 1 with version number 100 sent by configuring gateway node 2 to configuring gateway node 4 in ②) and information 1 with version number 100 sent by configuring gateway node 3. If the applicable type is the same and the version number has not been updated, it confirms that the information it has received and information 1 with version number 100 sent by configuring gateway node 3 are the same information. In this case, configuring gateway node 4 no longer receives information 1 with version number 100 transmitted by configuring gateway node 3.

[0189] In the event that configuration gateway node 1 fails, the management and control platform confirms a configuration gateway node (such as configuration gateway node 2) from configuration gateway node 2 to configuration gateway node 4, and sends information 1 with version number 100 to the configuration gateway node. The management and control platform can use any method described in examples A to C to confirm a configuration gateway node from configuration gateway node 2 to configuration gateway node 4.

[0190] When both configuration gateway node 1 and configuration gateway node 2 fail, the management and control platform determines a configuration gateway node (such as configuration gateway node 3) from configuration gateway node 3 and configuration gateway node 4, and sends information 1 with version number 100 to the configuration gateway node. The management and control platform can use any method described in examples A to C to confirm a configuration gateway node from configuration gateway node 3 and configuration gateway node 4.

[0191] In step ②, information 1 with version number 100 is transmitted within the network cluster. This process includes the following ① to ③.

[0192] ①, information 1 with version number 100 is transmitted between the configuration gateway node and the control node.

[0193] The gateway node 1 is configured to transmit the information 1 with the version number 100 to the control node 1 and the control node 2, and the control node 1 and the control node 2 receive the information 1 with the version number 100.

[0194] The configuration gateway node 2 transmits information 1 with version number 100 to the control node 1 and the control node 2. The control node 1 compares the applicable type (key) and version number (version) of the information it has received (such as the configuration gateway node 1 transmitting information 1 with version number 100 to the control node 1) and the configuration gateway node 2 transmitting information 1 with version number 100 to the control node 1, and confirms that it has received information 1 with version number 100 when the applicable type is the same and the version number is not updated. In this case, the control node 1 no longer receives the configuration gateway node 2 to send information 1 with version number 100. The process of the control node 2 receiving the information 1 with version number 100 is the same as that of the control node 1, which will not be repeated here.

[0195] In the event that the configuration gateway node 1 fails, the configuration gateway node 2 sends information 1 with version number 100 to the control node 1 and the control node 2. This process is the same as the process described above and will not be repeated here. In the event that both the configuration gateway node 1 and the configuration gateway node 2 fail, the control node 1 and the control node 2 wait until at least one of the configuration gateway node 1 and the configuration gateway node 2 resumes working. In the event that at least one of the configuration gateway node 1 and the configuration gateway node 2 resumes working, the resumed configuration gateway node receives information 1 with version number 100 sent and received by at least one configuration gateway in the network cluster 2, and transmits information 1 with version number 100 to the control node 1 and the control node 2.

[0196] In the event that at least one of the control node 1 and the control node 2 fails, the failed control node waits until it is restored to work. After the failed control node is restored to work, the information 1 with the version number 100 sent by at least one of the configuration gateway node 1 and the configuration gateway node 2 is received.

[0197] ②, Information 1 with version number 100 is transmitted between the control node and the configuration release node.

[0198] Control node 1 transmits information 1 with version number 100 to configuration publishing node 1 and configuration publishing node 2, and configuration publishing node 1 and configuration publishing node 2 receive information 1 with version number 100.

[0199] Control node 2 transmits information 1 with version number 100 to configuration publishing node 1 and configuration publishing node 2. Configuration publishing node 1 compares the applicable type (key) and version number (version) of the information it has received (such as information 1 transmitted by control node 1 to configuration publishing node 1) and information 1 with version number 100 transmitted by control node 2 to configuration publishing node 1, and confirms that it has received information 1 with version number 100 when the applicable type is the same and the version number has not been updated. In this case, control node 1 no longer receives information 1 with version number 100 sent by control node 2. The process of configuration publishing node 2 receiving information 1 with version number 100 is the same as the process of configuration publishing node 1 receiving information 1 with version number 100, which will not be repeated here.

[0200] In the event of a failure in one of the control nodes 1 or 2, the normally functioning control node sends information 1 with a version number of 100 to the configuration publishing node 1 and the configuration publishing node 2. This process is the same as described above and will not be repeated here. In the event of a failure in both the control node 1 and the control node 2, the configuration publishing node 1 and the configuration publishing node 2 wait until at least one of the control node 1 and the control node 2 resumes operation. At least one control node that resumes operation sends information 1 with a version number of 100 to the configuration publishing node 1 and the configuration publishing node 2. This process is the same as described above and will not be repeated here.

[0201] ③, information 1 with version number 100 is transmitted between the configuration publishing node and the authoritative server.

[0202] Configuration publishing node 1 transmits information 1 with version number 100 to authoritative server 1, and configuration publishing node 2 transmits information 1 with version number 100 to authoritative server 2.

[0203] In the case where configuration publishing node 1 fails, authoritative server 1 cannot receive information 1 with version number 100 during the time when configuration publishing node 1 fails. In this case, authoritative server 1 waits until configuration publishing node 1 resumes normal operation, and after configuration publishing node 1 resumes normal operation, receives information 1 with version number 100 transmitted by the control node, and configuration publishing node 1 transmits information 1 with version number 100 to authoritative server 1. The process of configuration publishing node 2 transmitting information 1 with version number 100 to authoritative server 2 is the same as the process of configuration publishing node 1 transmitting information 1 with version number 100 to authoritative server 1, and will not be repeated here.

[0204] The above describes the process of the domain name configuration system completing the configuration of information 1, assuming that the domain name configuration system includes two network clusters, each of which includes: two configuration gateway nodes, two control nodes, two configuration publishing nodes, and two authoritative servers. In the case where the domain name configuration system includes more than two network clusters, each of which includes more than two configuration gateway nodes, control nodes, configuration publishing nodes, and authoritative servers, the configuration of information can still be implemented in the manner described above.

[0205] In actual applications, when the domain name configuration system implements information configuration, the various nodes included in the network cluster can transmit information in the one-to-one manner described above, or in a one-to-many manner (such as Fig.18 Information is transmitted in a one-to-two (one-to-two) manner as described in the present application. The present application does not limit the use of one-to-one or one-to-many information transmission.

[0206] The above text uses information 1 with a configuration version number of 100 as an example to illustrate the process of configuring information of the domain name configuration system. In some possible examples, the domain name configuration system can also use the method of configuring information 1 described above to implement the configuration of geographic location information (such as information 2). For related descriptions, please refer to the above text and will not be repeated here. Taking information 2 including the correspondence between geographic location 1 and IP address segment 1, and the correspondence between geographic location 2 and IP address segment 2 as an example, according to the needs of actual applications, information 2 can also include other corresponding relationships, such as the correspondence between geographic location 2 and other IP address segments 3, and one geographic location can also correspond to multiple IP address segments, which is not limited in this application.

[0207] Fig.18 The network cluster 1 and network cluster 2 included in the domain name configuration system shown can be deployed in different geographical locations, such as network cluster 1 deployed in location 1 and network cluster 2 deployed in location 2. The various nodes included in network cluster 1 are located in network 21, and the various nodes included in network cluster 2 are located in network 22. In the case where a client located in location 1 initiates a domain name resolution request, the authoritative server in network cluster 1 receives the domain name resolution request and sends the resolution result to the client. In this way, network cluster 1 and the client are both located in location 1, which reduces the network delay in transmitting domain name requests and domain name resolution results compared to network cluster 2 located in location 2, thereby improving the efficiency of domain name resolution. Location 1 and location 2 may refer to cities, provinces, districts, or geographical locations with the same or different areas at different longitudes and latitudes obtained by other division methods.

[0208] In some possible situations, the domain name configuration system may also include: a health detection node. Fig.19 Take the domain name configuration system shown as an example, Fig.19The structural diagram of the third domain name configuration system provided for this application is as follows: Fig.19 The domain name configuration system shown is the same as Fig.18 The domain name configuration system shown is different: Fig.19 The domain name configuration system shown includes: a health detection node 1 and a health detection node 2. The health detection node 1 is connected to the configuration gateway node 1 and the control node 1 respectively, and the health detection node 2 is connected to the configuration gateway node 2 and the control node 2 respectively.

[0209] Still Fig.19 The domain name configuration system configuration information 1 shown in the figure is used as an example to illustrate the process of configuring the domain name configuration system configuration information including the health detection node. The process of configuring the domain name configuration system including the health detection node, the gateway node, the control node, the configuration publishing node and the authoritative server to configure the domain name configuration is similar to Fig.18 The configuration gateway node, control node, configuration publishing node and authoritative server of the domain name configuration system shown are the same, and will not be repeated here. The process of health detection node configuration information is described in detail below.

[0210] The health detection node 1 receives the information 1 with version number 100 transmitted by the configuration gateway node 1, and parses the information 1 with version number 100 to obtain the communication status of each IP address corresponding to the domain name 1 contained in the information 1 with version number 100. The health detection node 1 transmits the communication status of each IP address to the control node 1. The control node 1 transmits the communication status of each IP address to the authoritative server 1 and the authoritative server 2 in the manner described above. When the authoritative server 1 receives the resolution request for the domain name 1 sent by the client, the authoritative server 1 determines the IP address with the best communication status among the multiple IP addresses as the resolution result of the domain name 1. The transmission process of the information 1 with version number 100 at the health detection node 2 is the same as the transmission process of the information 1 with version number 100 at the health detection node 1, which will not be repeated here.

[0211] In the event that health detection node 1 fails, Fig.19 The domain name configuration system shown uses Fig.18 The method for configuring the information 1 with version number 100 of the domain name configuration system shown completes the configuration of the information 1 with version number 100. When the authoritative server 1 receives the resolution request for the domain name 1 sent by the client, the authoritative server 1 determines any one of the communication states of the multiple IP addresses as the resolution result of the domain name 1.

[0212] Combination of the above Figures 3 to 19The domain name configuration system provided by the present application is described. The domain name configuration system provided by the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a node or a node implements a certain function or functions in the form of hardware or computer software driving hardware depends on the specific application scenario and design constraints of the domain name configuration system. Fig. 20 Describe a domain name configuration device provided by this application, Fig. 20 A schematic diagram of the structure of a domain name configuration device provided in the present application, which is applied to a domain name configuration system. The domain name configuration system includes: M network clusters, each network cluster includes: N configuration gateway nodes, I control node, J configuration publishing nodes, L authoritative servers, where M, N, I, J and L are all positive integers greater than or equal to 2.

[0213] like Fig. 20 As shown, the domain name configuration device 2000 includes: a transceiver module 2010 applied to the first configuration gateway node included in the first network cluster, used to: receive the domain name configuration information input by the user, and send the domain name configuration information to H configuration gateway nodes in the domain name configuration system; and send the domain name configuration information to K control nodes included in the first network cluster. Wherein, the first network cluster is any one of the M network clusters, the first configuration gateway node is any one of the N configuration gateway nodes included in the first network cluster, H is a positive integer greater than or equal to 1 and less than or equal to N; the K control nodes are any K control nodes of the I control nodes included in the first network cluster. The transceiver module 2010 is also applied to the first control node included in the first network cluster, used to: send the domain name configuration information to X configuration publishing nodes. Wherein, the first control node is any one of the K control nodes, and the X configuration publishing nodes are any X configuration publishing nodes of the J configuration publishing nodes included in the first network cluster. The transceiver module 2010 is also applied to the first control node included in the first network cluster, used to: send the domain name configuration information to the authoritative server corresponding to the first configuration publishing node. The first configuration publishing node is any one of the X configuration publishing nodes. The first authoritative server receives the domain name configuration information and performs domain name configuration according to the correspondence between the domain name and the IP address. The domain name configuration information includes: the correspondence between the domain name and the IP address.

[0214] In a possible scenario, before the transceiver module 2010 sends the domain name configuration information to any one of the other configuration gateway nodes included in the domain name configuration system, in the case of a failure of the first configuration gateway node, the transceiver module 2010 is also applied to the second configuration gateway node, for: receiving the domain name configuration information input by the user, and sending the domain name configuration information to the K control nodes included in the network cluster where it is located. Wherein, the second configuration gateway node is any one of the configuration gateway nodes in the system except the first configuration gateway node. The K control nodes are any K control nodes of the I control nodes included in the first network cluster. The transceiver module 2010 is also applied to the first control node of the first network cluster, for: sending the domain name configuration information to the X configuration publishing nodes. Wherein, the first control node is any one of the K control nodes, and the X configuration publishing nodes are any X configuration publishing nodes of the J configuration publishing nodes included in the first network cluster. The transceiver module 2010 is also applied to the first configuration publishing node of the first network cluster, for: sending the domain name configuration information to its corresponding authoritative server. Wherein, the first configuration publishing node is any one of the X configuration publishing nodes. The first authoritative server receives the domain name configuration information, and performs domain name configuration according to the correspondence between the domain name and the IP address. The domain name configuration information includes: the correspondence between the domain name and the IP address.

[0215] In a possible scenario, the second configuration gateway node is any one of all configuration gateway nodes in other network clusters except the first network cluster in the system.

[0216] In a possible scenario, after the transceiver module 2010 applied to the first configuration gateway node sends the domain name configuration information to all other configuration gateway nodes included in the domain name configuration system, in the case of a failure of the first configuration gateway node, the transceiver module 2010 is also applied to the second configuration gateway node, for: sending the domain name configuration information to the K control nodes included in the network cluster where it is located. Among them, the second configuration gateway node is any one of the configuration gateway nodes except the first configuration gateway node in the system. The K control nodes are any K control nodes of the I control nodes included in the first network cluster. The transceiver module 2010 is also applied to the first control node, for: sending the domain name configuration information to the X configuration publishing nodes. Among them, the first control node is any one of the K control nodes, and the X configuration publishing nodes are any X configuration publishing nodes of the J configuration publishing nodes included in the first network cluster. The transceiver module 2010 is also applied to the first configuration publishing node, for: sending the domain name configuration information to the corresponding authoritative server. Among them, the first configuration publishing node is any one of the X configuration publishing nodes. The first authoritative server receives the domain name configuration information, and performs domain name configuration according to the correspondence between the domain name and the IP address. The domain name configuration information includes: the correspondence between the domain name and the IP address.

[0217] In a possible scenario, the domain name configuration information also includes: a second version number of the correspondence between the domain name and the IP address and a second applicable type of the correspondence between the domain name and the IP address. The domain name configuration device also includes: a storage module 2020 applied to the first configuration publishing node and a processing module 2030 applied to the first configuration publishing node. The storage module 2020 is used to: store historical domain name configuration information, and the historical domain name information includes: a first version number and a first applicable type. The processing module 2030 is used to: compare whether the first applicable type and the second applicable type match. In the case where the first applicable type and the second applicable type match, the processing module 2030 is applied to the first configuration publishing node to: determine whether the second version number is updated compared to the first version number. In the case that the second version number is updated, the transceiver module 2010 is applied to the first configuration publishing node to: receive the domain name configuration information.

[0218] In a possible scenario, each network cluster further includes: W health detection nodes, where W is a positive integer greater than or equal to 2. The correspondence between domain names and IP addresses is: one domain name corresponds to one target address set, and the target address set includes: one or more IP addresses. The transceiver module 2010 is also used to: send domain name configuration information to the W health detection nodes included in the first network cluster. The processing module 2030 is also applied to the first health detection node included in the first network cluster, and is used to: parse the domain name configuration information to obtain the communication status of one or more IP addresses included in the target address set. The transceiver module 2010 is also used to: send the communication status of one or more IP addresses to the first control node. The transceiver module 2010 is also applied to the first control node, and is used to: send domain name configuration information to X configuration publishing nodes. The transceiver module 2010 is also applied to the first configuration publishing node, and is used to: send domain name configuration information to the first authoritative server corresponding to the first configuration publishing node. When the first authoritative server receives a request for resolving a domain name sent by a client, the first authoritative server obtains one or more IP addresses whose communication status meets the conditions based on the communication status of one or more IP addresses corresponding to the domain name, and sends the one or more IP addresses whose communication status meets the conditions to the client.

[0219] In one possible scenario, the MxN configuration gateway nodes included in the domain name configuration system are located in the first network, and the N configuration gateway nodes, I control nodes, J configuration release nodes and W health detection nodes included in each network cluster are all located in the second network, and the network environments of the first network and the second network are different.

[0220] In a possible scenario, the domain name configuration information further includes: an identifier of a network cluster, where the identifier is used to indicate the network cluster in which the domain name configuration information is effective.

[0221] A more detailed description of the above-mentioned transceiver module 2010, storage module 2020 and processing module 2030 can be directly obtained by referring to the relevant description in the method embodiment shown in the aforementioned drawings, and will not be repeated here.

[0222] When the domain name configuration device implements the domain name configuration method shown in any of the above-mentioned figures through software, the domain name configuration device and its various units may also be software modules. The above-mentioned domain name configuration method is implemented by calling the software module through a processor. The processor may be a CPU, an application-specific integrated circuit (ASIC), other general-purpose processors, a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic device (PLD), a complex programmable logical device (CPLD), a generic array logic (GAL) or any combination thereof.

[0223] For a more detailed description of the above-mentioned domain name configuration device, please refer to the relevant description in the embodiment shown in the above-mentioned figures, which will not be repeated here. It can be understood that the domain name configuration device shown in the above-mentioned figures is only an example provided by this embodiment. Depending on the first object contained in the first image, the domain name configuration device may include more or fewer modules, and this application is not limited to this.

[0224] When the domain name configuration device is implemented by hardware, the hardware can be implemented by a processor or a chip. The chip includes an interface circuit and a control circuit. The interface circuit is used to receive data from other devices outside the processor and transmit it to the control circuit, or send data from the control circuit to other devices outside the processor.

[0225] The control circuit is used to implement any possible implementation method in the above embodiments through a logic circuit or executing code instructions. The beneficial effects can be found in the description of any aspect of the above embodiments, which will not be repeated here.

[0226] Alternatively, the chip includes a processor and a power supply circuit, the power supply circuit is used to power the processor, and the processor can be used to implement the domain name configuration method in the aforementioned embodiment. Exemplarily, the power supply circuit can be located in the same chip as the processor, or in another chip outside the chip where the processor is located. The power supply circuit can include but is not limited to at least one of the following: a power supply subsystem, a power management chip, a power management processor, or a power management control circuit, etc.

[0227] Alternatively, when the domain name configuration device implements the domain name configuration shown in any of the above figures through hardware, the hardware may be a computing device, Fig.21A schematic diagram of a computing device provided in this application, such as Fig.21 As shown, the computing device 2100 includes: a processor 2110 and a communication interface 2120. The processor 2110 and the communication interface 2120 are coupled to each other. It is understood that the communication interface 2120 can be a transceiver or an input-output interface. Optionally, the computing device 2100 may also include a memory 2130 for storing instructions executed by the processor 2110 or storing input data required by the processor 2110 to execute instructions, or storing data generated after the processor 2110 executes instructions.

[0228] When the computing device 2100 is used to implement Figure 3 to Figure 19 In the illustrated embodiment, the processor 2110, the communication interface 2120 and the memory 2130 may also cooperate to implement various operation steps in the configuration process of the information executed by each node in the network cluster.

[0229] The specific connection medium between the communication interface 2120, the processor 2110 and the memory 2130 is not limited in the embodiment of the present application. Fig.21 The communication interface 2120, the processor 2110 and the memory 2130 are connected via a bus 2140. Fig.21 The connections between the other components are shown in bold lines, which are only for illustration and are not intended to be limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.21 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0230] The memory 2130 may be used to store software programs and modules, such as program instructions / modules corresponding to the information configuration method provided in the embodiment of the present application. The processor 2110 executes the software programs and modules stored in the memory 2130 to perform various functional applications and data processing. The communication interface 2120 may be used to communicate signaling or data with other devices. In the present application, the computing device 2100 may have multiple communication interfaces 2120.

[0231] In a possible example, the above-mentioned memory 2130 can be, but is not limited to, the memory 2130 can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a ROM, a PROM, an EPROM, an EEPROM or a flash memory. The volatile memory can be a RAM, which is used as an external cache. By way of exemplary but not limiting explanation, many forms of RAM are available, such as SRAM, DRAM, synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data date SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synchlink DRAM, SLDRAM) and direct memory bus random access memory (direct rambus RAM, DR RAM). It is understood that the processor in the embodiment of the present application can be a CPU, and can also be other general-purpose processors, DSPs, ASICs, FPGAs or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. The general-purpose processor can be a microprocessor or any conventional processor.

[0232] It should be understood that the computing device 2100 according to the embodiment of the present application may correspond to the various nodes included in the domain name configuration system in the embodiment of the present application, and the above-mentioned and other operations and / or functions of each module in the computing device 2100 are the corresponding processes executed by the various nodes included in the domain name configuration system, which will not be described in detail here for the sake of brevity.

[0233] The embodiment of the present application also provides a computing device cluster. Fig. 22 A schematic diagram of the structure of a computing device cluster provided in this application, such as Fig. 22 As shown, the computing device cluster includes at least one computing device. The computing device can be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device can also be a terminal device such as a desktop computer, a laptop computer, or a smart phone.

[0234] like Fig. 22 As shown, the computing device cluster includes at least one computing device 2100. The memory 2130 in one or more computing devices 2100 in the computing device cluster may store the same instructions for the method for domain name configuration.

[0235] In some possible implementations, the memory 2130 of one or more computing devices 2100 in the computing device cluster may also store partial instructions for domain name configuration. In other words, the combination of instructions stored in one or more computing devices 2100 may be used together to complete the domain name configuration.

[0236] It should be noted that the memory 2130 in different computing devices 2100 in the computing device cluster can store different instructions, which are respectively used to execute part of the functions of the domain name configuration device. That is, the instructions stored in the memory 2130 in different computing devices 2100 can implement the functions of one or more modules among the transceiver module, the processing module and the storage module.

[0237] In some possible implementations, one or more computing devices in the computing device cluster may be connected via a network, which may be a wide area network or a local area network. Fig.23 A possible implementation is shown. Fig.23 A schematic diagram of a possible connection method of a computing device cluster provided in this application, such as Fig.23 As shown, two computing devices 2100A and 2200B are connected via a network. Specifically, the network is connected via a communication interface in each computing device. In this type of possible implementation, the memory 2130 in the computing device 2100A stores instructions for executing the functions of the transceiver module. At the same time, the memory 2130 in the computing device 2100B stores instructions for executing the functions of the processing module and the storage module.

[0238] Fig.23 The connection method between the computing device clusters shown may be based on the needs of the domain name configuration system provided by the present application (eg, sending and receiving a large amount of data), and therefore, it is considered that the functions implemented by the transceiver module are handed over to the computing device 2100A for execution.

[0239] It should be understood that Fig.23 The functions of the computing device 2100A shown in FIG. 2100A may also be completed by multiple computing devices 2100. Similarly, the functions of the computing device 2100B may also be completed by multiple computing devices 2100.

[0240] The present application embodiment also provides another computing device cluster. The connection relationship between the computing devices in the computing device cluster can be similar to that of Fig. 22 and Fig.23 The connection mode of the computing device cluster is different in that the memory 2130 in one or more computing devices 2100 in the computing device cluster may store the same instructions for implementing the method for domain name configuration.

[0241] In some possible implementations, the memory 2130 of one or more computing devices 2100 in the computing device cluster may also store partial instructions for implementing the method for domain name configuration. In other words, the combination of one or more computing devices 2100 may jointly execute instructions for implementing the method for domain name configuration.

[0242] It should be noted that the memory 2130 in different computing devices 2100 in the computing device cluster can store different instructions for executing part of the functions of the domain name configuration method. That is, the instructions stored in the memory 2130 in different computing devices 2100 can implement the functions of one or more nodes among the gateway configuration node, the control node, and the configuration release node.

[0243] The embodiment of the present application also provides a computer program product including instructions. The computer program product may be software or a program product including instructions that can be run on a computing device or stored in any available medium. When the computer program product is run on at least one computing device, the at least one computing device executes the domain name configuration method.

[0244] The embodiment of the present application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that can be stored by a computing device or a data storage device such as a data center that contains one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk). The computer-readable storage medium includes instructions that instruct the computing device to execute the domain name configuration method.

[0245] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in the present application, and these modifications or replacements should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A domain name configuration system, characterized in that: The system includes: M network clusters, each network cluster includes: N configuration gateway nodes, I control node, J configuration publishing nodes, L authoritative servers, wherein M, N, I, J and L are all positive integers greater than or equal to 2. The first configuration gateway node included in the first network cluster receives the domain name configuration information input by the user, and sends the domain name configuration information to the H configuration gateway nodes included in the system; The first network cluster is any one of the M network clusters, the first configuration gateway node is any one of the N configuration gateway nodes included in the first network cluster, and H is a positive integer greater than or equal to 1 and less than or equal to N; The first configuration gateway node further sends the domain name configuration information to K control nodes included in the first network cluster; The K control nodes are any K control nodes among the I control nodes included in the first network cluster; The first control node included in the first network cluster sends the domain name configuration information to X configuration publishing nodes; The first control node is any one of the K control nodes, and the X configuration publishing nodes are any X configuration publishing nodes among the J configuration publishing nodes included in the first network cluster; The first configuration publishing node included in the first network cluster sends the domain name configuration information to its corresponding authoritative server; The first configuration publishing node is any one of the X configuration publishing nodes; The first authoritative server receives the domain name configuration information, and performs domain name configuration according to the correspondence between the domain name and the IP address, wherein the domain name configuration information includes: the correspondence between the domain name and the IP address.

2. The system according to claim 1, characterized in that Before the first configuration gateway node sends the domain name configuration information to any one of the other configuration gateway nodes included in the system, in the event that the first configuration gateway node fails, The second configuration gateway node receives the domain name configuration information input by the user; wherein the second configuration gateway node is any configuration gateway node in the system except the first configuration gateway node; The second configuration gateway node also sends the domain name configuration information to K control nodes included in the network cluster where it is located; The K control nodes are any K control nodes among the I control nodes included in the first network cluster; The first control node included in the first network cluster sends the domain name configuration information to X configuration publishing nodes; The first control node is any one of the K control nodes, and the X configuration publishing nodes are any X configuration publishing nodes among the J configuration publishing nodes included in the first network cluster; The first configuration publishing node included in the first network cluster sends the domain name configuration information to its corresponding authoritative server; The first configuration publishing node is any one of the X configuration publishing nodes; The first authoritative server receives the domain name configuration information, and performs domain name configuration according to the correspondence between the domain name and the IP address, wherein the domain name configuration information includes: the correspondence between the domain name and the IP address.

3. The system according to claim 2, characterized in that The second configuration gateway node is any one of all configuration gateway nodes in other network clusters except the first network cluster in the system.

4. The system according to any one of claims 1 to 3, characterized in that: After the first configuration gateway node sends the domain name configuration information to other configuration gateway nodes included in the system, in the event of a failure of the first configuration gateway node, The second configuration gateway node also sends the domain name configuration information to K control nodes included in the network cluster where it is located; The second configuration gateway node is any configuration gateway node in the system except the first configuration gateway node; the K control nodes are any K control nodes among the I control nodes included in the first network cluster; The first control node included in the first network cluster sends the domain name configuration information to X configuration publishing nodes; The first control node is any one of the K control nodes, and the X configuration publishing nodes are any X configuration publishing nodes among the J configuration publishing nodes included in the first network cluster; The first configuration publishing node included in the first network cluster sends the domain name configuration information to its corresponding authoritative server; The first configuration publishing node is any one of the X configuration publishing nodes; The first authoritative server receives the domain name configuration information, and performs domain name configuration according to the correspondence between the domain name and the IP address, wherein the domain name configuration information includes: the correspondence between the domain name and the IP address.

5. The system according to any one of claims 1 to 4, characterized in that: The domain name configuration information also includes: a second version number of the correspondence between the domain name and the IP address and a second applicable type of the correspondence between the domain name and the IP address; The first configuration publishing node stores historical domain name configuration information, and the historical domain name information includes: a first version number and a first applicable type, The first configuration publishing node included in the first network cluster receives the domain name configuration information sent by the first control node, including: The first configuration publishing node compares the first applicable type and the second applicable type to see whether they match; In the case where the first applicable type and the second applicable type match, the first configuration publishing node determines whether the second version number is updated compared to the first version number; When the second version number is updated, the first configuration publishing node receives the domain name configuration information.

6. The system according to any one of claims 1 to 5, characterized in that: Each network cluster further includes: W health detection nodes, where W is a positive integer greater than or equal to 2; the correspondence between the domain name and the IP address is: one domain name corresponds to one target address set, and the target address set includes: one or more IP addresses; The first configuration gateway node also sends the domain name configuration information to W health detection nodes included in the first network cluster; The first health detection node included in the first network cluster parses the domain name configuration information to obtain the communication status of one or more IP addresses included in the target address set, and sends the communication status of the one or more IP addresses to the first control node; The first control node sends the domain name configuration information to X configuration publishing nodes; The first configuration publishing node sends the domain name configuration information to its corresponding first authoritative server; When the first authoritative server receives the request for resolving the domain name sent by the client, the first authoritative server obtains one or more IP addresses whose communication status meets the conditions based on the communication status of one or more IP addresses corresponding to the domain name, and sends the one or more IP addresses whose communication status meets the conditions to the client.

7. The system according to any one of claims 1 to 6, characterized in that: The MxN configuration gateway nodes included in the system are located in the first network, and the N configuration gateway nodes, I control node, J configuration release nodes and W health detection nodes included in each network cluster are all located in the second network, and the network environments of the first network and the second network are different.

8. The system according to any one of claims 1 to 7, characterized in that: The domain name configuration information further includes: an identifier of a network cluster, where the identifier is used to indicate the network cluster in which the domain name configuration information is effective.

9. A domain name configuration method, characterized in that: The method is performed by a domain name configuration system, which includes: M network clusters, each network cluster includes: N configuration gateway nodes, I control node, J configuration publishing nodes, L authoritative servers, where M, N, I, J and L are all positive integers greater than or equal to 2; The method comprises: The first configuration gateway node included in the first network cluster receives the domain name configuration information input by the user, and sends the domain name configuration information to the H configuration gateway nodes included in the system; The first network cluster is any one of the M network clusters, the first configuration gateway node is any one of the N configuration gateway nodes included in the first network cluster, and H is a positive integer greater than or equal to 1 and less than or equal to N; The first configuration gateway node further sends the domain name configuration information to K control nodes included in the first network cluster; The K control nodes are any K control nodes among the I control nodes included in the first network cluster; The first control node included in the first network cluster sends the domain name configuration information to X configuration publishing nodes; The first control node is any one of the K control nodes, and the X configuration publishing nodes are any X configuration publishing nodes among the J configuration publishing nodes included in the first network cluster; The first configuration publishing node included in the first network cluster sends the domain name configuration information to its corresponding authoritative server; The first configuration publishing node is any one of the X configuration publishing nodes; The first authoritative server receives the domain name configuration information, and performs domain name configuration according to the correspondence between the domain name and the IP address, wherein the domain name configuration information includes: the correspondence between the domain name and the IP address.

10. The method according to claim 9, characterized in that Before the first configuration gateway node sends the domain name configuration information to any one of the other configuration gateway nodes included in the system, the method further includes: In the case where the first configuration gateway node fails, a second configuration gateway node receives the domain name configuration information input by the user; wherein the second configuration gateway node is any configuration gateway node in the system except the first configuration gateway node; The second configuration gateway node also sends the domain name configuration information to K control nodes included in the network cluster where it is located; The K control nodes are any K control nodes among the I control nodes included in the first network cluster; The first control node included in the first network cluster sends the domain name configuration information to X configuration publishing nodes; The first control node is any one of the K control nodes, and the X configuration publishing nodes are any X configuration publishing nodes among the J configuration publishing nodes included in the first network cluster; The first configuration publishing node included in the first network cluster sends the domain name configuration information to its corresponding authoritative server; The first configuration publishing node is any one of the X configuration publishing nodes; The first authoritative server receives the domain name configuration information, and performs domain name configuration according to the correspondence between the domain name and the IP address, wherein the domain name configuration information includes: the correspondence between the domain name and the IP address.

11. The method according to claim 10, characterized in that The second configuration gateway node is any one of all configuration gateway nodes in other network clusters except the first network cluster in the system.

12. The method according to any one of claims 9 to 11, characterized in that: After the first configuration gateway node sends the domain name configuration information to other configuration gateway nodes included in the system, The method further comprises: In the event that the first configuration gateway node fails, the second configuration gateway node further sends the domain name configuration information to K control nodes included in the network cluster where it is located; The second configuration gateway node is any configuration gateway node in the system except the first configuration gateway node; the K control nodes are any K control nodes among the I control nodes included in the first network cluster; The first control node included in the first network cluster sends the domain name configuration information to X configuration publishing nodes; The first control node is any one of the K control nodes, and the X configuration publishing nodes are any X configuration publishing nodes among the J configuration publishing nodes included in the first network cluster; The first configuration publishing node included in the first network cluster sends the domain name configuration information to its corresponding authoritative server; The first configuration publishing node is any one of the X configuration publishing nodes; The first authoritative server receives the domain name configuration information, and performs domain name configuration according to the correspondence between the domain name and the IP address, wherein the domain name configuration information includes: the correspondence between the domain name and the IP address.

13. The method according to any one of claims 9 to 12, characterized in that: The domain name configuration information also includes: a second version number of the correspondence between the domain name and the IP address and a second applicable type of the correspondence between the domain name and the IP address; The first configuration publishing node stores historical domain name configuration information, the historical domain name information includes: a first version number and a first applicable type, and the method further includes: The first configuration publishing node compares the first applicable type and the second applicable type to see whether they match; In the case where the first applicable type and the second applicable type match, the first configuration publishing node determines whether the second version number is updated compared to the first version number; When the second version number is updated, the first configuration publishing node receives the domain name configuration information.

14. The method according to any one of claims 9 to 13, characterized in that: Each network cluster further includes: W health detection nodes, where W is a positive integer greater than or equal to 2; the corresponding relationship between the domain name and the IP address is: one domain name corresponds to one target address set, and the target address set includes: one or more IP addresses, and the method further includes: The first configuration gateway node also sends the domain name configuration information to W health detection nodes included in the first network cluster; The first health detection node included in the first network cluster parses the domain name configuration information to obtain the communication status of one or more IP addresses included in the target address set, and sends the communication status of the one or more IP addresses to the first control node; The first control node sends the domain name configuration information to X configuration publishing nodes; The first configuration publishing node sends the domain name configuration information to its corresponding first authoritative server; When the first authoritative server receives the request for resolving the domain name sent by the client, the first authoritative server obtains one or more IP addresses whose communication status meets the conditions based on the communication status of one or more IP addresses corresponding to the domain name, and sends the one or more IP addresses whose communication status meets the conditions to the client.

15. The method according to any one of claims 9 to 14, characterized in that: The MxN configuration gateway nodes included in the domain name configuration system are located in the first network, and the N configuration gateway nodes, I control node, J configuration publishing nodes and W health detection nodes included in each network cluster are all located in the second network, and the network environments of the first network and the second network are different.

16. The method according to any one of claims 9 to 15, characterized in that: The domain name configuration information further includes: an identifier of a network cluster, where the identifier is used to indicate the network cluster in which the domain name configuration information is effective.

17. A computing device cluster, characterized in that: comprising at least one computing device, each computing device comprising a processor and a memory; The processor of the at least one computing device is used to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the domain name configuration method according to any one of claims 9 to 16.

18. A computer-readable storage medium, characterized in that: The method comprises computer program instructions. When the computer program instructions are executed by a computing device cluster, the computing device cluster performs the method according to any one of claims 9 to 16.

19. A computer program product comprising instructions, characterized in that When the instruction is executed by a computing device cluster, the computing device cluster executes the domain name configuration method according to any one of claims 9 to 16.

Images