Domain name configuration system

Abstract

Disclosed is a domain name configuration system, which relates to the technical field of communications. A first configuration gateway node receives domain name configuration information, and transmits the domain name configuration information to H configuration gateway nodes among all the configuration gateway nodes, which are comprised in other network clusters. In this way, the rapid propagation of domain name configuration information between network clusters is realized, so as to reduce network latency of the arrival of the domain name configuration information at the network clusters, thereby providing a guarantee for the network clusters to receive consistent domain name configuration information. The first configuration gateway node sends the domain name configuration information to K control nodes, which are comprised in a first network cluster, a first control node sends the domain name configuration information to X configuration publishing nodes, which are comprised in the first network cluster, and a first configuration publishing node transmits the domain name configuration information to an authoritative server. In this way, the transmission efficiency of domain name configuration information within a network cluster is improved, so as to reduce network latency of the arrival of the domain name configuration information at an authoritative server, thereby providing a guarantee for the authoritative server to receive consistent domain name configuration information.

Description

A domain name configuration system Technical Field

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

[0002] The Domain Name System (DNS) can include multiple authoritative servers. Each authoritative server receives domain name configuration information sent by the management and control platform and resolves domain names (such as www.xxxx.com.cn) to Internet Protocol (IP) addresses (such as xxxx) based on the domain name configuration information received.

[0003] When there is a significant network delay or communication failure between the authoritative server and the management and control platform, multiple authoritative servers may receive inconsistent domain name configuration information. If multiple authoritative servers with inconsistent domain name configuration information receive the same domain name resolution request from a client, these multiple authoritative servers will resolve the domain name resolution request based on their respective domain name configuration information. This may result in different resolution results for the same domain name resolution request, affecting the user experience.

[0004] 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 a 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 node, J configuration publishing nodes, and L authoritative servers, where M, N, I, J, and L are all positive integers greater than or equal to 2. 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 the domain name configuration 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 also 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 included 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 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 included in the J configuration publishing nodes included in the first network cluster. A 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 configures the domain name based on 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 transmitting domain name configuration information to each network cluster is saved, the network delay for 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 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 for 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 one possible implementation, before the first configuration gateway node sends domain name configuration information to any of the other configuration gateway nodes included in the domain name configuration system, in the event of a failure of the first configuration gateway node, a 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 other than the first configuration gateway node. The second configuration gateway node also sends the domain name configuration information to the K control nodes included in its network cluster. The K control nodes are any K control nodes included in the I control nodes included in the first network cluster. A 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 included in 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 based on 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. In this way, even if the first configuration gateway node that receives domain name configuration information fails, the user can still use the domain name configuration system to configure the domain name. The user will not be aware that the configuration gateway node that receives their 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 configuration gateway nodes in network clusters other than the first network cluster in the domain name configuration system. In this way, if the first configuration gateway node receiving domain name configuration information fails, the configuration gateway nodes in other network clusters in the domain name configuration system can receive the domain name configuration information. This avoids the delay required for the configuration gateway node to receive the domain name configuration information input by the user, caused by a failure of the first configuration gateway node, which in turn causes failures in other configuration gateway nodes in the first network cluster.

[0010] In another possible implementation, after 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 event of a failure of the first configuration gateway node, the second configuration gateway node further sends the domain name configuration information to the K control nodes included in its network cluster. The second configuration gateway node is any configuration gateway node in the domain name configuration system other than the first configuration gateway node. The K control nodes are any K control nodes from the I control nodes included in the first network cluster. The first control node 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. The X configuration publishing nodes are any X configuration publishing nodes from the J configuration publishing nodes included in the first network cluster. The first configuration publishing node 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 based on 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. 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, reducing the probability of inconsistent domain name configuration information received by each authoritative server in the first network cluster.

[0011] In another possible embodiment, 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 the first applicable type and the second applicable type to see whether they match. In the case that 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 that 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 embodiment, each network cluster further includes W health detection nodes. 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. 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 resolves 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 a request from a client to resolve a domain name, the first authoritative server obtains one or more IP addresses whose communication status meets a condition based on the communication status of the one or more IP addresses corresponding to the domain name, and sends the one or more IP addresses whose communication status meets the condition 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 transmitted 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 communication quality and user experience.

[0013] In another possible implementation, the M x N configuration gateway nodes included in the domain name configuration system are located in the first network. 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. 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 due to 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 due to large network delays within the network cluster.

[0014] In another possible implementation, the domain name configuration information also includes an identifier of a network cluster, which indicates the network cluster in which the domain name configuration information is effective. Thus, when a domain name resolution request is received, the authoritative server closest to the client initiating the domain name resolution request is used to resolve the domain name resolution request based on the identifier of the network cluster, thereby improving 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, which includes: M network clusters. Each network cluster includes: N configuration gateway nodes, I control node, 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 network cluster among the M network clusters, the first configuration gateway node is any configuration gateway node among 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 based on 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, which includes: M network clusters. Each network cluster includes: N configuration gateway nodes, I control node, J configuration publishing nodes, and L authoritative servers. 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 a first configuration gateway node included in a first network cluster, configured to: receive domain name configuration information input by a 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. 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, and 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, configured to: send 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 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 configured 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 based on 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.

