Domain name management system, domain name registration and resolution method, device, equipment and medium

Abstract

The present invention discloses a domain name management system, a domain name registration and resolution method, an apparatus, a device and a medium. The domain name management system provided by the embodiment of the present invention includes: a routing domain and at least one domain name storage and resolution domain; the domain name storage and resolution domain includes: an alliance chain composed of multiple domain name storage and resolution nodes; the routing domain includes: an alliance chain composed of multiple routing nodes; the anchor node is a domain name storage and resolution node in the domain name storage and resolution domain connected to the routing node in the routing domain; each domain name storage and resolution domain and the routing domain perform information interaction through the anchor node and the routing node, realize the partitioning and storage of different top-level domain names and subdomain names in different domain name storage and resolution domains, and realize cross-domain interaction between different domain name storage and resolution domains through the routing domain, solve the problems of uneven computing resource allocation, domain name storage overload and chaotic domain name structure existing in a single public chain, optimize the resolution performance, and can meet the requirements of high-concurrency scenarios of DNS resolution requests.

Description

Technical Field

[0001] The present invention relates to the field of Internet technology, and in particular to a domain name management system, a domain name registration and resolution method, device, equipment and medium. Background Art

[0002] The Domain Name System (DNS) is a domain name resolution system widely used in the traditional Internet. It enables users to access the Internet more conveniently without having to remember the IP address of the machine. It is one of the most important public services in the traditional Internet.

[0003] The combination of blockchain technology and DNS system has changed the centralized storage mode of traditional DNS system to a certain extent, but it also brings some problems. At present, most decentralized DNS technologies use a single public chain as the underlying infrastructure. Since the domain name metadata information has reached the order of billions so far, the huge domain name metadata information requires a lot of storage resources. However, the existing single public chain has problems such as uneven distribution of computing resources, overload of domain name storage and chaotic domain name structure, and cannot standardize the management of domain names. Summary of the invention

[0004] The present invention provides a domain name management system, a domain name registration and resolution method, an apparatus, a device and a medium to solve the problems of uneven computing resource allocation, domain name storage overload and chaotic domain name structure in the decentralized DNS technology using a single public chain as the underlying infrastructure, improves the domain name resolution performance, can meet the needs of high-concurrency scenarios of DNS resolution requests, and facilitates standardized management of domain names.

[0005] According to one aspect of the present invention, there is provided a domain name management system, comprising: a routing domain and at least one domain name storage and resolution domain;

[0006] The domain name storage and resolution domain includes: a consortium chain composed of a plurality of domain name storage and resolution nodes, wherein the domain name storage and resolution nodes are used to store and resolve domain names;

[0007] The routing domain includes: a consortium chain composed of a plurality of routing nodes, wherein the routing nodes are used to store routing information of anchor nodes of the domain name storage and resolution domain; the anchor nodes are domain name storage and resolution nodes in the domain name storage and resolution domain connected to routing nodes in the routing domain;

[0008] The domain name storage and resolution domains and the routing domains exchange information through the anchor node and the routing node.

[0009] According to another aspect of the present invention, a domain name registration method is provided, which is applied to the request domain name storage and resolution domain in the domain name management system described in any embodiment, and the method comprises:

[0010] Receive a domain name registration request by requesting a domain name storage resolution node;

[0011] The domain name information to be registered contained in the domain name registration request is linked to the alliance chain of the target domain name storage and resolution domain through the request domain name storage and resolution node.

[0012] According to another aspect of the present invention, a domain name resolution method is provided, characterized in that it is applied to a domain name storage resolution domain in a domain name management system according to any embodiment, and the method comprises:

[0013] Receive the domain name resolution request by requesting the domain name storage resolution node;

[0014] If the requested domain name storage and resolution domain is the target domain name storage and resolution domain, accessing the requested domain name storage and resolution domain based on the domain name resolution request through the requested domain name storage and resolution node to obtain a resolution result of the domain name to be resolved;

[0015] If the requested domain name storage and resolution domain is not the target domain name storage and resolution domain, the domain name resolution request is forwarded to the routing domain through the requested domain name storage and resolution node, so that the routing domain accesses the target domain name storage and resolution domain based on the domain name resolution request to obtain the resolution result of the domain name to be resolved.

[0016] According to another aspect of the present invention, a domain name resolution method is provided, which is applied to a routing domain in a domain name management system according to any one of the embodiments, and the method comprises:

[0017] Receiving, by requesting a routing node, a cross-domain domain name resolution request sent by a request anchor node in a request domain name storage resolution domain, and determining a target domain name storage resolution domain based on querying routing information of the cross-domain domain name resolution request;

[0018] The cross-domain domain name resolution request is sent to the target domain name storage resolution domain through the request routing node, so that the target domain name storage resolution domain obtains the resolution result of the domain name to be resolved based on the cross-domain domain name resolution request query and returns it to the request routing node;

[0019] The resolution result of the domain name to be resolved is returned to the request anchor node through the request routing node.

[0020] According to another aspect of the present invention, a domain name registration device is provided, which is applied to the requested domain name storage and resolution domain in the domain name management system described in any embodiment, and the device includes:

[0021] A registration request receiving module, used to receive a domain name registration request by requesting a domain name storage resolution node;

[0022] The information chain module is used to chain the domain name information to be registered contained in the domain name registration request to the alliance chain of the target domain name storage and resolution domain through the request domain name storage and resolution node.

[0023] According to another aspect of the present invention, a domain name resolution device is provided, characterized in that it is applied to the domain name storage resolution domain in the domain name management system described in any embodiment, and the device includes:

[0024] A resolution request receiving module, used to receive a domain name resolution request by requesting a domain name storage resolution node;

[0025] A first resolution module, configured to, if the requested domain name storage resolution domain is a target domain name storage resolution domain, access the requested domain name storage resolution domain based on the domain name resolution request through the requested domain name storage resolution node to obtain a resolution result of the domain name to be resolved;

[0026] The second resolution module is used to forward the domain name resolution request to the routing domain through the request domain name storage resolution node if the request domain name storage resolution domain is not the target domain name storage resolution domain, so that the routing domain accesses the target domain name storage resolution domain based on the domain name resolution request to obtain the resolution result of the domain name to be resolved.

[0027] According to another aspect of the present invention, a domain name resolution device is provided, characterized in that it is applied to a routing domain in a domain name management system according to any embodiment, and the device comprises:

[0028] A resolution request determination module is used to receive a cross-domain domain name resolution request sent by a request anchor node in a request domain name storage resolution domain through a request routing node, and determine a target domain name storage resolution domain based on the cross-domain domain name resolution request query routing information;

[0029] A resolution request sending module, used for sending the cross-domain domain name resolution request to the target domain name storage resolution domain through the request routing node, so that the target domain name storage resolution domain obtains the resolution result of the domain name to be resolved based on the cross-domain domain name resolution request query and returns it to the request routing node;

[0030] The resolution result sending module is used to return the resolution result of the domain name to be resolved to the request anchor node by requesting the routing node.

[0031] According to another aspect of the present invention, a terminal device is provided, the terminal device comprising:

[0032] at least one processor; and

[0033] a memory communicatively connected to the at least one processor; wherein,

[0034] The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the domain name registration method and / or domain name resolution method described in any embodiment of the present invention.

[0035] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the domain name registration method and / or domain name resolution method described in any embodiment of the present invention when executed.

[0036] The domain name management system provided by the embodiment of the present invention includes: a routing domain and at least one domain name storage and resolution domain; the domain name storage and resolution domain includes: an alliance chain composed of multiple domain name storage and resolution nodes, and the domain name storage and resolution nodes are used to store and resolve domain names; the routing domain includes: an alliance chain composed of multiple routing nodes, and the routing nodes are used to store routing information of anchor nodes of the domain name storage and resolution domain; the anchor node is a domain name storage and resolution node in the domain name storage and resolution domain connected to the routing node in the routing domain; each domain name storage and resolution domain and the routing domain perform information interaction through the anchor node and the routing node, so as to realize the partitioning and storage of different top-level domain names and subdomain names in different domain name storage and resolution domains, and realize cross-domain interaction between different domain name storage and resolution domains through the routing domain, and compared with the decentralized DNS technology using a single public chain as the underlying infrastructure, the problems of uneven computing resource allocation, domain name storage overload and chaotic domain name structure existing in a single public chain are solved, the resolution performance is optimized, the requirements of high-concurrency scenarios of DNS resolution requests can be met, and standardized management of domain names is facilitated.

[0037] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0039] Figure 1 is a system architecture diagram of a domain name management system provided according to Embodiment 1 of the present invention;

[0040] Figure 2 is a schematic diagram of a storage method of routing information provided according to Embodiment 1 of the present invention;

[0041] Figure 3A This is a system architecture diagram of a domain name management system provided according to Embodiment 2 of the present invention;

[0042] Figure 3B is a system architecture diagram of another domain name management system provided according to Embodiment 2 of the present invention;

[0043] Figure 4 is a flowchart of a domain name registration method provided according to Embodiment 3 of the present invention;

[0044] Figure 5 is a flowchart of a domain name resolution method provided according to Embodiment 4 of the present invention;

[0045] Figure 6 is a flowchart of a domain name resolution method provided according to Embodiment 5 of the present invention;

[0046] Figure 7 is a flowchart of a domain name resolution method provided according to Embodiment 6 of the present invention;

[0047] Figure 8 is a structural diagram of a domain name registration device provided according to Embodiment 7 of the present invention;

[0048] Fig. 9 is a structural diagram of a domain name resolution device provided according to Embodiment 8 of the present invention;

[0049] Fig.10 is a schematic diagram of the structure of a domain name resolution device provided according to Embodiment 9 of the present invention;

[0050] Fig.11 It is a schematic diagram of the structure of a terminal device for implementing the domain name registration method and / or domain name resolution method of an embodiment of the present invention. DETAILED DESCRIPTION

[0051] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0052] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0053] Embodiment 1

[0054] Figure 1 A system architecture diagram of a domain name management system is provided for the first embodiment of the present invention. This embodiment is applicable to the case of partition management of domain names. Figure 1 As shown, the domain name management system includes: a routing domain 20 and at least one domain name storage and resolution domain 100; the domain name storage and resolution domain 100 includes: an alliance chain composed of multiple domain name storage and resolution nodes 101, and the domain name storage and resolution node 101 is used to store and resolve domain names; the routing domain 200 includes: an alliance chain composed of multiple routing nodes 201, and the routing node 201 is used to store routing information of the anchor node 102 of the domain name storage and resolution domain; the anchor node 102 is a domain name storage and resolution node 101 in the domain name storage and resolution domain 100 connected to the routing node 201 in the routing domain 200; each of the domain name storage and resolution domains 100 and the routing domain 200 exchanges information through the anchor node 102 and the routing node 201.