[0017] In a fourth aspect, the present application provides a processor configured 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 including a processor and a memory. The processor of at least one computing device is configured 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 comprising computer program instructions, which, when executed in a computing device cluster, cause the computing device cluster to execute 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 that, when executed on a computing device cluster, enables the computing device cluster to perform 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 be referred 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 in the above aspects, this application can also be further combined to provide more implementations. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] FIG1 is a schematic diagram of the structure of a first domain name configuration system;

[0023] FIG2 is a schematic diagram of the structure of a second domain name configuration system;

[0024] FIG3 is a schematic diagram of a first domain name configuration system provided by this application;

[0025] FIG4 is a schematic diagram of configuring a gateway node to receive information provided by the present application;

[0026] FIG5 is a schematic diagram of a connection of a first configuration gateway node provided in this application;

[0027] FIG6 is a schematic diagram of the structure of a communication model provided by this application;

[0028] FIG7 is a schematic diagram of a second configuration of a gateway node provided in this application;

[0029] FIG8 is a schematic diagram of a first process for determining and configuring a gateway node provided by the present application;

[0030] FIG9 is a schematic diagram of a second process for determining and configuring a gateway node provided by the present application;

[0031] FIG10 is a schematic diagram of the transmission of the first type of information provided by this application to a configuration gateway node within a network cluster;

[0032] FIG11 is a schematic diagram of the transmission of the second type of information provided by this application to a configuration gateway node within a network cluster;

[0033] FIG12 is a schematic diagram of the transmission of the first type of information provided by this application between the configuration gateway node and the control node;

[0034] FIG13 is 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] FIG14 is a schematic diagram of the transmission of the first type of information provided by the present application between the control node and the configuration publishing node;

[0036] FIG15 is 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] FIG16A is a schematic diagram of the structure of the first network cluster provided by this application;

[0038] FIG16B is a schematic diagram of the structure of the second network cluster provided by this application;

[0039] FIG17 is a flow chart of a domain name configuration method provided by this application;

[0040] FIG18 is a schematic diagram of the structure of the second domain name configuration system provided by this application;

[0041] FIG19 is a schematic structural diagram of a third domain name configuration system provided by this application;

[0042] FIG20 is a schematic structural diagram of a domain name configuration device provided by the present application;

[0043] FIG21 is a schematic diagram of the structure of a computing device provided by the present application;

[0044] FIG22 is a schematic diagram of the structure of a computing device cluster provided by this application;

[0045] FIG23 is a schematic diagram of a possible connection method of a computing device cluster provided in this application. DETAILED DESCRIPTION

[0046] Domain name resolution The domain name configuration 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 (IP) address (such as xxxx) based on the domain name configuration information received. The management and control platform may be an application (application, app) that implements the domain name configuration function. The application may 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 processing devices such as augmented reality (AR) and virtual reality (VR) devices. This embodiment does not impose any special restrictions on the specific device form of the processing device on which the management and control platform is installed. For example, the management and control platform can be installed on a tablet computer or a mobile phone. In this application, domain name configuration information is also referred to as information.

[0047] There are many ways to process configuration information from a device to an authoritative server. Here are three common ways to process configuration information from a device.

[0048] Method ①

[0049] Figure 1 is a schematic diagram of the structure of the first domain name configuration system. As shown in Figure 1, 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 transferring the domain name configuration system configuration information to the authoritative server included in the domain name configuration system is described. Specifically, the master node of network cluster 1 receives the information transmitted by the control platform and transmits the information to the backup node of network cluster 1 and the authoritative server of network cluster 1.

[0051] When the master node of network cluster 1 receives information 1 transmitted by the control platform but fails to transmit information 1 to the backup 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 initiates the next information transmission process and transmits information 2 to the backup node of network cluster 1. The backup node of network cluster 1 then transmits information 2 to the authoritative server of network cluster 1. This process results in the authoritative server of network cluster 1 not receiving information 1, while the authoritative servers included in other normally functioning network clusters in the domain name configuration system do receive information 1, resulting in inconsistent information received by the authoritative servers of 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] Continuing with the process of configuring network cluster 1 within the domain name configuration system as an example, the process of transmitting configuration information from the domain name configuration system to the authoritative server within the domain name configuration system will be described. Specifically, the master node and backup node of network cluster 1 receive information transmitted by the management and control platform. If both the master node and 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. If at least one of the master node and 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 master node and the backup node fails cannot receive information, while the authoritative server in the network cluster where both the master 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 is a schematic diagram of the structure of the second domain name configuration system. As shown in Figure 2, 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] Taking the process of configuring network cluster 1 included in the domain name configuration system as an example, the process of transmitting the configuration information of the domain name configuration system to the authoritative server included in the domain name configuration system is described. The process is as follows: the message middleware of network cluster 1 receives the information transmitted by the 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 is a schematic diagram of the first domain name configuration system provided herein. As shown in Figure 3, domain name configuration system 300 includes: network clusters 1 through M, where M is a positive integer greater than or equal to 2. Network clusters 1 through M included in domain name configuration system 300 can be deployed in different ways, each of which is described below.

[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] Illustratively, 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] In a second possible scenario, network clusters 1 to M included in the domain name configuration system 300 are deployed in different geographical locations.

[0066] In this scenario, one or more network clusters 310 can be deployed in the same geographic location. Taking M equal to 3 as an example, the domain name configuration system 300 includes the deployment of network clusters 1 through 3. As shown in Table 2, network clusters 1 and 2 are deployed in geographic location 1, and network cluster 3 is deployed in location 2.

[0067] Table 2

[0068] 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. This application is not limited to this.

[0069] 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, if 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, if 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 network cluster deployment methods can be selected, and this application does not limit this.

[0070] Please continue to refer to 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.

[0071] In one possible scenario, the configuration gateway node included in each network cluster in the domain name configuration system is located on the first network. This reduces network latency during information transmission between the network clusters included in the domain name configuration system, improves transmission efficiency, and reduces the probability of information inconsistencies caused by significant network latency between the network clusters.

[0072] 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.

[0073] Taking 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 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 shows the correspondence between two domain names and the first target address set. As shown in Table 3, the rows corresponding to sequence numbers 1 to 4 in Table 3 show the domain name information with version number 100, including: the correspondence between domain name 1 and ip1 and ip2, and the correspondence between domain name 2 and ip3 and ip4.

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

[0075] Table 3

[0076] Exemplarily, the gateway node is configured to verify the user-entered information shown in Table 3 and confirm that the content of rows corresponding to sequence numbers 1, 3, 6, and 6 conform to the DNS structure, indicating that the verification has passed. The gateway node is configured to encapsulate the verified information into a message format that can be transmitted in a P2P network and transmit the encapsulated information to the control node. For information on message formats that can be transmitted in a P2P network, please refer to the general technical description and will not be repeated here.

[0077] In some possible scenarios, the user-entered information may also include a network cluster identifier (namespace), which indicates the network cluster in which the domain name configuration information is effective. For example, if the domain name configuration system includes network clusters 1 through M, and the user-entered information includes a network cluster identifier (namespace), as shown in the last column of Table 4, the last column of the rows corresponding to sequence numbers 1 through 3 in Table 4 indicates the correspondence between domain name 1 and IP address 1, and the correspondence between domain name 2 and IP addresses 3 and 4 is effective in network cluster 1.

[0078] Table 4

[0079] Figure 4 is a schematic diagram of a configuration gateway node receiving information provided by the present application. As shown in Figure 4, 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. Wherein, 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.

[0080] Based on the above embodiments, the domain name configuration method provided by this application is exemplarily described below with reference to the accompanying figures. The domain name configuration method provided by this embodiment includes the following: information transmission between different network clusters and information transmission between nodes within a network cluster. These two processes are described below.

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

[0082] Depending on the value of H, the information propagation mode between different network clusters is different, which is explained below.

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

[0084] The first configuration gateway node of the first network cluster receives the information input by the user, determines the second configuration gateway node of the second network cluster from all configuration gateway nodes included in network clusters other than the first network cluster included in the domain name configuration system, and transmits the information to the second configuration gateway node. The second configuration gateway node receives the information and determines the third configuration gateway node of the third network cluster from all configuration gateway nodes included in network clusters other than the first and second network clusters included in the domain name configuration system. The above process is repeated until all network clusters included in the domain name configuration system have received the information.

[0085] For example, FIG5 is a connection diagram of the first configuration gateway node provided by this application. As shown in FIG5 , 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.

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

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

[0088] 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 that 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 that 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.

[0089] The above description uses the example of a first applicable type and a second applicable type matching (e.g., both indicating domain name information) 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 (e.g., 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 the information.

[0090] Depending on the different representations of the version number, the first configuration gateway node may determine in different ways whether the second version number is updated compared to the first version number. Several possible examples are given below.

[0091] 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) with 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, no update is found.

[0092] 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 numerical 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 numerical 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.

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

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

[0095] 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 the domain name configuration information sent by the first control node, including: the first configuration release node compares the third applicability type and the fourth applicability type to see whether they match. In the case where the third applicability type and the third applicability type match, 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.

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

[0097] Taking the example of information transmission between each network cluster in a one-to-two manner (i.e., H equals 2), a communication model as shown in Figure 6 can be formed in this case. Figure 6 is a structural diagram of a communication model provided by this application. As shown in Figure 6, node 11 sends information to nodes 21 and 22, node 21 sends information to nodes 31 and 32, and node 22 sends information to nodes 33 and 34.

[0098] Taking the communication model shown in FIG6 as an example, the information transmission process between the various network clusters is described.

[0099] The first configuration gateway node of the first network cluster receives information input by the user, determines a second configuration gateway node of the second network cluster and a third configuration gateway node of the third network cluster from all configuration gateway nodes included in network clusters other than 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 a fourth configuration gateway node of the fourth network cluster and a fifth configuration gateway node of the fifth network cluster from all configuration gateway nodes included in network clusters other than the first, second, and third network clusters included in the domain name configuration system. The above process is repeated until all network clusters included in the domain name configuration system have received information.

[0100] Exemplarily, FIG7 is a connection diagram of the second configuration gateway node provided by the present application. As shown in FIG7 , the domain name configuration system includes network clusters 1 to network clusters 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 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 cluster M, and sends information to the configuration gateway node 41 and the configuration gateway node 42. The above process is repeated until all network clusters included in the domain name configuration information receive the information.

[0101] 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 Case 1. For related descriptions, please refer to the above and will not be repeated here.

[0102] 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.

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

[0104] In Example A, the first configuration gateway node determines one or more configuration gateway nodes based on the communication status with each of the other configuration gateway nodes. FIG8 is a schematic diagram of the first process for determining a configuration gateway node provided by this application. As shown in FIG8 , the process may include the following steps ① to ③.