[0055] Among them, the domain name storage and resolution domain 10 can be understood as a blockchain for providing domain name storage and resolution, and the domain name storage and resolution domain 100 can include: a consortium chain composed of multiple domain name storage and resolution nodes 101. The multiple domain name storage and resolution nodes 101 include at least one anchor node 102. The anchor node 102 can be understood as a domain name storage and resolution node in the domain name storage and resolution domain that is connected to the routing node in the routing domain. The role of the anchor node is to realize information interaction between the domain name storage and resolution node and the routing domain. The number of anchor nodes can be one or more, and each anchor node in the same domain name storage and resolution domain can be connected to one or more routing nodes in the routing domain.

[0056] The routing domain 200 can be understood as a blockchain for storing routing information of the domain name storage and resolution nodes connected to each domain name storage and resolution domain 100, and is used to realize information interaction between each domain name storage and resolution domain. The routing domain 200 may include: a consortium chain composed of multiple routing nodes 201, and the routing node 201 is used to store the routing information of the domain name storage and resolution nodes connected to the domain name storage and resolution domain, and the routing information is shared between multiple routing nodes.

[0057] Specifically, the domain name storage and resolution node 101 is a blockchain node in the alliance chain. As a core service node for domain name resolution, domain name registration, update, cancellation and resolution can be performed through a client (such as a browser) set on the domain name storage and resolution node. The routing domain 20 serves as an intermediate bridge for cross-domain domain name resolution between different domain name storage and resolution domains 100. It can receive a domain name resolution request sent by a domain name storage and resolution node 101 in a domain name storage and resolution domain 100, locate the domain name storage and resolution domain that actually stores the requested domain name, and forward the domain name resolution request to achieve a response to the cross-domain domain name resolution request.

[0058] The principle of realizing information interaction between different domain name storage and resolution domains 100 through routing domain 20 can be as follows: by connecting anchor node 102 in domain name storage and resolution domain 100 with routing node 201 in routing domain 200, and registering anchor node routing information corresponding to anchor node 102 in routing node 201 connected to anchor node 102, information interaction between each domain name storage and resolution node 101 in each domain name storage and resolution domain 100 and routing node 201 in routing domain 200 can be realized, and multiple domain name storage and resolution domains are located through anchor node routing information stored in routing domain, thereby realizing cross-domain domain name resolution and cross-domain resolution interaction between multiple domain name storage and resolution domains.

[0059] Exemplarily, the anchor node can be determined by the domain name storage and resolution nodes in the domain name storage and resolution domain jointly electing an anchor node. The election rule can be that during the election, nodes can vote based on the order of joining the domain name storage and resolution nodes and the amount of domain name information stored. If the number of votes for a domain name storage and resolution node is more than half of the total number of nodes in the current domain name storage and resolution domain, the domain name storage and resolution node becomes the anchor node. After the election is completed, the anchor node can register its own information in the routing domain for communication with the routing domain. The anchor node can also be determined by receiving the anchor node selected by the user from each domain name storage and resolution node in the domain name storage and resolution domain.

[0060] Exemplarily, each domain name storage resolution domain 100 and routing domain 200 may be a Fabric HyperLedger consortium chain that networks blockchain nodes, and the topological structure of the network may be a ring structure.

[0061] It should be noted that the embodiment of the present invention designs different alliance chains for different top-level domain names. Since the storage capacity of a chain may be limited, it also supports the expansion of the storage and resolution domain of the domain name in the same system, that is, multiple chains exist in the same system and can interact.

[0062] The domain name management system provided by the embodiment of the present invention includes: a routing domain and at least one domain name storage and resolution domain; the domain name storage and resolution domain includes: an alliance chain composed of multiple domain name storage and resolution nodes, and the domain name storage and resolution nodes are used to store and resolve domain names; the routing domain includes: an alliance chain composed of multiple routing nodes, and the routing nodes are used to store routing information of anchor nodes of the domain name storage and resolution domain; the anchor node is a domain name storage and resolution node in the domain name storage and resolution domain connected to the routing node in the routing domain; each domain name storage and resolution domain and the routing domain perform information interaction through the anchor node and the routing node, so as to realize the partitioning and storage of different top-level domain names and subdomain names in different domain name storage and resolution domains, and realize cross-domain interaction between different domain name storage and resolution domains through the routing domain, and compared with the decentralized DNS technology using a single public chain as the underlying infrastructure, the problems of uneven computing resource allocation, domain name storage overload and chaotic domain name structure existing in a single public chain are solved, the resolution performance is optimized, the requirements of high-concurrency scenarios of DNS resolution requests can be met, and standardized management of domain names is facilitated.

[0063] Optionally, the routing table of each domain name storage and resolution node in the domain name storage and resolution domain stores routing information of the domain name storage and resolution nodes with a preset interval span in the alliance chain of the domain name storage and resolution domain.

[0064] Specifically, in order to further improve the load balancing of the domain name resolution process in high-concurrency scenarios, this embodiment adopts an efficient routing strategy based on the Chord algorithm. Figure 2 As shown, the logic of the Chord algorithm is to store a routing table in each domain name storage and resolution node in the network, which stores the routing information of the domain name storage and resolution node with a preset interval span. The routing table may include: domain name storage and resolution node ID, resource ID, and the starting and ending points of the routing information storage interval.

[0065] Exemplarily, the preset interval span may be half the number of domain name storage and resolution nodes in the domain name storage and resolution domain, such as Figure 2As shown, the routing table of the domain name storage and resolution node N0 stores routing information of N0 to N20, and the routing table of the domain name storage and resolution node N1 stores routing information of N1 to N21. When a domain name storage and resolution node receives a domain name resolution request, if the routing table can locate the location of the target domain name storage and resolution node where the requested domain name is located, the domain name resolution request is sent to the target domain name storage and resolution node for response. If the domain name storage and resolution node that receives the domain name resolution request cannot respond to the domain name resolution request, the domain name resolution request is forwarded to the domain name storage and resolution node farthest from the node in the routing table to continue searching, such as Figure 2 As shown, if the domain name storage and resolution node that receives the domain name resolution request is N0, it is forwarded to the domain name storage and resolution N20. Since the search process is similar to a binary search, the efficiency of data routing and positioning is improved.

[0066] Optionally, different domain name storage and resolution domains are used to store different top-level domain names and subdomain names under the top-level domain names.

[0067] Exemplarily, different domain name storage and resolution domains can be used to store different top-level domain names and all subdomain names under the top-level domain names, as well as metadata information of each domain name. Figure 1 The four domain name storage and resolution domains shown are: domain name storage and resolution domain A is used to store the top-level domain name ".com" and its subdomain names "baidu.com" and "123.baidu.com" etc.; domain name storage and resolution domain B is used to store the top-level domain name ".cn" and its subdomain names; domain name storage and resolution domain C is used to store the top-level domain name ".gov" and its subdomain names; domain name storage and resolution domain A is used to store the top-level domain name ".net" and its subdomain names.

[0068] Embodiment 2

[0069] Figure 3A A system architecture diagram of a domain name management system is provided for the second embodiment of the present invention. This embodiment is applicable to the situation where domain names are managed in partitions. Figure 3A As shown, the domain name management system includes:

[0070] A routing domain 20 and at least one domain name storage and resolution domain 100; the domain name storage and resolution domain 100 includes: a consortium chain composed of multiple domain name storage and resolution nodes 101, and the domain name storage and resolution node 101 is used to store and resolve domain names; the routing domain 200 includes: a consortium chain composed of multiple routing nodes 201, and the routing node 201 is used to store routing information of the anchor node 102 of the domain name storage and resolution domain; the anchor node 102 is a domain name storage and resolution node 101 in the domain name storage and resolution domain 10 connected to the routing node 201 in the routing domain 200; each of the domain name storage and resolution domains 100 and the routing domain 200 performs information exchange through the anchor node 102 and the routing node 201;

[0071] The domain name storage and resolution domain 100 includes: a request domain name storage and resolution domain 110 and a target domain name storage and resolution domain 120; the request domain name storage and resolution domain 110 is the domain name storage and resolution to which the request domain name storage and resolution node 111 that receives the domain name request belongs; the target domain name storage and resolution domain 120 is the domain name storage and resolution to which the target domain name storage and resolution node 121 requested by the domain name request belongs; wherein, the request domain name storage and resolution domain 110 and the target domain name storage and resolution domain 120 are the same domain name storage and resolution domain, or two different domain name storage and resolution domains.

[0072] The requesting domain name storage resolution node 111 can be understood as a domain name storage resolution node that receives a domain name request initiated by a user, and the domain name storage resolution domain to which the requesting domain name storage resolution node 111 belongs is the requesting domain name resolution domain 110. The requesting domain name storage resolution node 111 can be a domain name storage resolution node that is closest to the user and is accessed via the RestFul API.

[0073] The target domain name storage and resolution node 121 can be understood as the domain name storage and resolution node requested by the domain name request, and the domain name storage and resolution domain to which the target domain name storage and resolution node 121 belongs is the target domain name resolution domain 120 .

[0074] It should be noted that the requesting domain name storage resolution domain 110 and the target domain name storage resolution domain 120 can be the same two domain name storage resolution domains, or can be two different domain name storage resolution domains. The requesting domain name storage resolution domain and the target domain name storage resolution domain can be the same two domain name storage resolution domains, that is, the requesting domain name storage resolution node and the target domain name storage resolution node belong to the same domain name storage resolution domain. It can be understood that the requesting domain name storage resolution node and the target domain name storage resolution node can also be the same domain name storage resolution node, or two different domain name storage resolution nodes.

[0075] In a specific example, if the request domain name storage resolution domain and the target domain name storage resolution domain are the same domain name storage resolution domain, such as Figure 1 The domain name storage and resolution domain A shown can receive the domain name request through the requesting domain name storage and resolution node in the domain name storage and resolution domain A, and respond to the domain name request through the target domain name storage and resolution node and / or the routing domain in the domain name storage and resolution domain A.

[0076] In another specific example, if the request domain name storage resolution domain and the target domain name storage resolution domain are two different domain name storage resolution domains, such as Figure 1 The request domain name storage resolution domain A and the target domain name storage resolution domain C shown in the figure can receive the domain name request through the request domain name storage resolution node in the request domain name storage resolution domain A, and forward the domain name request to the target domain name storage resolution node in the target domain name storage resolution domain C through the routing domain to respond to the domain name request.

[0077] Optionally, the multiple routing nodes 201 of the routing domain include: a request routing node 211 and a target routing node 221;

[0078] The request routing node 211 is connected to the request anchor node 112 of the request domain name storage resolution domain;

[0079] The target routing node 221 is connected to the target anchor node 122 of the target domain name storage resolution domain;

[0080] The request routing node 211 and the target routing node 221 are the same routing node or two different routing nodes.

[0081] Among them, the request anchor node 112 can be understood as an anchor node in the request domain name storage and resolution domain, and the target anchor node 122 can be understood as an anchor node in the target domain name storage and resolution domain. It can be understood that the request anchor node 112 and the request domain name storage and resolution node 111 are both domain name storage and resolution nodes in the request domain name storage and resolution domain. Therefore, the request anchor node 112 and the request domain name storage and resolution node 111 can be the same domain name storage and resolution node, or two different domain name storage and resolution nodes.