[0105] In step 1, the first configuration gateway node determines the communication status with each of the other configuration gateway nodes. The first configuration gateway node can use different methods to determine the communication status with the other configuration gateway nodes, such as network delay, network bandwidth, etc.

[0106] For example, a domain name configuration system includes configuration gateway nodes 1 through n. Configuration gateway node 1 transmits the same data to configuration gateway nodes 2 through n, respectively. The network delay between configuration gateway nodes 2 through n in receiving the data is obtained, and the communication status between configuration gateway node 1 and each of configuration gateway nodes 2 through n is determined using the network delay.

[0107] In another example, the domain name configuration system includes configuration gateway nodes 1 to n. Configuration gateway node 1 obtains the network bandwidth between itself and each of configuration gateway nodes 2 to n, and uses the network bandwidth to determine the communication status between configuration gateway node 1 and each of configuration gateway nodes 2 to n.

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

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

[0110] 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.

[0111] In step 3, the first configuration gateway node determines one or more configuration gateway nodes based on the communication state sequence. For example, the first configuration gateway node determines one or more configuration gateway nodes that are ranked first in the communication state sequence (such as the network delay sequence or the network bandwidth sequence).

[0112] In Example B, the first configured gateway node determines one or more configured gateway nodes based on the relationship between the communication status of each configured gateway node among the other configured gateway nodes and a set threshold. Figure 9 is a schematic diagram of the second process for determining a configured gateway node provided by this application. As shown in Figure 9, the process may include the following steps ① to ②.

[0113] Step 1 in this example is the same as step 1 in Example A, with the difference being step 2. Step 2 is specifically described as follows: the first configured gateway node compares the communication status of each configured gateway node with the set threshold, and if 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.

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

[0115] 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 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 a power outage, the failure of the control platform to operate normally, the failure of the medium for transmitting information to operate normally, etc. This application does not limit the cause of the failure.

[0116] The process of transmitting the user-entered information to the domain name configuration system varies depending on the configuration gateway node that fails, and is described below.

[0117] 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.

[0118] In this scenario, the second configuration gateway node receives the domain name configuration information entered by the user. The second configuration gateway node can be any configuration gateway node in the domain name configuration system other than the first configuration gateway node. This allows the user to continue configuring their domain name using this domain name configuration system even if the first configuration gateway node receiving the domain name configuration information fails. This unawareness of the failure of the configuration gateway node receiving their input increases the reliability of the domain name configuration system and enhances the user experience.

[0119] The second configuration gateway node can be any one of all the configuration gateway nodes in the other network clusters other than the first network cluster in the domain name configuration system. The management and control platform can use any of the methods given in Examples A to C to determine the second configuration gateway node, and this application is not limited to this. In this way, in the event that the first configuration gateway node that receives the domain name configuration information fails, the configuration gateway nodes in the 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 due to 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. Exemplarily, the domain name configuration system includes network clusters 1 to M. Network cluster i includes configuration gateway nodes i1 to iN, where i is a positive integer from 1 to M. Configuration gateway node 11 receives the information input by the user and sends a fault signal before sending information to the configuration gateway nodes other than configuration gateway node 11 included in the domain name configuration system. In this case, all other configuration gateway nodes (such as configuration gateway node 21) included in the domain name configuration system except configuration gateway nodes 12 to 1N can receive the information input by the user.

[0120] 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 Example A to Example C, which is not limited in this application. Exemplarily, the domain name configuration system includes network cluster 1 to network cluster M. Network cluster i includes configuration gateway node i1 to configuration gateway node iN, where i is a positive integer from 1 to M. The configuration gateway node 11 receives information input by the user, and sends a fault before sending information to the configuration gateway nodes included in the domain name configuration system except the configuration gateway node 11. In this case, the configuration gateway nodes 12 to configuration gateway node 1N (such as configuration gateway node 12) included in the domain name configuration system can all receive information input by the user.

[0121] 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.

[0122] 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 and will not be repeated here.

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

[0124] The preceding text, combined with the accompanying figures, describes the process of information transmission between network clusters within the domain name configuration system using configuration gateway nodes. The following, combined with the accompanying figures, illustrates the process of information transmission within a network cluster. The information received by the configuration gateway node, control node, configuration publishing node, authority server, and health detection node within the network cluster is similar to the information received by the configuration gateway node described in Scenario 1 above. For details, please refer to the preceding text and will not be repeated here. The following describes only how various nodes transmit information to the next node.

[0125] In one possible scenario, the configuration gateway node, control node, and configuration publishing node included in the network cluster are located on a second network. The first network and the second network are different. This reduces network latency within the network cluster, improves transmission efficiency, and reduces the probability of inconsistent domain name configuration information caused by significant network latency within the network cluster.

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

[0127] 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.

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

[0129] Type ①: Information transmission process between the configuration gateway node 11 and the configuration gateway node 1N included in the network cluster 1.

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

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

[0132] The configuration gateway node 11 sends information to one of the configuration gateway nodes 12 to the configuration gateway node 1N, and the configuration gateway node that receives the information sends information to other configuration gateway nodes until each of the configuration gateway nodes 11 to the configuration gateway node 1N receives the information. Figure 10 is a schematic diagram of the transmission of the first type of information provided by the present application within the configuration gateway node of the network cluster. As shown in Figure 10, the configuration gateway node 11 sends information to the configuration gateway node 12 from the configuration gateway node 12 to the configuration gateway node 1N. The configuration gateway node 12 sends information to the configuration gateway node 13 from the configuration gateway node 13 to the configuration gateway node 1N, and the process is repeated 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, and the target configuration gateway node from the other configuration gateway nodes included in the network cluster 1 is used as the object of information sending. The target configuration gateway node can be the configuration gateway node with the best communication status, or it can be any randomly determined configuration gateway node.