[0082] The request routing node 211 can be understood as a routing node in the routing domain connected to the request anchor node 112 of the request domain name storage and resolution domain 110; the target routing node 221 can be understood as a routing node in the routing domain connected to the target anchor node 122 of the target domain name storage and resolution domain 120. Two different domain name storage and resolution domains can be connected to the same routing node in the routing domain, such as Figure 1 The domain name storage resolution domain A and the domain name storage resolution domain B shown in FIG. 2 ; two different domain name storage resolution domains can also be connected to two different routing nodes in the routing domain, such as Figure 1 The domain name storage resolution domain B and the domain name storage resolution domain C are shown in .

[0083] Specifically, the requesting domain name storage and resolution domain exchanges information with the routing domain through the requesting anchor node and the requesting routing node in the routing domain, and the target domain name storage and resolution domain exchanges information with the routing domain through the target anchor node and the target routing node in the routing domain. If the requesting routing node and the target routing node are the same routing node, the routing node can realize the information exchange between the requesting domain name storage and resolution domain and the target domain name storage and resolution domain; if the requesting routing node and the target routing node are two different routing nodes, the requesting routing node and the target routing node can exchange information, so that the requesting domain name storage and resolution domain and the target domain name storage and resolution domain can exchange information.

[0084] For example, Figure 3A or Figure 3B As shown, if the requesting domain name storage resolution node is a domain name storage resolution node in domain name storage resolution domain A, and the target domain name storage resolution node is a domain name storage resolution node in domain name storage resolution domain C, then the target domain name storage resolution domain is domain name storage resolution domain C, then the requesting domain name storage resolution node and the target domain name storage resolution node can realize the interaction between the requesting domain name storage resolution node in the requesting domain name storage resolution domain A and the target domain name storage resolution node in the target domain name storage resolution domain C through the requesting anchor node in the domain name storage resolution domain A and the requesting routing node connected to the requesting anchor node, the target anchor node in the domain name storage resolution domain C and the target routing node connected to the target anchor node.

[0085] Optionally, the domain name storage and resolution node is used for at least one of the following:

[0086] Acting as the requested domain name storage and resolution node 111, receiving the domain name request;

[0087] Acting as the target domain name storage resolution node 121, responding to the domain name request;

[0088] Acting as the request anchor node 112, forwarding the domain name request to the request routing node;

[0089] As the target anchor node 122, it receives the domain name request sent by the target routing node, and forwards it to the domain name storage and resolution node in the target domain name storage and resolution domain.

[0090] Specifically, the roles and responsibilities of the domain name storage and resolution nodes in the domain name storage and resolution domain are different in different scenarios. As a requesting domain name storage and resolution node, it can receive domain name requests; as a target domain name storage and resolution node, it can respond to domain name requests; as a requesting anchor node, it can forward the received domain name requests to the requesting routing node; as a target anchor node, it can forward the domain name requests to the domain name storage and resolution nodes in the domain name storage and resolution.

[0091] It should be noted that a domain name storage and resolution node in the requesting domain name storage and resolution domain can simultaneously serve as a requesting domain name storage and resolution node and a requesting anchor node, receive domain name requests, and forward domain name requests to the requesting routing node. A domain name storage and resolution node in the target domain name storage and resolution domain can simultaneously serve as a target domain name storage and resolution node and a target anchor node, receive domain name requests sent by the target routing node and respond to the domain name requests.

[0092] Optionally, the routing node is used for at least one of the following:

[0093] Acting as a request routing node 211, receiving the domain name request forwarded by the request anchor node 112;

[0094] As the target routing node 221 , the domain name request is forwarded to the target anchor node 122 .

[0095] Specifically, the roles and responsibilities of routing nodes in a routing domain may be different in different scenarios. As a request routing node, it receives domain name requests forwarded by request anchor nodes in the request domain name storage and resolution domain; as a target routing node, it forwards domain name requests to target anchor nodes in the target domain name storage and resolution domain.

[0096] It should be noted that a routing node in a routing domain can also serve as a request routing node and a target routing node at the same time, receiving a domain name request sent by a request anchor node in a request domain name storage and resolution domain, and forwarding the domain name request to a target anchor node in a target domain name storage and resolution domain.

[0097] Optionally, the domain name request includes: a domain name registration request, a domain name update request, a domain name cancellation request and a domain name resolution request.

[0098] Specifically, the domain name request received by the requesting domain name storage and resolution node in the requesting domain name storage and resolution domain may include: a domain name registration request, a domain name update request, a domain name cancellation request, and a domain name resolution request. A domain name registration request refers to a request indicating the registration of a domain name, a domain name update request refers to a request indicating the update of domain name information, a domain name cancellation request refers to a request containing cancellation domain name information, and a domain name resolution request refers to a request for resolving a domain name.

[0099] For example, domain name registration request, domain name update request and domain name cancellation request can implement business logic through smart contracts.

[0100] Embodiment 3

[0101] Figure 4 A flowchart of a domain name registration method is provided for the third embodiment of the present invention. This embodiment is applicable to the case of registering a domain name in a domain name storage and resolution domain. The method can be executed by a domain name registration device. The domain name registration device can be implemented in the form of hardware and / or software. The domain name registration device can be configured in a terminal device. Figure 4 As shown, the method includes:

[0102] S310: Receive a domain name registration request by requesting a domain name storage resolution node.

[0103] The domain name registration request refers to a request containing the registration domain name information, and the domain name registration request may include the domain name information to be registered, such as the type, name and resource record of the domain name to be registered.

[0104] Specifically, a client is set on a domain name storage and resolution node of a domain name storage and resolution domain, and the client can be used to obtain a domain name registration request initiated by a user. The domain name storage and resolution node where the client that receives the domain name registration request is located is determined as the requesting domain name storage and resolution node.

[0105] S320: Upload the domain name information to be registered included in the domain name registration request to the alliance chain of the target domain name storage and resolution domain through the request domain name storage and resolution node.

[0106] Specifically, after receiving the domain name registration request, the requesting domain name storage and resolution node on the domain name storage and resolution domain links the domain name information to be registered to the alliance chain of the target domain name storage and resolution domain in the domain name management system based on the name of the domain name to be registered contained in the domain name registration request.

[0107] When a user logs in to the domain name management system for the first time, he needs to register a user account with user authorization. After successful registration and login, he can initiate a domain name request in the domain name management system. For the domain name registration process, there may already be a target domain name storage and resolution domain in the domain name management system that can store the domain name to be registered corresponding to the domain name registration request, and the domain name to be registered information can be linked to the alliance chain of the target domain name storage and resolution domain. It is also possible that there is no target domain name storage and resolution domain in the domain name management system that can store the domain name to be registered corresponding to the domain name registration request. Therefore, it may be necessary to first create a target domain name storage and resolution domain in the domain name management system that can store the domain name to be registered corresponding to the domain name registration request, and then link the domain name to be registered information to the alliance chain of the target domain name storage and resolution domain.

[0108] In this embodiment, since different domain name storage and resolution domains are used to store different top-level domain names and subdomain names under the top-level domain names, by using different alliance chains based on domain names to perform chain registration and storage of domain names, it is possible to solve the problems of uneven distribution of computing resources, overload of domain name storage, and chaotic domain name structure in the decentralized DNS technology that uses a single public chain as the underlying infrastructure.

[0109] The technical solution of the embodiment of the present invention receives a domain name registration request by requesting a domain name storage and resolution node; links the domain name information to be registered contained in the domain name registration request to the alliance chain of the target domain name storage and resolution domain through the requesting domain name storage and resolution node; can realize domain name registration in the domain name management system, so that the domain name information to be registered is linked to the alliance chain of the target domain name storage and resolution domain in the domain name management system, and different alliance chains are used to perform chain registration and storage of domain names based on domain names, thereby solving the problems of uneven computing resource allocation, domain name storage overload and chaotic domain name structure in the decentralized DNS technology that uses a single public chain as the underlying infrastructure in the prior art.

[0110] Optionally, the domain name information to be registered included in the domain name registration request is linked to the alliance chain of the target domain name storage and resolution domain through the request domain name storage and resolution node, including:

[0111] If the type of the domain name to be registered is a top-level domain name, the name and resource record of the domain name to be registered are chained to the alliance chain of the target domain name storage and resolution domain through the requesting domain name storage and resolution node;

[0112] If the type of the domain name to be registered is a non-top-level domain name, and the top-level domain name of the domain name to be registered exists in the target domain name storage and resolution domain, then the name and resource records of the domain name to be registered are linked to the alliance chain of the target domain name storage and resolution domain through the requesting domain name storage and resolution node;

[0113] The alliance chain of the target domain name storage resolution domain is established according to the domain name information to be registered.

[0114] Specifically, establishing a consortium chain of a domain name storage and resolution domain according to the domain name information to be registered, and uplinking the domain name information to be registered included in the domain name registration request to the consortium chain of a target domain name storage and resolution domain includes the following two situations:

[0115] In the first case, if the type of domain name to be registered contained in the domain name registration request received by the requesting domain name storage and resolution node is a top-level domain name, a consortium chain of the domain name storage and resolution domain is established based on the information of the domain name to be registered, and then the name and resource records of the domain name to be registered are linked to the consortium chain of the target domain name storage and resolution domain through the requesting domain name storage and resolution node.

[0116] In the second case, if the type of the domain name to be registered contained in the domain name registration request received by the requesting domain name storage and resolution node is a non-top-level domain name, it is determined whether the top-level domain name of the domain name to be registered exists in the domain name management system based on the information of the domain name to be registered; if so, the domain name storage and resolution domain stored in the top-level domain name of the domain name to be registered is determined as the target domain name storage and resolution domain, and the name and resource records of the domain name to be registered are linked to the alliance chain of the target domain name storage and resolution domain; if not, the user is prompted that the top-level domain name does not exist, and please register the top-level domain name first, and establish the alliance chain of the target domain name storage and resolution domain based on the top-level domain name information, and then link the name and resource records of the top-level domain name to be registered to the alliance chain of the target domain name storage and resolution domain by requesting the domain name storage and resolution node.

[0117] Exemplarily, a method for establishing a consortium chain for the target domain name storage and resolution domain based on the domain name information to be registered may be to establish a consortium chain for the target domain name storage and resolution domain based on the number of chain nodes, anchor node selection, identification storage and resolution node location, node memory and disk size, and configure consortium chain parameters for the target domain name storage and resolution domain. This process may also require review by an auditor.

[0118] Optionally, after uploading the domain name information to be registered included in the domain name registration request to the alliance chain of the target domain name storage and resolution domain, the method further includes:

[0119] Through the target anchor node, the routing information of the target anchor node is uploaded to the alliance chain of the routing domain.

[0120] The target anchor node routing information includes: the anchor node's IP, port number and routing information of each domain name storage resolution node in the target domain name storage resolution domain. The routing information of the domain name storage resolution node may include the domain name, domain name storage resolution node ID and resource ID.

[0121] Specifically, after the domain name information to be registered included in the domain name registration request is linked to the alliance chain of the target domain name storage and resolution domain, the domain name information stored in the target domain name storage and resolution domain changes, and thus the target anchor node routing information corresponding to the target anchor node in the target domain name storage and resolution domain also changes accordingly. Therefore, through the target anchor node, the target anchor node routing information is linked to the alliance chain of the routing domain, so that the anchor node routing information stored in the routing domain is synchronously updated and kept consistent with the anchor node routing information of each domain name storage and resolution domain.

[0122] Optionally, uplinking the target anchor node routing information to the consortium chain of the routing domain through the target anchor node includes:

[0123] Through the target anchor node, a key-value pair consisting of the domain name to be registered stored in the target domain name storage resolution domain and the routing information of the target anchor node is linked to the alliance chain of the routing domain;

[0124] The target anchor node routing information includes: an Internet Protocol IP address and a port number of the requesting anchor node.

[0125] Specifically, in the process of uplinking the target anchor node routing information to the alliance chain of the routing domain, the target anchor node forms a key-value pair based on the domain name to be registered and the routing information of the target anchor node, and uplinks the target anchor node routing information to the routing node connected to the target anchor node in the routing domain in the form of a key-value pair.

[0126] In one embodiment, a domain name cancellation request is received through the request domain name storage resolution node;

[0127] The domain name storage and resolution node for requesting the domain name is used to review the domain name information to be cancelled contained in the domain name cancellation request, and determine whether the domain name is allowed to be cancelled;

[0128] The domain name cancellation request is sent to the target domain name storage and resolution node through the requesting domain name storage and resolution node, so that the domain name allowed to be cancelled stored in the target domain name storage and resolution node is deleted.

[0129] Specifically, the requesting domain name storage and resolution node in the requesting domain name storage and resolution domain receives a domain name cancellation request initiated by a user, reviews the domain name information to be cancelled contained in the domain name cancellation request to determine whether the domain name to be cancelled is allowed to be cancelled, and determines the domain name to be cancelled that is allowed to be cancelled as the domain name to be cancelled, for example, prohibiting cancellation of the top-level domain name and the second-level domain name. The domain name cancellation request is sent to the target domain name storage and resolution domain, so that the domain name allowed to be cancelled stored in the target domain name storage and resolution domain is deleted.

[0130] Exemplarily, the method of sending the domain name cancellation request to the target domain name storage and resolution domain may be: if the request domain name storage and resolution domain receiving the domain name cancellation request and the target domain name storage and resolution domain are the same domain name storage and resolution domain, the domain name cancellation request is sent to the target domain name storage and resolution node in the domain, so that the target domain name storage and resolution node deletes the stored domain name that is allowed to be cancelled based on the domain name information to be cancelled included in the domain name cancellation request. If the request domain name storage and resolution domain receiving the domain name cancellation request and the target domain name storage and resolution domain are not the same domain name storage and resolution domain, the domain name cancellation request is sent to the target anchor node of the target domain name storage and resolution domain through the routing domain, and the domain name cancellation request is sent to the target domain name storage and resolution node of the target domain name storage and resolution domain through the target anchor node, so that the target domain name storage and resolution node deletes the stored domain name that is allowed to be cancelled based on the domain name information to be cancelled included in the domain name cancellation request.

[0131] In one embodiment, the method further comprises:

[0132] Receiving a domain name update request through the request domain name storage resolution node;

[0133] The domain name information to be updated contained in the domain name update request is linked to the alliance chain of the domain name storage and resolution domain through the requesting domain name storage and resolution node, so as to update the domain name information stored in each of the domain name storage and resolution nodes in the domain name storage and resolution domain;

[0134] The anchor node routing update information is uploaded to the alliance chain of the routing domain through the anchor node to update the anchor node routing information stored in the routing nodes in the routing domain.

[0135] Specifically, the process of uplinking the domain name information to be updated contained in the domain name update request to the alliance chain of the domain name storage and resolution domain is basically the same as the process of uplinking the domain name information to be cancelled in the domain name cancellation request, and the embodiment of the present invention will not elaborate on this. After uplinking the domain name information to be updated contained in the domain name update request to the alliance chain of the domain name storage and resolution domain, the target domain name storage and resolution node updates the domain name information of the stored domain name to be updated based on the domain name information to be updated contained in the domain name update request.

[0136] After the domain name information stored in the target domain name storage and resolution node is updated, the routing information of the requesting anchor node or the target anchor node may be updated accordingly, and the routing information after the anchor node is updated is determined as the anchor node routing update information, and the anchor node routing update information is linked to the alliance chain of the routing domain, and the anchor node routing information stored in the routing node to which the anchor node is connected in the routing domain is updated.

[0137] Embodiment 4

[0138] Figure 5 This is a flowchart of a domain name resolution method provided by the fourth embodiment of the present invention. This embodiment is applicable to the case where a domain name is resolved through a domain name storage resolution domain in a domain name management system. The method can be executed by a domain name resolution device, which can be implemented in the form of hardware and / or software, and can be configured in a terminal device. Figure 5 As shown, the method includes:

[0139] S410: Receive a domain name resolution request by requesting a domain name storage resolution node.

[0140] The domain name resolution request may be understood as a resolution request initiated by a user at a client disposed on a node storing and resolving a requested domain name. The domain name resolution request may include: routing information of the domain name to be resolved, such as the name and ID of the domain name to be resolved.

[0141] S420: If the requested domain name storage and resolution domain is the target domain name storage and resolution domain, access the requested domain name storage and resolution domain based on the domain name resolution request through the requested domain name storage and resolution node to obtain a resolution result of the domain name to be resolved.

[0142] Specifically, the domain name to be resolved corresponding to the received domain name resolution request may be stored in the requested domain name storage resolution domain to which the requested domain name storage resolution node belongs, or may exist in other domain name storage resolution domains, that is, the target domain name storage resolution domain may be the requested domain name storage resolution domain, or may be other domain name storage resolution domains. If the requested domain name storage resolution domain is the target domain name storage resolution domain, then based on the domain name resolution request, the target domain name storage resolution node where the domain name to be resolved is stored is located in the requested domain name storage resolution domain, and the target domain name storage resolution node is accessed to obtain the resolution result of the domain name to be resolved, without cross-domain access to other domain name storage resolution domains.

[0143] Exemplarily, based on the domain name resolution request, the method of searching in the requested domain name storage resolution domain to determine the target domain name storage resolution node where the domain name to be resolved is to traverse and access each domain name storage resolution node in the requested domain name storage resolution domain starting from the requested domain name storage resolution node until the target domain name storage resolution node is accessed to obtain the resolution result of the domain name to be resolved; or it can be searched based on certain rules, such as using a binary search method to access the target domain name storage resolution node to obtain the resolution result of the domain name to be resolved.

[0144] S430: If the requested domain name storage and resolution domain is not the target domain name storage and resolution domain, the domain name resolution request is forwarded to the routing domain through the requested domain name storage and resolution node, so that the routing domain accesses the target domain name storage and resolution domain based on the domain name resolution request to obtain a resolution result of the domain name to be resolved.

[0145] Specifically, if the requested domain name storage resolution domain is not the target domain name storage resolution domain, that is, the target domain name storage resolution node cannot be located in the requested domain name storage resolution domain, and thus the target domain name storage resolution node cannot be accessed to obtain the resolution result of the domain name to be resolved. Therefore, it is necessary to forward the domain name resolution request to the routing domain through the requested domain name storage resolution node, and send the domain name resolution request to the target domain name storage resolution domain to which the target domain name storage resolution node belongs through the routing node in the routing domain, locate and access the target domain name storage resolution node in the target domain name storage resolution domain to obtain the resolution result of the domain name to be resolved, thereby realizing cross-domain resolution between different domain name storage resolution domains, optimizing the resolution performance, and being able to meet the requirements of high concurrency scenarios for DNS resolution requests.

[0146] The technical solution of the embodiment of the present invention receives a domain name resolution request by requesting a domain name storage resolution node; if the requested domain name storage resolution domain is a target domain name storage resolution domain, the requested domain name storage resolution domain is accessed through the requested domain name storage resolution node based on the domain name resolution request to obtain a resolution result of the domain name to be resolved; if the requested domain name storage resolution domain is not the target domain name storage resolution domain, the requested domain name storage resolution node forwards the domain name resolution request to a routing domain, so that the routing domain accesses the target domain name storage resolution domain based on the domain name resolution request to obtain a resolution result of the domain name to be resolved, thereby solving the problems of uneven computing resource allocation, domain name storage overload and domain name structure confusion in the decentralized DNS technology that uses a single public chain as the underlying infrastructure in the prior art, optimizing the resolution performance, and realizing load balancing of the domain name resolution process in a high-concurrency scenario.

[0147] Optionally, also include:

[0148] Through the requested domain name storage and resolution node, based on the top-level domain name stored in the requested domain name storage and resolution domain and the top-level domain name of the domain name to be resolved in the domain name resolution request, it is determined whether the requested domain name storage and resolution domain is the target domain name storage and resolution domain.

[0149] After executing step S410 and before executing step S420 or step S430, the requesting domain name storage resolution node further includes: judging whether the requesting domain name storage resolution domain is the target domain name storage resolution domain through the requesting domain name storage resolution node. The judging method may be: judging whether the requesting domain name storage resolution domain is the target domain name storage resolution domain based on the top-level domain name stored in the requesting domain name storage resolution domain and the top-level domain name of the domain name to be resolved in the domain name resolution request.

[0150] Specifically, if the top-level domain name stored in the requested domain name storage and resolution domain is the same as the top-level domain name of the domain name to be resolved in the domain name resolution request, it indicates that the requested domain name storage and resolution domain can be used to store the top-level domain name of the domain name to be resolved and its subdomain names (i.e., the domain name to be resolved), and therefore, the requested domain name storage and resolution domain is the target domain name storage and resolution domain; if the top-level domain name stored in the requested domain name storage and resolution domain is not the same as the top-level domain name of the domain name to be resolved in the domain name resolution request, it indicates that the requested domain name storage and resolution domain cannot be used to store the top-level domain name of the domain name to be resolved and its subdomain names, and therefore, the requested domain name storage and resolution domain is not the target domain name storage and resolution domain.

[0151] Optionally, step S420, through the requested domain name storage resolution node, accessing the requested domain name storage resolution domain based on the domain name resolution request to obtain the resolution result of the domain name to be resolved, includes:

[0152] S421. Determine the requested domain name storage and resolution node as the first current domain name storage and resolution node.

[0153] S422. Through the first current domain name storage and resolution node, query the target domain name storage and resolution node corresponding to the domain name to be resolved in the domain name resolution request in the routing table of the local node, send the domain name resolution request to the target domain name storage and resolution node, and obtain the resolution result of the domain name to be resolved.

[0154] Specifically, when the first current domain name storage and resolution node receives the domain name resolution request, it queries the routing table of the local node based on the domain name resolution request, that is, it queries the routing table of the first current domain name storage and resolution node for the target domain name storage and resolution node corresponding to the domain name to be resolved in the domain name resolution request. If the routing table of the first current domain name storage and resolution node queries the target domain name storage and resolution node corresponding to the domain name to be resolved, the domain name resolution request is sent to the target domain name storage and resolution node, so that the target domain name storage and resolution node performs a query based on the domain name resolution request to obtain the resolution result of the domain name to be resolved.