[0133] 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).

[0134] 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. Figure 11 is a schematic diagram of the transmission of the second type of information provided by this application in the configuration gateway node within the network cluster. As shown in Figure 11, the configuration gateway node 11 sends information to the configuration gateway node 12 and the configuration gateway node 13 in the configuration gateway node 12 to the configuration gateway node 1N. The configuration gateway node 12 sends information to the configuration gateway node 13 and the configuration gateway node 14 in the configuration gateway node 13 to the configuration gateway node 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 use the method given in Example A to Example 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 randomly determined, or determined according to the communication status, or determined 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). This application is not limited to this.

[0135] When G is greater than or equal to 3, the configuration gateway node 11 can use 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.

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

[0137] 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 is described below.

[0138] 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).

[0139] FIG12 is 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. As shown in FIG12 , configuration gateway node 11 sends information to control node 11 among control nodes 11 to 1I. Control nodes 12 to 1I that have not received the information receive information sent by configuration gateway node 12 to configuration gateway node 1N, such as control node 12 receiving information sent by configuration gateway node 12. The configuration gateway node can use the methods provided in Examples A to C to determine the target control node from control nodes 11 to 1I as the object of information transmission.

[0140] 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).

[0141] FIG13 is a schematic diagram illustrating the transmission of the second type of information provided herein between a configuration gateway node and a control node. As shown in FIG13 , configuration gateway node 11 transmits information to control node 11 and control node 12 among control nodes 11 to 1I. Control nodes 13 to 1I that have not received the information receive information sent by configuration gateway node 12 to configuration gateway node 1N, such as control node 13 and control node 14 receiving information sent by configuration gateway node 12. The configuration gateway node can employ the methods described in Examples A to C to determine two target control nodes from control node 11 to 1I as the targets for information transmission.

[0142] 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 a method where K is equal to 2, which will not be described in detail here.

[0143] Type ③: The information transmission process between the control node and the configuration release node included in the network cluster 1.

[0144] The first control node sends domain name configuration information to X configuration publishing nodes included in the first network cluster. The first control node indicates one of the K control nodes. X is a positive integer less than or equal to J. The information transmission process between the control node and the configuration publishing node varies depending on the value of X, which is described separately below.

[0145] 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).

[0146] FIG14 is a schematic diagram of the transmission of the first type of information provided by the present application between a control node and a configuration publishing node. As shown in FIG14 , control node 11 sends information to configuration publishing node 11 among configuration publishing nodes 11 to 1L. Configuration publishing nodes 12 to 1L that have not received the information receive information sent by control node 12 to control node 1I, such as configuration publishing node 12 receiving information sent by control node 12. The control node can use the methods provided in Examples A to C to determine a target configuration publishing node from configuration publishing nodes 11 to 1L as the object to which the information is to be sent.

[0147] 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).

[0148] FIG15 is a schematic diagram of the second type of information transmission provided by the present application between a control node and a configuration publishing node. As shown in FIG15 , control node 11 sends information to configuration publishing node 11 and configuration publishing node 12 in a range from configuration publishing node 11 to configuration publishing node 1L. Configuration publishing node 13 to configuration publishing node 1L that have not received the information receive information sent by control node 12 to control node 1I, such as configuration publishing node 13 and configuration publishing node 14 receiving information sent by control node 12. The control node can use the methods provided in Examples A to C to determine two target control nodes from configuration publishing node 11 to configuration publishing node 1L as the targets for information transmission.

[0149] 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.

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

[0151] The first configuration publishing node receives the domain name configuration information, parses the domain name configuration information to obtain a correspondence between the domain name and the IP address, and sends the correspondence between the domain name and the IP address to a 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 based on the correspondence between the domain name and the IP address.

[0152] Exemplarily, network cluster 1 includes configuration publishing node 11 and authoritative server 1. Configuration publishing node 11 and authoritative server 1 are deployed on the same processing device. Upon receiving the information shown in Table 5, configuration publishing node 11 transmits the information to authoritative server 1. Upon receiving a resolution request for domain name 1, authoritative server 1 obtains either IP1 or IP2 as a resolution result based on the correspondence between domain name 1 and IP addresses 1 and 2 as shown in information 1 in Table 5, and transmits the resolution result to the client.

[0153] Table 5

[0154] In one 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 scenario, authoritative server 1 receives the domain name resolution request and, based on the received geographic location information, determines IP address segment 1 corresponding to geographic location 1. Based on the correspondence between domain names and multiple IP addresses, authoritative server 1 determines that the IP address in IP address segment 1 is the domain name resolution result, and sends this IP address to the client.

[0155] The above describes a scenario where the configuration release nodes and authoritative servers included in a network cluster are deployed on the same processing device in a one-to-one manner. In some possible scenarios, the configuration release nodes and authoritative servers 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 and authoritative servers 1 through n. Configuration release node 1 and authoritative servers 1 through n are deployed on the same electronic device. Upon receiving information 1 shown in Table 5, configuration release node 1 transmits information 1 to authoritative servers 1 through n.