[0155] S423. If the target domain name storage and resolution node is not found in the routing table of the first current domain name storage and resolution node, a new first current domain name storage and resolution node is determined through the first current domain name storage and resolution node, and the domain name resolution request is forwarded to the new first current domain name storage and resolution node in the request domain name storage and resolution domain.

[0156] Specifically, if the routing information of the domain name to be resolved is not found in the routing table of the first current domain name storage and resolution node, it means that the target domain name storage and resolution node cannot be located in the first current domain name storage and resolution node, and it is necessary to forward the domain name resolution request to the new first domain name storage and resolution node in the requested domain name storage and resolution domain, so that the new first domain name storage and resolution node continues to query the domain name to be resolved in the routing table of the local node to locate the target domain name storage and resolution node, and forward the domain name resolution request to the target domain name storage and resolution node to obtain the resolution result of the domain name to be resolved.

[0157] S424: Execute the step of querying the target domain name storage and resolution node corresponding to the domain name to be resolved in the domain name resolution request in the routing table of the local node through the new first current domain name storage and resolution node, until the resolution result is determined.

[0158] Specifically, when the new first current domain name storage and resolution node receives a domain name resolution request, it accesses the local node based on the domain name resolution request, that is, it queries the first current domain name storage and resolution node for the target domain name storage and resolution node corresponding to the domain name to be resolved in the domain name resolution request. If the new first current domain name storage and resolution node queries the target domain name storage and resolution node in the local node, the resolution result of the domain name to be resolved is determined through the target domain name storage and resolution node, and the resolution result is returned to the requesting domain name storage and resolution node. If the new first current domain name storage and resolution node does not query the target domain name storage and resolution node in the routing table of the local node, it is necessary to continue to execute the step of determining the new first current domain name storage and resolution node until the target domain name storage and resolution node is located, and the resolution result is determined by accessing the target domain name storage and resolution node.

[0159] S425: Send the resolution result to the request domain name storage resolution node through the target domain name storage resolution node.

[0160] Specifically, after obtaining the resolution result based on the domain name resolution request query, the target domain name storage resolution node sends the resolution result to the requesting domain name storage resolution node, so that the requesting domain name storage resolution node obtains the resolution result of the domain name to be resolved contained in the first domain name resolution request.

[0161] Optionally, the new first current domain name storage resolution node includes:

[0162] The domain name storage and resolution node that is farthest from the first current domain name storage and resolution node within the preset interval span of the first current domain name storage and resolution node.

[0163] Specifically, in the embodiment of the present invention, in order to further improve the load balancing of the domain name resolution process in a high-concurrency scenario, this embodiment adopts an efficient routing strategy based on the Chord algorithm. Figure 2 As shown, the logic of the Chord algorithm is to allow each node in the network to store the routing information of the domain name storage and resolution node with a preset interval span. The preset interval span can be half the number of domain name storage and resolution nodes in the domain name storage and resolution domain. Therefore, the domain name storage and resolution node farthest from the first current domain name storage and resolution node is determined within the preset interval span, and the domain name storage and resolution node is determined as the new first current domain name storage and resolution node. The advantage of doing this is that it improves the efficiency of data routing and locating the target domain name storage and resolution node, shortens the time to locate the target domain name storage and resolution node to obtain the resolution result, and further improves the load balancing of the domain name resolution process in high concurrency scenarios.

[0164] Embodiment 5

[0165] Figure 6A flowchart of a domain name resolution method is provided for Embodiment 5 of the present invention. Based on the above embodiment, this embodiment further defines step S430. Figure 6 As shown, the method includes:

[0166] S510: Receive a domain name resolution request by requesting a domain name storage resolution node.

[0167] S520: If the requested domain name storage and resolution domain is the target domain name storage and resolution domain, access the requested domain name storage and resolution domain based on the domain name resolution request through the requested domain name storage and resolution node to obtain a resolution result of the domain name to be resolved.

[0168] S530. If the requested domain name storage resolution domain is not the target domain name storage resolution domain, and the requested domain name storage resolution node is the requested anchor node, a cross-domain domain name resolution request is initiated to the routing domain through the requested domain name storage resolution node to access the target storage resolution node of the target domain name storage resolution domain to obtain a resolution result of the domain name to be resolved.

[0169] Among them, the cross-domain domain name resolution request is used to interact in the routing nodes of the routing domain to realize the request of cross-domain domain name resolution; the cross-domain domain name resolution request can be determined based on the domain name resolution request, and the embodiment of the present invention does not limit this.

[0170] Specifically, if the requested domain name storage and resolution domain is not the target domain name storage and resolution domain, it is necessary to send the domain name resolution request to the target domain name storage and resolution domain to which the target domain name storage and resolution node belongs through the routing node in the routing domain, and access the target domain name storage and resolution node in the target domain name storage and resolution domain to obtain the resolution result of the domain name to be resolved. However, only the anchor node in the domain name storage and resolution domain can exchange information with the routing node in the routing domain, so it is necessary to further determine whether the requested domain name storage and resolution node is the requested anchor node.

[0171] If the requested domain name storage resolution domain is not the target domain name storage resolution domain, and the requested domain name storage resolution node is a request anchor node, then the requested domain name storage resolution node in the requested domain name storage resolution domain receives the domain name resolution request and also acts as a request anchor node connected to the routing node in the routing domain, and initiates a cross-domain domain name resolution request to the routing node connected to the request anchor node in the routing domain, thereby locating the target domain name storage resolution domain to which the target domain name storage resolution node belongs based on the cross-domain domain name resolution request through the routing node in the routing domain, and the domain name storage resolution node in the target domain name storage resolution domain queries the domain name to be resolved to obtain the resolution result of the domain name to be resolved.

[0172] S540: If the requested domain name storage and resolution domain is not the target domain name storage and resolution domain, and the requested domain name storage and resolution node is not a requested anchor node, the domain name resolution request is forwarded to the requested anchor node through the requested domain name storage and resolution node; a cross-domain domain name resolution request is initiated to the routing domain through the requested anchor node to access the target domain name storage and resolution node of the target domain name storage and resolution domain to obtain a resolution result of the domain name to be resolved.

[0173] If the requested domain name storage resolution domain is not the target domain name storage resolution domain, and the requested domain name storage resolution node is not the requested anchor node, the requested domain name storage resolution node needs to forward the domain name resolution request to the requested anchor node first, and initiate a cross-domain domain name resolution request to the routing node to which the requested anchor node is connected in the routing domain through the requested anchor node, so that the routing node in the routing domain locates the target domain name storage resolution domain to which the target domain name storage resolution node belongs based on the cross-domain domain name resolution request, and the domain name storage resolution node in the target domain name storage resolution domain queries the domain name to be resolved to obtain the resolution result of the domain name to be resolved.

[0174] The technical solution of the embodiment of the present invention receives a domain name resolution request by requesting a domain name storage resolution node; if the requested domain name storage resolution domain is a target domain name storage resolution domain, the requested domain name storage resolution domain is accessed through the requested domain name storage resolution node based on the domain name resolution request to obtain a resolution result of the domain name to be resolved; if the requested domain name storage resolution domain is not the target domain name storage resolution domain, the requested domain name storage resolution node forwards the domain name resolution request to a routing domain, so that the routing domain accesses the target domain name storage resolution domain based on the domain name resolution request to obtain a resolution result of the domain name to be resolved, thereby solving the problems of uneven computing resource allocation, domain name storage overload and domain name structure confusion in the decentralized DNS technology that uses a single public chain as the underlying infrastructure in the prior art, optimizing the resolution performance, and realizing load balancing of the domain name resolution process in a high-concurrency scenario.

[0175] Optionally, initiating a cross-domain domain name resolution request to the routing domain through the request anchor node to access the target domain name storage resolution node of the target domain name storage resolution domain to obtain the resolution result of the domain name to be resolved, including:

[0176] Determine, through the request anchor node, a cross-domain domain name resolution request based on the domain name resolution request, and send the cross-domain domain name resolution request to the request routing node of the routing domain;

[0177] The resolution result of the domain name to be resolved returned by the request routing node is received through the request anchor node, and the resolution result is obtained by accessing the target domain name storage resolution node based on the cross-domain domain name resolution request sent by the request routing node by the target anchor node of the target domain name storage resolution domain.

[0178] The domain name resolution request received by the requesting anchor node may be a domain name resolution request initiated by a user, or may be a domain name resolution request forwarded by a requesting domain name storage resolution node in the requesting domain name storage resolution domain.

[0179] Specifically, when receiving the domain name resolution request, the requesting anchor node determines the cross-domain domain name resolution request according to the domain name resolution request, and sends the cross-domain domain name resolution request to the requesting routing node connected to the requesting anchor node in the routing domain, so that the routing node in the routing domain determines the target domain name storage resolution domain based on the cross-domain domain name resolution request and sends the cross-domain domain name resolution request to the target domain name storage resolution domain, accesses the target domain name storage resolution node based on the cross-domain domain name resolution request by accessing the target anchor node of the target domain name storage resolution domain, obtains the resolution result of the domain name to be resolved, and returns the resolution result to the requesting anchor node. The requesting anchor node receives the resolution result returned by the requesting routing node in the routing domain.

[0180] Exemplarily, a method for determining a cross-domain domain name resolution request based on a domain name resolution request may be to resolve the domain name resolution request to obtain information such as the name of the domain name to be resolved, and to encapsulate and process the name of the domain name to be resolved to obtain a cross-domain domain name resolution request. The cross-domain domain name resolution request may be recognized by a routing node in a routing domain, and the embodiments of the present invention do not limit this.

[0181] Optionally, also include:

[0182] Through the target anchor node of the target domain name storage resolution domain, the target domain name storage resolution domain is accessed based on the cross-domain domain name resolution request to obtain the resolution result of the domain name to be resolved; and the resolution result is returned to the target routing node.

[0183] Specifically, when the target anchor node of the target domain name storage and resolution domain receives a cross-domain domain name resolution request sent by the target routing node in the routing domain, it accesses the target domain name storage and resolution domain based on the cross-domain domain name resolution request, queries the target domain name storage and resolution node in the target domain name storage and resolution domain to obtain the resolution result of the domain name to be resolved, and returns the resolution result to the target routing node.

[0184] Optionally, accessing the target domain name storage resolution domain based on the cross-domain domain name resolution request through the target anchor node to obtain the resolution result of the domain name to be resolved includes:

[0185] Determine the target anchor node as the second current domain name storage and resolution node;

[0186] Through the second current domain name storage and resolution node, query the target domain name storage and resolution node corresponding to the domain name to be resolved in the cross-domain domain name resolution request in the routing table of the local node, send the cross-domain domain name resolution request to the target domain name storage and resolution node, and obtain the resolution result of the domain name to be resolved;

[0187] If the target domain name storage resolution node is not found in the routing table of the second current domain name storage resolution node, a new second current domain name storage resolution node is determined through the second current domain name storage resolution node, and the cross-domain domain name resolution request is forwarded to the new second current domain name storage resolution node in the target domain name storage resolution domain;

[0188] By using the new second current domain name storage and resolution node, executing the step of searching the routing table of the local node for the target domain name storage and resolution node corresponding to the domain name to be resolved in the domain name resolution request, until the resolution result is determined;

[0189] The resolution result is sent to the target anchor node through the target domain name storage resolution node.

[0190] Specifically, the process of obtaining the resolution result of the domain name to be resolved by accessing the target domain name storage resolution domain through the cross-domain domain name resolution request received by the target anchor node is similar to obtaining the resolution result of the domain name to be resolved by accessing the requested domain name storage resolution domain based on the domain name resolution request through the requested domain name storage resolution node, and the embodiments of the present invention will not elaborate on this.

[0191] Optionally, returning the parsing result to the target routing node through the target anchor node includes:

[0192] If the target routing node and the request routing node are the same routing node, returning the parsing result to the request routing node through the target anchor node, so that the request routing node returns the parsing result to the request anchor node;

[0193] If the target routing node and the request routing node are not the same routing node, the parsing result is returned to the target routing node through the target anchor node, so that the request routing node forwards the parsing result to the request routing node, and returns the parsing result to the request anchor node through the request routing node.

[0194] The request anchor node of the request domain name storage and resolution domain and the target anchor node of the target domain name storage and resolution domain may be connected to the same routing node in the routing domain or to two different routing nodes.

[0195] Specifically, Figure 3B As shown, in the case where the request anchor node of the requesting domain name storage resolution domain and the target anchor node of the target domain name storage resolution domain are connected to the same routing node in the routing domain, that is, the request routing node connected to the request anchor node and the target routing node connected to the target anchor node are the same routing node. At this time, the target anchor node can directly return the resolution result to the requesting routing node, so that the requesting routing node returns the resolution result to the requesting anchor node.

[0196] like Figure 3A As shown, in the case where the request anchor node of the request domain name storage resolution domain and the target anchor node of the target domain name storage resolution domain are connected to two different routing nodes in the routing domain, that is, the request routing node connected to the request anchor node and the target routing node connected to the target anchor node are different routing nodes. At this time, the target anchor node cannot directly return the resolution result to the request routing node. The target anchor node needs to return the resolution result to the target routing node, first forward the resolution result to the request routing node through the request routing node, and then return the resolution result to the request anchor node through the request routing node.

[0197] Embodiment 6

[0198] Figure 7 This is a flowchart of a domain name resolution method provided by Embodiment 6 of the present invention. This embodiment is applicable to the case where a domain name is resolved through a routing domain in a domain name management system. The method can be executed by a domain name resolution device, which can be implemented in the form of hardware and / or software, and can be configured in a terminal device. Figure 7 As shown, the method includes:

[0199] S610: Receive a cross-domain domain name resolution request sent by a request anchor node in a request domain name storage resolution domain through a request routing node, query routing information based on the cross-domain domain name resolution request, and determine a target domain name storage resolution domain.

[0200] The request routing node in the routing domain is connected to the request anchor node in the request domain name storage and resolution domain.

[0201] Specifically, when the requesting routing node receives the cross-domain domain name resolution request sent by the requesting anchor node, it queries the routing information stored in the local node based on the cross-domain domain name resolution request, determines the relevant information of the domain name to be resolved, such as the target domain name storage resolution domain stored in the domain name to be resolved and its top-level domain name, and determines the target domain name storage resolution domain based on the relevant information of the domain name to be resolved.

[0202] S620: Send the cross-domain domain name resolution request to the target domain name storage and resolution domain through the request routing node, so that the target domain name storage and resolution domain obtains the resolution result of the domain name to be resolved based on the cross-domain domain name resolution request query and returns it to the request routing node.

[0203] Specifically, the request routing node sends the cross-domain domain name resolution request to the target domain name storage and resolution domain, so that when the target anchor node of the target domain name storage and resolution domain receives the cross-domain domain name resolution request, it queries at the local node or forwards it to other domain name storage and resolution nodes in the target domain name storage and resolution domain for query, determines the resolution result of the domain name to be resolved and returns it to the request routing node through the request anchor node.

[0204] Exemplarily, the method of requesting the routing node to send the cross-domain domain name resolution request to the target domain name storage and resolution domain may include: requesting the routing node to send the cross-domain domain name resolution request to the target anchor node of the target domain name storage and resolution domain, or requesting the routing node to forward the cross-domain domain name resolution request to the target routing node, and forwarding the cross-domain domain name resolution request to the target anchor node through the target routing node.

[0205] S630: Return the resolution result of the domain name to be resolved to the request anchor node through the request routing node.

[0206] Specifically, when receiving the resolution result of the domain name to be resolved, the request routing node returns the resolution result to the request anchor node, so that the request anchor node returns the resolution result to the request domain name storage resolution receiving node.

[0207] The technical solution of the embodiment of the present invention receives a cross-domain domain name resolution request sent by a request anchor node in a request domain name storage and resolution domain through a request routing node, queries routing information based on the cross-domain domain name resolution request, and determines a cross-domain domain name resolution request of a target domain name storage and resolution domain; sends the cross-domain domain name resolution request to the target domain name storage and resolution domain through the request routing node, so that the target domain name storage and resolution domain obtains a resolution result of the domain name to be resolved based on the cross-domain domain name resolution request query and returns it to the request routing node; returns the resolution result of the domain name to be resolved to the request anchor node through the request routing node, and can realize cross-domain interaction between different domain name storage and resolution domains through the routing domain. Compared with the decentralized DNS technology that uses a single public chain as the underlying infrastructure, it solves the problems of uneven computing resource allocation, domain name storage overload and chaotic domain name structure existing in a single public chain, optimizes the resolution performance, and can meet the requirements of high concurrency scenarios of DNS resolution requests.

[0208] Optionally, sending the cross-domain domain name resolution request to the target domain name storage resolution domain through the request routing node includes:

[0209] If the request routing node and the target routing node are the same node, the cross-domain domain name resolution request is sent to the target anchor node of the target domain name storage resolution domain through the request routing node;

[0210] If the request routing node and the target routing node are not the same node, the cross-domain domain name resolution request is sent to the target routing node through the request routing node; the cross-domain domain name resolution request is forwarded to the target anchor node of the target domain name storage resolution domain through the target routing node.

[0211] The request anchor node of the request domain name storage and resolution domain and the target anchor node of the target domain name storage and resolution domain may be connected to the same routing node in the routing domain or to two different routing nodes.

[0212] Specifically, when the request anchor node of the requesting domain name storage and resolution domain and the target anchor node of the target domain name storage and resolution domain are connected to the same routing node in the routing domain, that is, the request routing node and the target routing node are the same node, the request routing node can directly send the cross-domain domain name resolution request to the target anchor node of the target domain name storage and resolution domain. When the request anchor node of the requesting domain name storage and resolution domain and the target anchor node of the target domain name storage and resolution domain are connected to two different routing nodes in the routing domain, that is, the request routing node connected to the request anchor node and the target routing node connected to the target anchor node are different routing nodes, the request routing node cannot directly send the cross-domain domain name resolution request to the target anchor node of the target domain name storage and resolution domain, and needs to send the cross-domain domain name resolution request line to the target routing node, and then the target routing node forwards the cross-domain domain name resolution request to the target anchor node of the target domain name storage and resolution domain.

[0213] Optionally, returning the resolution result of the domain name to be resolved to the request anchor node through the request routing node includes:

[0214] Receiving, through the target routing node, a parsing result returned by the target anchor node;

[0215] If the request routing node and the target routing node are the same node, the resolution result is sent to the request anchor node of the request domain name storage resolution domain through the target routing node;

[0216] If the request routing node and the target routing node are not the same node, the resolution result is sent to the request routing node through the target routing node; the resolution result is forwarded to the request anchor node of the request domain name storage resolution domain through the request routing node.

[0217] Specifically, similar to the process of sending the cross-domain domain name resolution request to the target domain name storage resolution domain through the request routing node, the process of returning the resolution result of the domain name to be resolved to the request anchor node through the request routing node also includes two cases.

[0218] like Figure 3B As shown, in the case where the request anchor node of the requesting domain name storage and resolution domain and the target anchor node of the target domain name storage and resolution domain are connected to the same routing node in the routing domain, that is, the requesting routing node and the target routing node are the same node,

[0219] like Figure 3A As shown, the request routing node can directly send the cross-domain domain name resolution request to the target anchor node of the target domain name storage resolution domain. In the case where the request anchor node of the request domain name storage resolution domain and the target anchor node of the target domain name storage resolution domain are connected to two different routing nodes in the routing domain, that is, the request routing node connected to the request anchor node and the target routing node connected to the target anchor node are different routing nodes, the request routing node cannot directly send the cross-domain domain name resolution request to the target anchor node of the target domain name storage resolution domain, and needs to send the cross-domain domain name resolution request line to the target routing node, and then the target routing node forwards the cross-domain domain name resolution request to the target anchor node of the target domain name storage resolution domain.

[0220] Embodiment 7

[0221] Figure 8 This is a structural diagram of a domain name registration device provided by Embodiment 7 of the present invention, the device is integrated into a domain name storage and resolution node in a requesting domain name storage and resolution domain. Figure 8 As shown, the device includes: a registration request receiving module 710 and an information uplink module 720;

[0222] A registration request receiving module 710 is used to receive a domain name registration request by requesting a domain name storage resolution node;

[0223] The information uplink module 720 is used to link the domain name information to be registered contained in the domain name registration request to the alliance chain of the target domain name storage and resolution domain through the request domain name storage and resolution node.

[0224] Optionally, the domain name information to be registered includes: the type, name and resource record of the domain name to be registered; accordingly, the information uplink module 720 includes:

[0225] A first information uplinking unit is configured to, if the type of the domain name to be registered is a top-level domain name, uplink the name and resource record of the domain name to be registered to the alliance chain of the target domain name storage and resolution domain through the requesting domain name storage and resolution node;

[0226] The second information uplink unit is used to link the name and resource record of the domain name to be registered to the alliance chain of the target domain name storage and resolution domain through the requesting domain name storage and resolution node if the type of the domain name to be registered is a non-top-level domain name and the top-level domain name of the domain name to be registered exists in the target domain name storage and resolution domain.

[0227] The alliance chain of the target domain name storage resolution domain is established according to the domain name information to be registered.

[0228] Optionally, the device further comprises:

[0229] The information chain module is used to chain the domain name information to be registered contained in the domain name registration request to the alliance chain of the target domain name storage and resolution domain, and then chain the target anchor node routing information to the alliance chain of the routing domain through the target anchor node.

[0230] Optionally, the information uplink module is specifically used for:

[0231] Through the target anchor node, a key-value pair consisting of the domain name to be registered stored in the target domain name storage resolution domain and the routing information of the target anchor node is linked to the alliance chain of the routing domain;