[0156] 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, it can select the IP address with the best communication status 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.

[0157] FIG16A is a schematic diagram of the structure of the first network cluster provided by the present application. As shown in FIG16A , the network cluster further includes: health detection nodes 11 to 1K. Gateway node 11 is configured to send information to one of health detection nodes 11 to 1K (e.g., 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 control nodes 11 to 1I (e.g., control node 11).

[0158] In some possible cases, FIG16B is a schematic diagram of the structure of the second network cluster provided by this application. As shown in FIG16B , the gateway node 11 is configured to send information to multiple of the health detection nodes 11 to 1K (e.g., 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.

[0159] 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, and describes 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, and so on. The above text illustrates the information transmission process in the domain name configuration system in conjunction with the accompanying drawings. Based on the domain name configuration system provided in Figures 3 to 16B, this application also provides a possible specific example of a domain name configuration method, as shown in Figure 17. Figure 17 is a flow chart of a domain name configuration method provided by this application. For an introduction to the domain name configuration system, please refer to the description of Figures 3 to 16B above, which will not be repeated here. The domain name configuration method provided in this embodiment includes the following steps S1710 to S1750.

[0160] 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.

[0161] 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.

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

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

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

[0165] 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.

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

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

[0168] 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.

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

[0170] The rapid propagation of domain name configuration information between network clusters is achieved, which saves the transmission time of domain name configuration information between network clusters, reduces the network delay for domain name configuration information to reach each network cluster, and provides a guarantee 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, and 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 for 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. For more relevant content about the domain name configuration method, please refer to the relevant description of the domain name configuration system above, which will not be repeated here.

[0171] 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 above-mentioned domain name configuration system and will not be repeated here.

[0172] Based on the above description of the domain name configuration system and domain name configuration method provided by this application, the following takes the example of a domain name configuration system including two network clusters, each network cluster including 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 using 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.

[0173] Figure 18 is a schematic diagram of the structure of the second domain name configuration system provided in this application. As shown in Figure 18, 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, and 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, and authoritative server 3 and authoritative server 4. The contents of information 1 and information 2 are shown in Table 6.

[0174] Table 6

[0175] The following describes the process of configuring the domain name system configuration information by taking the domain name configuration system configuration information 1 shown in FIG18 as an example. The process includes the following steps ① and ②.

[0176] 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 ③.

[0177] ①, 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.

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

[0179] For configuration gateway node 3: configuration gateway node 3 compares the applicable type (key) and version number (version) contained in information 1. If 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 configuration gateway node 1 to configuration gateway node 3) and information 1 with version number 100 transmitted by configuration gateway node 2 are the same information. In this case, configuration gateway node 3 no longer receives information 1 with version number 100 transmitted by configuration gateway node 2.

[0180] 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 is established, 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.

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

[0182] For configuration gateway node 4: configuration 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 configuration gateway node 2 to configuration gateway node 4 in ②) and information 1 with version number 100 sent by configuration gateway node 3. If the applicable type is the same and the version number is not updated, it confirms that the information it has received and information 1 with version number 100 sent by configuration gateway node 3 are the same information. In this case, configuration gateway node 4 no longer receives information 1 with version number 100 transmitted by configuration gateway node 3.

[0183] 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.

[0184] 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.

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

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

[0187] 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 .

[0188] Gateway node 2 is configured to transmit information 1 with version number 100 to control node 1 and control node 2. Control node 1 compares the applicable type (key) and version number (version) of the information it has received (such as information 1 with version number 100 transmitted by gateway node 1 to control node 1) with the information 1 with version number 100 transmitted by gateway node 2 to control node 1. If the applicable types are the same and the version number has not been updated, it confirms that it has received information 1 with version number 100. In this case, control node 1 no longer receives information 1 with version number 100 sent by gateway node 2. The process of control node 2 receiving information 1 with version number 100 is the same as that of control node 1 and will not be repeated here.

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

[0190] In the event that at least one of control node 1 and control node 2 fails, the failed control node waits until it recovers. After the failed control node recovers, it receives information 1 with version number 100 sent by at least one of configuration gateway node 1 and configuration gateway node 2.

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

[0192] 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.

[0193] Control node 2 transmits information 1 with version number 100 to configuration release node 1 and configuration release node 2. Configuration release 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 release node 1) with the information 1 with version number 100 transmitted by control node 2 to configuration release node 1. If the applicable type is the same and the version number has not been updated, it confirms that it has received information 1 with version number 100. In this case, control node 1 no longer receives information 1 with version number 100 sent by control node 2. The process of configuration release node 2 receiving information 1 with version number 100 is the same as the process of configuration release node 1 receiving information 1 with version number 100, and will not be repeated here.

[0194] If either control node 1 or control node 2 fails, the normally functioning control node sends information 1 with version number 100 to configuration publishing node 1 and configuration publishing node 2. This process is the same as described above and is not repeated here. If both control node 1 and control node 2 fail, configuration publishing node 1 and configuration publishing node 2 wait until at least one of control node 1 and control node 2 resumes operation. The at least one control node that resumes operation sends information 1 with version number 100 to configuration publishing node 1 and configuration publishing node 2. This process is the same as described above and is not repeated here.

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

[0196] 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.

[0197] If configuration publishing node 1 fails, authoritative server 1 will not be able to receive information 1 with version number 100 during the time that configuration publishing node 1 fails. In this case, authoritative server 1 waits until configuration publishing node 1 resumes normal operation. After configuration publishing node 1 resumes normal operation, it 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.