[0232] The target anchor node routing information includes: the Internet Protocol IP address and port number of the target anchor node.

[0233] Optionally, the device further comprises:

[0234] A cancellation request receiving module, used to receive a domain name cancellation request through the request domain name storage resolution node;

[0235] An information review module, used to review the domain name information to be cancelled contained in the domain name cancellation request through the request domain name storage and resolution node, and determine whether the domain name is allowed to be cancelled;

[0236] The cancellation request sending module is used to send the domain name cancellation request to the target domain name storage and resolution node through the request domain name storage and resolution node, so that the allowed cancellation domain name stored in the target domain name storage and resolution node is deleted.

[0237] Optionally, the device further comprises:

[0238] An update request receiving module, used to receive a domain name update request through the request domain name storage resolution node;

[0239] An update information chaining module, used to chain the domain name information to be updated contained in the domain name update request to the alliance chain of the target domain name storage and resolution domain through the requesting domain name storage and resolution node, so as to update the domain name information stored in the target domain name storage and resolution node in the target domain name storage and resolution domain;

[0240] The routing update information chaining module is used to chain the anchor node routing update information to the alliance chain of the routing domain through the anchor node, so as to update the anchor node routing information stored in the routing nodes in the routing domain.

[0241] The domain name registration device provided in the embodiment of the present invention can execute the domain name registration method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0242] Embodiment 8

[0243] Fig. 9 This is a schematic diagram of the structure of a domain name resolution device provided by Embodiment 8 of the present invention, wherein the domain name resolution device is integrated into a domain name storage resolution node in a request domain name storage resolution domain. Fig. 9 As shown, the device includes: a parsing request receiving module 810, a first parsing module 820 and a second parsing module 830;

[0244] A resolution request receiving module 810 is used to receive a domain name resolution request by requesting a domain name storage resolution node;

[0245] A first resolution module 820 is configured to access the requested domain name storage resolution domain based on the domain name resolution request through the requested domain name storage resolution node to obtain a resolution result of the domain name to be resolved if the requested domain name storage resolution domain is a target domain name storage resolution domain;

[0246] The second resolution module 830 is used to forward the domain name resolution request to the routing domain through the request domain name storage resolution node if the request domain name storage resolution domain is not the target domain name storage resolution domain, so that the routing domain accesses the target domain name storage resolution domain based on the domain name resolution request to obtain the resolution result of the domain name to be resolved.

[0247] Optionally, the first parsing module 820 is specifically configured to:

[0248] Determine the requested domain name storage and resolution node as the first current domain name storage and resolution node;

[0249] Through the first current domain name storage and resolution node, query the target domain name storage and resolution node corresponding to the domain name to be resolved in the domain name resolution request in the routing table of the local node, send the domain name resolution request to the target domain name storage and resolution node, and obtain the resolution result of the domain name to be resolved;

[0250] If the target domain name storage resolution node is not found in the routing table of the first current domain name storage resolution node, a new first current domain name storage resolution node is determined through the first current domain name storage resolution node, and the domain name resolution request is forwarded to the new first current domain name storage resolution node in the request domain name storage resolution domain;

[0251] By using the new first current domain name storage and resolution node, executing the step of searching the routing table of the local node for the target domain name storage and resolution node corresponding to the domain name to be resolved in the domain name resolution request, until the resolution result is determined;

[0252] The resolution result is sent to the requesting domain name storage and resolution node through the target domain name storage and resolution node.

[0253] Optionally, the new first current domain name storage resolution node includes:

[0254] The domain name storage and resolution node that is farthest from the first current domain name storage and resolution node within the preset interval span of the first current domain name storage and resolution node.

[0255] Optionally, the second parsing module 830 includes:

[0256] A cross-domain request initiating unit, configured to initiate a cross-domain domain name resolution request to a routing domain through the request domain name storage resolution node if the request domain name storage resolution domain is not the target domain name storage resolution domain and the request domain name storage resolution node is the request anchor node, so as to access the target storage resolution node of the target domain name storage resolution domain and obtain a resolution result of the domain name to be resolved;

[0257] A cross-domain request forwarding unit is used to forward the domain name resolution request to the request anchor node through the request domain name storage resolution node if the request domain name storage resolution domain is not the target domain name storage resolution domain and the request domain name storage resolution node is not the request anchor node; initiate a cross-domain domain name resolution request to the routing domain through the request anchor node to access the target domain name storage resolution node of the target domain name storage resolution domain to obtain the resolution result of the domain name to be resolved.

[0258] Optionally, the device further comprises:

[0259] The judgment module is used to judge whether the requested domain name storage resolution domain is the target domain name storage resolution domain through the requested domain name storage resolution node based on the top-level domain name stored in the requested domain name storage resolution domain and the top-level domain name of the domain name to be resolved in the domain name resolution request.

[0260] Optionally, the cross-domain request initiating unit is specifically used to:

[0261] Determine, through the request anchor node, a cross-domain domain name resolution request based on the domain name resolution request, and send the cross-domain domain name resolution request to the request routing node of the routing domain;

[0262] The resolution result of the domain name to be resolved returned by the request routing node is received through the request anchor node; wherein the resolution result is obtained by accessing the target domain name storage resolution node based on the cross-domain domain name resolution request sent by the request routing node by the target anchor node of the target domain name storage resolution domain.

[0263] Optionally, the device further comprises:

[0264] An access module, configured to access the target domain name storage and resolution domain through a target anchor node of the target domain name storage and resolution domain based on the cross-domain domain name resolution request to obtain a resolution result of the domain name to be resolved;

[0265] The parsing result returning module is used to return the parsing result to the routing node in the target routing domain through the target anchor node, so that the routing node returns the parsing result to the request anchor node.

[0266] Optionally, the access module is specifically used to:

[0267] Determine the target anchor node as the second current domain name storage and resolution node;

[0268] Through the second current domain name storage and resolution node, query the target domain name storage and resolution node corresponding to the domain name to be resolved in the cross-domain domain name resolution request in the routing table of the local node, send the cross-domain domain name resolution request to the target domain name storage and resolution node, and obtain the resolution result of the domain name to be resolved;

[0269] If the target domain name storage resolution node is not found in the routing table of the second current domain name storage resolution node, a new second current domain name storage resolution node is determined through the second current domain name storage resolution node, and the cross-domain domain name resolution request is forwarded to the new second current domain name storage resolution node in the target domain name storage resolution domain;

[0270] By using the new second current domain name storage and resolution node, executing the step of searching the routing table of the local node for the target domain name storage and resolution node corresponding to the domain name to be resolved in the domain name resolution request, until the resolution result is determined;

[0271] The resolution result is sent to the target anchor node through the target domain name storage resolution node.

[0272] Optionally, the parsing result returning module includes:

[0273] If the target routing node and the request routing node are the same routing node, returning the parsing result to the request routing node through the target anchor node, so that the request routing node returns the parsing result to the request anchor node;

[0274] If the target routing node and the request routing node are not the same routing node, the parsing result is returned to the target routing node through the target anchor node, so that the request routing node forwards the parsing result to the request routing node, and returns the parsing result to the request anchor node through the request routing node.

[0275] The domain name resolution device provided in the embodiment of the present invention can execute the domain name resolution method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0276] Embodiment 9

[0277] Fig.10 This is a schematic diagram of the structure of a domain name resolution device provided by Embodiment 9 of the present invention. Fig.10 As shown, the device includes: a resolution request determination module 910, a resolution request sending module 920 and a resolution result sending module 930;

[0278] The resolution request determination module 910 is used to receive a cross-domain domain name resolution request sent by a request anchor node in a request domain name storage resolution domain through a request routing node, and determine a target domain name storage resolution domain based on the cross-domain domain name resolution request query routing information;

[0279] The resolution request sending module 920 is used to send the cross-domain domain name resolution request to the target domain name storage resolution domain through the request routing node, so that the target domain name storage resolution domain obtains the resolution result of the domain name to be resolved based on the cross-domain domain name resolution request query and returns it to the request routing node;

[0280] The resolution result sending module 930 is used to return the resolution result of the domain name to be resolved to the request anchor node by requesting the routing node.

[0281] Optionally, the resolution request sending module 920 is specifically configured to:

[0282] If the request routing node and the target routing node are the same node, the cross-domain domain name resolution request is sent to the target anchor node of the target domain name storage resolution domain through the request routing node;

[0283] If the request routing node and the target routing node are not the same node, the cross-domain domain name resolution request is sent to the target routing node through the request routing node; the cross-domain domain name resolution request is forwarded to the target anchor node of the target domain name storage resolution domain through the target routing node.

[0284] Optionally, the analysis result sending module 930 is specifically used to:

[0285] Receiving, through the target routing node, a parsing result returned by the target anchor node;

[0286] If the request routing node and the target routing node are the same node, the resolution result is sent to the request anchor node of the request domain name storage resolution domain through the target routing node;

[0287] If the request routing node and the target routing node are not the same node, the resolution result is sent to the request routing node through the target routing node; the resolution result is forwarded to the request anchor node of the request domain name storage resolution domain through the request routing node.

[0288] The domain name resolution device provided in the embodiment of the present invention can execute the domain name resolution method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0289] Embodiment 10

[0290] Fig.11 A schematic diagram of the structure of a terminal device 10 that can be used to implement an embodiment of the present invention is shown. The terminal device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The terminal device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0291] like Fig.11As shown, the terminal device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the terminal device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0292] A number of components in the terminal device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the terminal device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0293] The processor 11 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as a domain name registration method and / or a domain name resolution method.

[0294] In some embodiments, the domain name registration method and / or the domain name resolution method may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on the terminal device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the domain name registration method and / or the domain name resolution method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to execute the domain name registration method and / or the domain name resolution method in any other appropriate manner (e.g., by means of firmware).

[0295] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0296] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0297] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0298] To provide interaction with a user, the systems and techniques described herein may be implemented on a terminal device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball), through which the user can provide input to the terminal device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0299] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0300] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0301] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0302] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A domain name management system, characterized in that: include: A routing domain and at least one domain name storage resolution domain; The domain name storage and resolution domain includes: a consortium chain composed of a plurality of domain name storage and resolution nodes, wherein the domain name storage and resolution nodes are used to store and resolve domain names; The routing domain includes: a consortium chain composed of a plurality of routing nodes, wherein the routing nodes are used to store routing information of anchor nodes of the domain name storage and resolution domain; the anchor nodes are domain name storage and resolution nodes in the domain name storage and resolution domain connected to routing nodes in the routing domain; Each of the domain name storage and resolution domains and the routing domain exchanges information through the anchor node and the routing node; The domain name storage and resolution domain includes: a request domain name storage and resolution domain and a target domain name storage and resolution domain; the request domain name storage and resolution domain is the domain name storage and resolution domain to which the request domain name storage and resolution node that receives the domain name request belongs; the target domain name storage and resolution domain is the domain name storage and resolution domain to which the target domain name storage and resolution node requested by the domain name request belongs; wherein the request domain name storage and resolution domain and the target domain name storage and resolution domain are the same domain name storage and resolution domain, or two different domain name storage and resolution domains; The multiple routing nodes of the routing domain include: a request routing node and a target routing node; the request routing node is connected to the request anchor node of the request domain name storage and resolution domain; the target routing node is connected to the target anchor node of the target domain name storage and resolution domain; wherein the request routing node and the target routing node are the same routing node or two different routing nodes.

2. A domain name registration method, characterized in that: The method for storing and resolving a requested domain name in the domain name management system of claim 1 comprises: Receive a domain name registration request by requesting a domain name storage resolution node; The domain name information to be registered contained in the domain name registration request is linked to the alliance chain of the target domain name storage and resolution domain through the request domain name storage and resolution node.

3. The method according to claim 2, characterized in that The domain name information to be registered includes: the type, name and resource record of the domain name to be registered; accordingly, the domain name information to be registered included in the domain name registration request is linked to the alliance chain of the target domain name storage and resolution domain through the request domain name storage and resolution node, including: If the type of the domain name to be registered is a top-level domain name, the name and resource record of the domain name to be registered are chained to the alliance chain of the target domain name storage and resolution domain through the requesting domain name storage and resolution node; If the type of the domain name to be registered is a non-top-level domain name, and the top-level domain name of the domain name to be registered exists in the target domain name storage and resolution domain, then the name and resource records of the domain name to be registered are linked to the alliance chain of the target domain name storage and resolution domain through the requesting domain name storage and resolution node; The alliance chain of the target domain name storage resolution domain is established according to the domain name information to be registered.

4. The method according to claim 2, characterized in that: After uploading the domain name information to be registered included in the domain name registration request to the alliance chain of the target domain name storage and resolution domain, the method further includes: Through the target anchor node, the routing information of the target anchor node is uploaded to the alliance chain of the routing domain.

5. The method according to claim 2, characterized in that: Also includes: Receiving a domain name cancellation request through the request domain name storage and resolution node; The domain name storage and resolution node for requesting the domain name is used to review the domain name information to be cancelled contained in the domain name cancellation request, and determine whether the domain name is allowed to be cancelled; The domain name cancellation request is sent to the target domain name storage and resolution node through the requesting domain name storage and resolution node, so that the domain name allowed to be cancelled stored in the target domain name storage and resolution node is deleted.

6. The method according to claim 2, characterized in that Also includes: Receiving a domain name update request through the request domain name storage resolution node; The domain name information to be updated contained in the domain name update request is linked to the alliance chain of the target domain name storage and resolution domain through the requesting domain name storage and resolution node, so as to update the domain name information stored in the target domain name storage and resolution node in the target domain name storage and resolution domain; The anchor node routing update information is uploaded to the alliance chain of the routing domain through the anchor node to update the anchor node routing information stored in the routing nodes in the routing domain.

7. A domain name resolution method, characterized in that: The method for storing and resolving domain names in the domain name management system according to claim 1 comprises: Receive the domain name resolution request by requesting the domain name storage resolution node; If the requested domain name storage and resolution domain is the target domain name storage and resolution domain, accessing the requested domain name storage and resolution domain based on the domain name resolution request through the requested domain name storage and resolution node to obtain a resolution result of the domain name to be resolved; If the requested domain name storage and resolution domain is not the target domain name storage and resolution domain, the domain name resolution request is forwarded to the routing domain through the requested domain name storage and resolution node, so that the routing domain accesses the target domain name storage and resolution domain based on the domain name resolution request to obtain the resolution result of the domain name to be resolved.

8. The method according to claim 7, characterized in that The request domain name storage and resolution node accesses the request domain name storage and resolution domain based on the domain name resolution request to obtain the resolution result of the domain name to be resolved, including: Determine the requested domain name storage and resolution node as the first current domain name storage and resolution node; Through the first current domain name storage and resolution node, query the target domain name storage and resolution node corresponding to the domain name to be resolved in the domain name resolution request in the routing table of the local node, send the domain name resolution request to the target domain name storage and resolution node, and obtain the resolution result of the domain name to be resolved; If the target domain name storage resolution node is not found in the routing table of the first current domain name storage resolution node, a new first current domain name storage resolution node is determined through the first current domain name storage resolution node, and the domain name resolution request is forwarded to the new first current domain name storage resolution node in the request domain name storage resolution domain; By using the new first current domain name storage and resolution node, executing the step of searching the routing table of the local node for the target domain name storage and resolution node corresponding to the domain name to be resolved in the domain name resolution request, until the resolution result is determined; The resolution result is sent to the requesting domain name storage and resolution node through the target domain name storage and resolution node.

9. The method according to claim 8, characterized in that The new first current domain name storage and resolution node includes: The domain name storage and resolution node that is farthest from the first current domain name storage and resolution node within the preset interval span of the first current domain name storage and resolution node.

10. The method according to claim 7, characterized in that The domain name resolution request is forwarded to the routing domain by the requesting domain name storage resolution node, so that the routing domain accesses the target domain name storage resolution domain based on the domain name resolution request to obtain the resolution result of the domain name to be resolved, including: If the requested domain name storage resolution domain is not the target domain name storage resolution domain, and the requested domain name storage resolution node is the requested anchor node, a cross-domain domain name resolution request is initiated to the routing domain through the requested domain name storage resolution node to access the target storage resolution node of the target domain name storage resolution domain to obtain a resolution result of the domain name to be resolved; If the requested domain name storage and resolution domain is not the target domain name storage and resolution domain, and the requested domain name storage and resolution node is not a requested anchor node, the domain name resolution request is forwarded to the requested anchor node through the requested domain name storage and resolution node; a cross-domain domain name resolution request is initiated to the routing domain through the requested anchor node to access the target domain name storage and resolution node of the target domain name storage and resolution domain to obtain a resolution result of the domain name to be resolved.

11. The method according to claim 10, characterized in that Initiating a cross-domain domain name resolution request to the routing domain through the request anchor node to access the target domain name storage resolution node of the target domain name storage resolution domain to obtain the resolution result of the domain name to be resolved, including: Determine, through the request anchor node, a cross-domain domain name resolution request based on the domain name resolution request, and send the cross-domain domain name resolution request to the request routing node of the routing domain; The resolution result of the domain name to be resolved returned by the request routing node is received through the request anchor node; wherein the resolution result is obtained by accessing the target domain name storage resolution node based on the cross-domain domain name resolution request sent by the request routing node by the target anchor node of the target domain name storage resolution domain.

12. The method according to claim 11, characterized in that Also includes: Accessing the target domain name storage and resolution domain based on the cross-domain domain name resolution request through the target anchor node of the target domain name storage and resolution domain to obtain the resolution result of the domain name to be resolved; The parsing result is returned to a routing node in the target routing domain through the target anchor node, so that the routing node returns the parsing result to the requesting anchor node.

13. The method according to claim 12, characterized in that Accessing the target domain name storage resolution domain based on the cross-domain domain name resolution request through the target anchor node to obtain the resolution result of the domain name to be resolved includes: Determine the target anchor node as the second current domain name storage and resolution node; Through the second current domain name storage and resolution node, query the target domain name storage and resolution node corresponding to the domain name to be resolved in the cross-domain domain name resolution request in the routing table of the local node, send the cross-domain domain name resolution request to the target domain name storage and resolution node, and obtain the resolution result of the domain name to be resolved; If the target domain name storage resolution node is not found in the routing table of the second current domain name storage resolution node, a new second current domain name storage resolution node is determined through the second current domain name storage resolution node, and the cross-domain domain name resolution request is forwarded to the new second current domain name storage resolution node in the target domain name storage resolution domain; By using the new second current domain name storage and resolution node, executing the step of searching the routing table of the local node for the target domain name storage and resolution node corresponding to the domain name to be resolved in the domain name resolution request, until the resolution result is determined; The resolution result is sent to the target anchor node through the target domain name storage resolution node.

14. The method according to claim 12, characterized in that The target anchor node of the target domain is stored in the target domain name, and the resolution result is returned to the routing node in the target routing domain, including: If the target routing node and the request routing node are the same routing node, returning the parsing result to the request routing node through the target anchor node, so that the request routing node returns the parsing result to the request anchor node; If the target routing node and the request routing node are not the same routing node, the parsing result is returned to the target routing node through the target anchor node, so that the request routing node forwards the parsing result to the request routing node, and returns the parsing result to the request anchor node through the request routing node.

15. A domain name resolution method, characterized in that: Applied to the routing domain in the domain name management system of claim 1, the method comprises: Receiving, by requesting a routing node, a cross-domain domain name resolution request sent by a request anchor node in a request domain name storage resolution domain, and determining a target domain name storage resolution domain based on querying routing information of the cross-domain domain name resolution request; The cross-domain domain name resolution request is sent to the target domain name storage resolution domain through the request routing node, so that the target domain name storage resolution domain obtains the resolution result of the domain name to be resolved based on the cross-domain domain name resolution request query and returns it to the request routing node; The resolution result of the domain name to be resolved is returned to the request anchor node through the request routing node.

16. A domain name registration device, characterized in that: The device for storing and resolving a requested domain name in the domain name management system according to claim 1 comprises: A registration request receiving module, used to receive a domain name registration request by requesting a domain name storage resolution node; The information chain module is used to chain the domain name information to be registered contained in the domain name registration request to the alliance chain of the target domain name storage and resolution domain through the request domain name storage and resolution node.

17. A domain name resolution device, characterized in that: The domain name storage and resolution domain used in the domain name management system according to claim 1, the device comprising: A resolution request receiving module, used to receive a domain name resolution request by requesting a domain name storage resolution node; A first resolution module, configured to, if the requested domain name storage resolution domain is a target domain name storage resolution domain, access the requested domain name storage resolution domain based on the domain name resolution request through the requested domain name storage resolution node to obtain a resolution result of the domain name to be resolved; The second resolution module is used to forward the domain name resolution request to the routing domain through the request domain name storage resolution node if the request domain name storage resolution domain is not the target domain name storage resolution domain, so that the routing domain accesses the target domain name storage resolution domain based on the domain name resolution request to obtain the resolution result of the domain name to be resolved.

18. A domain name resolution device, characterized in that: Applied to the routing domain in the domain name management system of claim 1, the device comprises: A resolution request determination module is used to receive a cross-domain domain name resolution request sent by a request anchor node in a request domain name storage resolution domain through a request routing node, and determine a target domain name storage resolution domain based on the cross-domain domain name resolution request query routing information; A resolution request sending module, used for sending the cross-domain domain name resolution request to the target domain name storage resolution domain through the request routing node, so that the target domain name storage resolution domain obtains the resolution result of the domain name to be resolved based on the cross-domain domain name resolution request query and returns it to the request routing node; The resolution result sending module is used to return the resolution result of the domain name to be resolved to the request anchor node by requesting the routing node.

19. A terminal device, characterized in that: The terminal device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the domain name registration method described in any one of claims 2-6 and / or execute the domain name resolution method described in any one of claims 7-15.

20. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the domain name registration method described in any one of claims 2 to 6 and / or the domain name resolution method described in any one of claims 7 to 15 when executed.

Images