[0198] The above description describes the process of configuring information 1 in a domain name configuration system, assuming that the system includes two network clusters, each containing two configuration gateway nodes, two control nodes, two configuration publishing nodes, and two authoritative servers. If the domain name configuration system includes more than two network clusters, each containing more than two configuration gateway nodes, control nodes, configuration publishing nodes, and authoritative servers, the above method can still be used to configure information.

[0199] In actual applications, when the domain name configuration system implements information configuration, the various nodes contained in the network cluster can transmit information in the one-to-one manner described above, or in a one-to-many manner (such as the one-to-two described in Figure 18). This application does not limit whether one-to-one or one-to-many information transmission is used.

[0200] The above text takes 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 relevant descriptions, please refer to the above and will not be repeated here. Taking information 2 including the correspondence between geographic location 1 and IP address segment 1, and geographic location 2 and IP address segment 2 as an example, according to the needs of actual application, 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.

[0201] The domain name configuration system shown in Figure 18 includes network cluster 1 and network cluster 2, which can be deployed in different geographical locations, such as network cluster 1 is deployed in location 1 and network cluster 2 is 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. When 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 domain name resolution efficiency. Location 1 and location 2 can refer to cities, provinces, districts, or geographical locations with the same or different areas at different longitudes and latitudes obtained by other division methods.

[0202] In some possible scenarios, the domain name configuration system may further include a health detection node. The following takes the domain name configuration system shown in FIG19 as an example. FIG19 is a schematic structural diagram of the third domain name configuration system provided by this application. The domain name configuration system shown in FIG19 differs from the domain name configuration system shown in FIG18 in that the domain name configuration system shown in FIG19 includes a health detection node 1 and a health detection node 2. Among them, health detection node 1 is connected to configuration gateway node 1 and control node 1 respectively, and health detection node 2 is connected to configuration gateway node 2 and control node 2 respectively.

[0203] Continuing with the domain name configuration system configuration information 1 shown in FIG19 as an example, the process of configuring a domain name configuration system including a health detection node will be described. The process of configuring the domain name configuration system including a health detection node, including the gateway node, control node, configuration publishing node, and authoritative server, is similar to the process of configuring the gateway node, control node, configuration publishing node, and authoritative server in the domain name configuration system shown in FIG18 , and will not be further described here. The process of configuring the health detection node is described in detail below.

[0204] The health detection node 1 receives the information 1 with version number 100 transmitted by the configuration gateway node 1, and resolves the information 1 with version number 100, and obtains 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 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 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, and will not be repeated here.

[0205] In the event that health detection node 1 fails, the domain name configuration system shown in FIG19 completes the configuration of information 1 with version number 100 using the same method as the domain name configuration system shown in FIG18 for configuring information 1 with version number 100. When authoritative server 1 receives a resolution request for domain name 1 from a client, authoritative server 1 determines the communication status of any one of the multiple IP addresses as the resolution result for domain name 1.

[0206] The above text describes the domain name configuration system provided by the present application in conjunction with Figures 3 to 19. 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. The following describes a domain name configuration device provided by the present application in conjunction with Figure 20. Figure 20 is a structural schematic diagram of a domain name configuration device provided by the present application, and the domain name configuration device is applied to the 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 release nodes, L authoritative servers, where M, N, I, J and L are all positive integers greater than or equal to 2.

[0207] As shown in Figure 20, a domain name configuration device 2000 includes a transceiver module 2010, applied to a first configuration gateway node included in a first network cluster, configured to receive domain name configuration information input by a user and send the domain name configuration information to H configuration gateway nodes in the domain name configuration system; and to send the domain name configuration information to K control nodes included in the first network cluster. 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, and the K control nodes are any K control nodes among 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, configured to send 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 transceiver module 2010 is also applied to the first control node included in the first network cluster, configured 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.

[0208] In one possible scenario, before the transceiver module 2010 sends domain name configuration information to any of the other configuration gateway nodes included in the domain name configuration system, if the first configuration gateway node fails, the transceiver module 2010 is further used in a second configuration gateway node to receive domain name configuration information input by a user and send the domain name configuration information to the K control nodes included in the network cluster in which it resides. The second configuration gateway node is any configuration gateway node in the system other than the first configuration gateway node. The K control nodes are any K control nodes included in the I control nodes included in the first network cluster. The transceiver module 2010 is further used in the first control node of the first network cluster to send 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 included in the J configuration publishing nodes included in the first network cluster. The transceiver module 2010 is further used in the first configuration publishing node of the first network cluster to send 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. The domain name configuration information includes: the correspondence between the domain name and the IP address.

[0209] 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.

[0210] In one possible scenario, after the transceiver module 2010 implemented in the first configuration gateway node sends domain name configuration information to all other configuration gateway nodes included in the domain name configuration system, if the first configuration gateway node fails, the transceiver module 2010 is further implemented in the second configuration gateway node to send the domain name configuration information to the K control nodes included in its network cluster. The second configuration gateway node is any configuration gateway node in the system other than the first configuration gateway node. The K control nodes are any K control nodes included in the I control nodes included in the first network cluster. The transceiver module 2010 is further implemented in the first control node to send 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 included in the J configuration publishing nodes included in the first network cluster. The transceiver module 2010 is further implemented in the first configuration publishing node to send 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. The domain name configuration information includes: the correspondence between the domain name and the IP address.

[0211] In one 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 release node and a processing module 2030 applied to the first configuration release 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. If the first applicable type and the second applicable type match, the processing module 2030 is applied to the first configuration release node to determine whether the second version number is updated compared to the first version number. If the second version number is updated, the transceiver module 2010 is applied to the first configuration release node to receive the domain name configuration information.

[0212] In one 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 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.

[0213] 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 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.

[0214] 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.

[0215] A more detailed description of the 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.

[0216] When the domain name configuration device implements the domain name configuration method shown in any of the aforementioned figures through software, the domain name configuration device and its various units may also be software modules. The 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.

[0217] For a more detailed description of the domain name configuration device, please refer to the relevant description of the embodiment shown in the aforementioned figures, and will not be repeated here. It should be understood that the domain name configuration device shown in the aforementioned figures is merely an example provided in this embodiment. Depending on the first object included in the first image, the domain name configuration device may include more or fewer modules, and this application is not limited to this.

[0218] When the domain name configuration device is implemented via hardware, the hardware may be implemented via a processor or a chip. The chip includes an interface circuit and a control circuit. The interface circuit is used to receive data from devices other than the processor and transmit it to the control circuit, or to transmit data from the control circuit to devices other than the processor.

[0219] The control circuit is used to implement any possible implementation method of 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.

[0220] Alternatively, the chip includes a processor and a power supply circuit, the power supply circuit being used to power the processor, and the processor being used to implement the domain name configuration method in the aforementioned embodiment. For example, the power supply circuit can be located within the same chip as the processor, or within a separate chip from the processor. 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.

[0221] Alternatively, when the domain name configuration device implements the domain name configuration shown in any of the aforementioned figures through hardware, the hardware can be a computing device. Figure 21 is a schematic structural diagram of a computing device provided by this application. As shown in Figure 21, 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.

[0222] When the computing device 2100 is used to implement the embodiments shown in Figures 3 to 19, the processor 2110, the communication interface 2120 and the memory 2130 can also cooperate to implement various operation steps in the configuration process of the information executed by each node in the network cluster.

[0223] The specific connection medium between the communication interface 2120, processor 2110, and memory 2130 is not limited in the embodiments of the present application. In Figure 21, the embodiment of the present application shows that the communication interface 2120, processor 2110, and memory 2130 are connected via a bus 2140. The bus is represented by a bold line in Figure 21. The connection method between other components is only for schematic illustration and is 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, only one bold line is used in Figure 21, but this does not mean that there is only one bus or one type of bus.

[0224] The memory 2130 can be used to store software programs and modules, such as the program instructions / modules corresponding to the information configuration method provided in the embodiments 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 can be used to communicate signaling or data with other devices. In this application, the computing device 2100 can have multiple communication interfaces 2120.

[0225] In a possible example, the above-mentioned memory 2130 can be, but is not limited to, 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 ROM, PROM, EPROM, EEPROM or flash memory. The volatile memory can be RAM, which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as SRAM, DRAM, synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM) and direct RAM bus random access memory (DR RAM). It is understood that the processor in the embodiments of the present application can be a CPU, or 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.

[0226] 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. For the sake of brevity, they will not be repeated here.

[0227] An embodiment of the present application also provides a computing device cluster. Figure 22 is a schematic diagram of the structure of a computing device cluster provided by the present application. As shown in Figure 22, 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 smartphone.

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

[0229] 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 can be used together to complete domain name configuration.

[0230] It should be noted that the memory 2130 in different computing devices 2100 in the computing device cluster can store different instructions, each for executing a portion of the functions of the domain name configuration apparatus. In other words, the instructions stored in the memory 2130 in different computing devices 2100 can implement the functions of one or more of the transceiver module, the processing module, and the storage module.

[0231] In some possible implementations, one or more computing devices in a computing device cluster may be connected via a network. The network may be a wide area network or a local area network, etc. FIG23 shows a possible implementation. FIG23 is a schematic diagram of a possible connection method of a computing device cluster provided by the present application. As shown in FIG23 , 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.

[0232] The connection method between the computing device clusters shown in Figure 23 can be based on the needs of the domain name configuration system provided by this application (such as sending and receiving large amounts of data), so it is considered to entrust the functions implemented by the transceiver module to the computing device 2100A for execution.

[0233] It should be understood that the functionality of the computing device 2100A shown in FIG23 may also be implemented by multiple computing devices 2100. Similarly, the functionality of the computing device 2100B may also be implemented by multiple computing devices 2100.

[0234] The present application also provides another computing device cluster. The connection relationship between the computing devices in this computing device cluster can be similar to the connection method of the computing device cluster described in Figures 22 and 23. However, the memory 2130 in one or more computing devices 2100 in this computing device cluster can store the same instructions for implementing the domain name configuration method.

[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 implementing the domain name configuration method. In other words, the combination of one or more computing devices 2100 can jointly execute the instructions for implementing the domain name configuration method.

[0236] 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. In other words, the instructions stored in the memory 2130 in different computing devices 2100 can implement the functions of one or more of the gateway configuration node, the control node, and the configuration publishing node.

[0237] 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 executed on a computing device or stored on any available medium. When executed on at least one computing device, the computer program product causes the at least one computing device to execute a domain name configuration method.

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

[0239] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in the present application, and such modifications or substitutions should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection 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 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.

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