Reverse address resolution method, address allocation method, and hierarchical domain name service system

Abstract

The application discloses a reverse address resolution method, an address allocation method and a hierarchical domain name service system. The resolution method comprises the following steps: receiving a reverse address resolution request sent by an edge terminal, the request comprising an address to be resolved; if it is determined that a domain name service unit does not store a reverse resolution record corresponding to the address to be resolved, forwarding the reverse address resolution request to a central domain name service unit, so that the central domain name service unit performs reverse resolution on the address to be resolved through subordinate sub-domain name service units of each level, and generates response information; receiving the response information fed back by the central domain name service unit and the sub-domain name service units of each level, and generating a reverse resolution record using the response information and sending the record to the edge terminal. The reverse resolution of the address to be resolved is realized through the sub-domain name service units of each level, the load of the central domain name service unit is reduced, and the reverse resolution efficiency is improved. Moreover, the edge terminal can obtain the identification and attribute feature set of a service terminal, and the reverse resolution service provided is flexible and rich.

Description

Technical Field

[0001] This invention relates to the field of communication technology, specifically to a reverse address resolution method, an address allocation method, and a hierarchical domain name service system. Background Technology

[0002] Since IPv6-based Internet Protocol addresses can provide approximately 4.3 billion to the power of 4 addresses, address resources are abundant and can meet the address allocation needs of all current and future terminal devices and service sites, enabling Internet access and end-to-end device communication. For edge devices deployed at the network edge, direct access based on IP addresses is more efficient and faster than existing domain name access methods. Therefore, reverse resolution from IP address to domain name has become an application requirement.

[0003] However, currently, reverse lookup services are deployed directly on the DNS (Domain Name Resolution) system. This means that in addition to maintaining forward lookup records from domain names to IP addresses, the DNS system also needs to maintain a full set of reverse lookup records (i.e., PTR records). Since the number of IPv6 addresses is very large, this increases the workload of the DNS system in performing reverse lookup operations, resulting in a significant increase in query latency. Summary of the Invention

[0004] The purpose of this invention is to address the shortcomings of the prior art by proposing a reverse address resolution method and apparatus, an address allocation method and apparatus, and a hierarchical domain name service system. This purpose is achieved through the following technical solutions.

[0005] The first aspect of this invention proposes a reverse address resolution method applied to a domain name service unit, the method comprising:

[0006] Receive a reverse address resolution request sent by an edge terminal, the reverse address resolution request including the address to be resolved;

[0007] If it is determined that the domain name service unit does not store a reverse resolution record corresponding to the address to be resolved, the reverse address resolution request is forwarded to the central domain name service unit, so that the central domain name service unit performs reverse resolution on the address to be resolved through its subordinate subdomain name service units at each level, and generates response information corresponding to the reverse address resolution request.

[0008] Receive response information from the central domain name service unit and subdomain name service units at each level, and use the response information to generate a reverse resolution record and send it to the edge terminal;

[0009] The reverse resolution record includes the identification information of the service terminal corresponding to the address to be resolved, as well as the attribute feature parameters corresponding to the subdomain service units at each level participating in the reverse resolution.

[0010] A second aspect of the present invention provides a reverse address resolution apparatus for use in a domain name service unit, the apparatus comprising:

[0011] The request receiving module is used to receive a reverse address resolution request sent by the edge terminal, wherein the reverse address resolution request includes the address to be resolved;

[0012] The reverse resolution module is used to forward the reverse address resolution request to the central domain name service unit when it is determined that the domain name service unit does not store a reverse resolution record corresponding to the address to be resolved, so that the central domain name service unit can perform reverse resolution on the address to be resolved through its subordinate subdomain name service units and generate response information corresponding to the reverse address resolution request.

[0013] The response feedback module is used to receive response information from the central domain name service unit and the subdomain name service units at each level, and to use the response information to generate a reverse resolution record and send it to the edge terminal.

[0014] The reverse resolution record includes the identification information of the service terminal corresponding to the address to be resolved, as well as the attribute feature parameters corresponding to the subdomain service units at each level participating in the reverse resolution.

[0015] The reverse address resolution method and apparatus described in the first and second aspects above have the following beneficial effects or advantages:

[0016] When the local domain name service unit (the domain name service unit closest to the deployment location of the terminal device) receives a reverse resolution request, if the corresponding reverse resolution record is not stored locally, the reverse resolution request is forwarded to the central domain name service unit. The central domain name service unit then performs the reverse resolution of the address to be resolved through its subordinate domain name service units at various levels. This reduces the load on the central domain name service unit and makes the reverse resolution faster and more convenient to manage.

[0017] Furthermore, by adopting a layer-by-layer reverse resolution method, after the edge terminal receives the response returned by the local domain name service unit, it can not only obtain the unique identifier of the service terminal corresponding to the address to be resolved, but also obtain the set of attribute feature parameters corresponding to the service terminal. This provides a flexible reverse domain name resolution service, making the resolution results richer and easier to integrate into other application scenarios.

[0018] A third aspect of the present invention provides an address allocation method applied to a control platform in a hierarchical domain name service system, the method comprising:

[0019] Receive an address request sent by an edge terminal, the address request including attribute feature parameters of the edge terminal;

[0020] From the subdomain service units at each level recorded locally, determine the subdomain service unit corresponding to the attribute feature parameter, and allocate a free address to the edge terminal from the address block included in the determined subdomain service unit;

[0021] A registration notification containing the address and the identification information of the edge terminal is sent to the determined subdomain service unit so that the subdomain service unit can establish a reverse domain record using the address and the identification information.

[0022] A fourth aspect of the present invention provides an address allocation device for use in a control platform of a hierarchical domain name service system, the device comprising:

[0023] A request receiving module is used to receive an address request sent by an edge terminal, the address request including attribute feature parameters of the edge terminal;

[0024] The address allocation module is used to determine the subdomain service unit corresponding to the attribute feature parameter from the subdomain service units at each level recorded locally, and allocate a free address to the edge terminal from the address block included in the determined subdomain service unit.

[0025] The registration module is used to send a registration notification containing the address and the identification information of the edge terminal to the determined subdomain service unit, so that the subdomain service unit can use the address and the identification information to establish a reverse domain record.

[0026] The address allocation method and apparatus described in the third and fourth aspects above have the following beneficial effects or advantages:

[0027] When an address request is received from an edge terminal, the system matches the subdomain service units (SSUs) at each level that correspond to the attribute feature parameters of the edge terminal. It then allocates an address to the edge terminal using the address block maintained by the matched SSU. Simultaneously, it registers the address with the matched SSU to establish a reverse lookup record, facilitating subsequent reverse DNS lookups. Since the reverse lookup record for the edge terminal is maintained by the SSU at the level corresponding to the edge terminal's attribute feature parameters (i.e., the SSU of the address assigned to the edge terminal), meaning that reverse lookup records are maintained on SSUs with different attribute feature parameters, this maximizes the conservation of SSU storage resources, accelerates subsequent address reverse lookup matching, and improves resolution efficiency.

[0028] The fifth aspect of the present invention proposes a hierarchical domain name service system, the system comprising a control platform, a central domain name service unit, and subdomain name service units at each subordinate level;

[0029] Each level has at least one subdomain service unit. The subdomain service unit contains the attribute feature parameters and address blocks of the corresponding level. The subdomain service unit is associated with at least one subdomain service unit in the next level, and the subdomain service unit records the attribute feature parameters and address blocks of each subdomain service unit associated with it in the next level.

[0030] The control platform is used to allocate idle addresses to edge terminals according to the attribute feature parameters of the edge terminals, and send the addresses and the identification information of the edge terminals to the subdomain service unit corresponding to the attribute feature parameters for registration.

[0031] The hierarchical domain name service system described in the fifth aspect above has the following beneficial effects or advantages:

[0032] By deploying domain name service units in a hierarchical manner, each domain name service unit only maintains the attribute feature parameters and address network segment of its corresponding level, so as to map each level of domain name service unit to specific attributes that can be visually identified (such as location, security, application, business, etc.). Furthermore, the hierarchical deployment of domain name service units has relatively low equipment requirements. Depending on the conditions and needs, it can be deployed centrally or distributed, making the deployment more flexible and suitable for ultra-large-scale edge deployment and scheduling scenarios.

[0033] A sixth aspect of the present invention provides a server comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, performs the steps of the method as described in the first or third aspect above.

[0034] A seventh aspect of the present invention provides a computer-readable storage medium storing a computer program that, when read and executed by a processor, implements the steps of the method as described in the first or third aspect above.

[0035] The eighth aspect of the present invention provides a computer program product comprising a computer program, characterized in that the computer program is executed by a processor to implement the steps of the method as described in the first or third aspect above. Attached Figure Description

[0036] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this invention, illustrate exemplary embodiments of the invention and are used to explain the invention, but do not constitute an undue limitation of the invention. In the drawings:

[0037] Figure 1 This is a schematic diagram illustrating a hierarchical domain name service system structure according to an exemplary embodiment of the present invention;

[0038] Figure 2 This is a schematic diagram illustrating the attribute hierarchy structure of an edge terminal according to an exemplary embodiment of the present invention;

[0039] Figure 3 This is a flowchart illustrating an embodiment of an address allocation method according to an exemplary embodiment of the present invention;

[0040] Figure 4 This is a flowchart illustrating an embodiment of the reverse address resolution method according to an exemplary embodiment of the present invention;

[0041] Figure 5 This is a schematic diagram illustrating the structure of an address allocation device according to an exemplary embodiment of the present invention;

[0042] Figure 6 This is a schematic diagram illustrating the structure of a reverse address resolution device according to an exemplary embodiment of the present invention;

[0043] Figure 7 This is a schematic diagram of the hardware structure of a server according to an exemplary embodiment of the present invention;

[0044] Figure 8 This is a schematic diagram illustrating the structure of a storage medium according to an exemplary embodiment of the present invention. Detailed Implementation

[0045] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the invention as detailed in the appended claims.

[0046] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. The singular forms “a,” “the,” and “the” used in this invention and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more of the associated listed items.

[0047] It should be understood that although the terms first, second, third, etc., may be used in this invention to describe various information, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first information may also be referred to as second information without departing from the scope of this invention, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

[0048] In the existing solution, reverse DNS and the DNS system are deployed on the same site. In order to perform reverse DNS, all reverse DNS records must be established and maintained on the DNS system at the same time. Since the number of IPv6 addresses is very large, this will increase the operating load of the DNS system to perform reverse DNS operations. Therefore, the current technical architecture cannot provide flexible and efficient reverse DNS services for future ultra-large-scale IPv6 edge devices.

[0049] Based on this, the present invention proposes a hierarchical domain name service system, see [link to relevant documentation]. Figure 1 As shown, the hierarchical domain name service system includes a control platform, a central domain name service unit NS belonging to the central level, and subdomain name service units NS at each subordinate level.

[0050] Depend on Figure 1 As can be seen, the domain name service units at each level are deployed in a tree-like topology from top to bottom, with the top level being the central level, followed by the first level, the second level, ..., the nth level, and the lowest level (i.e., the access level). Each level has at least one subdomain name service unit, and each subdomain name service unit contains the attribute feature parameters and address blocks of the corresponding level. Each subdomain name service unit is associated with at least one subdomain name service unit in the next level, and each subdomain name service unit records the attribute feature parameters and address blocks of each subdomain name service unit associated with it in the next level.

[0051] The control platform manages the data of domain name service units at each level, and is used to allocate idle addresses to edge terminals according to the attribute feature parameters of the edge terminals, and send the addresses and the identification information of the edge terminals to the subdomain name service units corresponding to the attribute feature parameters of the edge terminals for registration.

[0052] The domain name service units deployed at each level can be virtualized, and each level's domain name service unit can be deployed on one or more physical servers as needed. For example, they can be deployed on distributed DNS servers or server clusters, on routers or business hosts that independently provide domain name resolution services, on virtual hosts or cloud hosts, or centrally deployed in the various subsystem units of the domain name service system that are planned hierarchically and have reverse resolution domains. This application does not specifically limit the specific deployment method of the domain name service units.

[0053] Preferably, domain name service units at the same level can be backed up in multiple locations and deployed in a distributed manner to increase security redundancy and facilitate users to access the nearest location.

[0054] Furthermore, each domain name service unit may include a communication module, a processing module, and a storage module. The communication module receives and forwards reverse DNS lookup requests from edge terminals and returns a response; the processing module generates forward and reverse DNS lookup records and sends them to the storage module for storage; after the communication module receives a DNS lookup request, the processing module also queries the storage module for a match and forwards the query result back to the communication module for transmission; the storage module stores the forward and reverse DNS lookup records.

[0055] In this embodiment, for the attribute feature parameters and address blocks maintained by each subdomain service unit in each level, the applied addresses are pre-divided into address blocks according to the hierarchical structure, and the attribute features of each level of the edge terminal are mapped to the address blocks of each level, thereby realizing the visual mapping of the attribute features of the edge terminal corresponding to each level of address blocks. The specific implementation process is described as follows:

[0056] (1) Specific layering process based on the attribute characteristics of edge terminals:

[0057] Based on the hierarchical relationship of the hierarchical domain name service system, the attribute types of edge terminals are hierarchically divided. That is, these attribute types (such as location, terminal type, application, security, etc.) are defined from high to low as first-level attributes, second-level attributes, third-level attributes, and so on, with the lowest-level attributes defined as access-level attributes.

[0058] See Figure 2 As shown, an attribute at the same level should contain the set of attribute feature parameters of all attributes at the same level. Specifically, if a location attribute is defined as a certain level attribute, then the attribute at that level contains the attribute features of all location ranges at the same level. For example, if the location attribute is at the city level, then the attribute features of the location ranges at the same level that it contains could be Shenzhen, Beijing, Shanghai, etc.

[0059] Furthermore, each attribute feature contained in an attribute at the same level corresponds to a set of attribute features at the next lower level.

[0060] Therefore, in this embodiment, when the attribute feature parameters of subdomain service units at each level all belong to the same attribute type, the attribute feature parameters of the next level subdomain service unit are sub-attributes of the attribute feature parameters of the previous level, and the subdomain service unit corresponding to the attribute feature parameters of the previous level is associated with the subdomain service unit of the next level.

[0061] It should be noted that different types of attributes can be divided into different levels, or attributes of the same type can be divided into multiple levels. Specifically, when using attributes of the same type to divide into multiple levels, the attributes of lower levels should be sub-attributes of the attributes of higher levels. For example, when defining two levels using location attributes, "province" can be defined as the attribute of the higher level, and "city" as the attribute of the lower level. Furthermore, the hierarchical order of attribute types of edge terminals can be determined based on factors such as the business characteristics in the actual scenario, the hierarchical relationship of attributes, network routing structure, and management optimization, and this application does not impose any restrictions. However, once the attribute hierarchy is determined, it should be kept as unchanged as possible to reduce the complexity of management and maintenance.

[0062] (2) The specific layering process for the requested address blocks is explained below, taking IPv6 addresses as an example:

[0063] First, the user (i.e. the service provider) applies for a block of addresses of sufficient size from the Regional Internet Registry (RIR) or Internet Service Provider (ISP) for allocation to edge terminals.

[0064] Optionally, the requested IPv6 address blocks should be contiguous, and all IPv6 addresses within a single block should share the same address prefix. Alternatively, users can request different IPv6 address blocks from multiple ISPs or RIRs. In this case, the address prefix for each IPv6 address block can be different, but it's best to ensure that the address prefix for each IPv6 address block occupies the same length of bits (typically using nibbles to represent IPv6 address bits, i.e., 1 bit equals 4 bits).

[0065] Then, the requested address blocks are divided into hierarchical levels according to the attribute hierarchy relationship described above, and the address blocks corresponding to each attribute feature parameter of the same level are respectively used as the address pool for the address blocks of the next level.

[0066] Optionally, IPv6 address block hierarchy partitioning can be allocated on nibble boundaries, which allows the corresponding address blocks to be represented in dotted hexadecimal numbers in the inverse domain record, simplifying the mapping of the inverse domain record and reducing allocation errors.

[0067] Preferably, address blocks of equal size can be divided for each attribute feature within the same level, so that the prefix boundaries of address blocks at the same level are the same, thereby simplifying allocation and management and improving reverse lookup efficiency.

[0068] In practical implementation, the bit length of the prefix boundary of each level of address block can be set according to the size of the attribute feature parameter set of each level. The longer the bit length of the prefix boundary, the more attribute feature parameters can be defined in the same level. Different levels can be divided into prefix boundaries with different bit lengths. The specific division method can be determined according to the actual situation, and this application does not impose any restrictions.

[0069] For example, combining Figure 1 As shown, all address blocks corresponding to the requested IPv6 addresses are allocated to the central domain name service unit (CNSS) at the central level for maintenance. Starting from the CNSS, the process proceeds sequentially from higher to lower levels. The address blocks of the subdomain service units in the first level under the CNSS serve as the address pool for each subdomain service unit in the first level. Address blocks are allocated and maintained for each subdomain service unit in the first level based on various attribute characteristics. Each address block in the first level serves as the address pool for each address block in the second level. Address blocks are allocated and maintained for each subdomain service unit in the second level based on various attribute characteristics, and so on, with each level sequentially allocating address blocks downwards.

[0070] Since the attribute characteristics of each level have been mapped to each domain name service unit at each level, the attribute characteristics of the terminal corresponding to the IPv6 address maintained by each level of domain name service unit can be identified by using the address prefix of the address block maintained by each level of domain name service unit.

[0071] Therefore, in this embodiment, the address block contained in the next-level subdomain service unit is a sub-address block of the address block of the previous level, and the subdomain service unit to which the address block of the previous level belongs is associated with the subdomain service unit of the next level.

[0072] Furthermore, address blocks belonging to the same level have the same address prefix length to simplify allocation and management and improve reverse lookup efficiency.

[0073] Based on the hierarchical domain name service system described above, the technical effects that can be achieved include:

[0074] By deploying domain name service units in a hierarchical manner, each domain name service unit only maintains the attribute feature parameters and address network segment of its corresponding level, so as to map each level of domain name service unit to specific attributes that can be visually identified (such as location, security, application, business, etc.). Furthermore, the hierarchical deployment of domain name service units has relatively low equipment requirements. Depending on the conditions and needs, it can be deployed centrally or distributed, making the deployment more flexible and suitable for ultra-large-scale edge deployment and scheduling scenarios.

[0075] Based on the hierarchical domain name service system proposed above, this application also proposes a reverse address resolution method and an address allocation method. In order to enable those skilled in the art to better understand these two application schemes, the technical solutions of these two application schemes will be clearly and completely described below with reference to the accompanying drawings in the embodiments of this application.

[0076] Figure 3 This is a flowchart illustrating an embodiment of an address allocation method according to an exemplary embodiment of the present invention, applied to the above. Figure 1 The control platform in the hierarchical domain name service system shown, taking IPv6 addresses as an example, is as follows: Figure 3 As shown, this address allocation method includes the following steps:

[0077] Step 301: Receive an address request sent by the edge terminal. The address request includes the attribute feature parameters of the edge terminal.

[0078] In this embodiment of the application, when deploying an edge terminal, the edge terminal initiates an address request to the control platform to apply for an IPv6 address for binding, and the address request carries attribute characteristic parameters related to the deployment status of the edge terminal.

[0079] Step 302: Determine the subdomain service unit corresponding to the attribute feature parameters from the subdomain service units at each level recorded locally, and allocate a free address to the edge terminal from the address block included in the determined subdomain service unit.

[0080] In practice, if the edge terminal possesses the attribute characteristics of all levels in the hierarchical domain name system, the control platform will ultimately determine the subdomain service unit corresponding to the attribute characteristic parameters of the edge terminal from the subdomain service units of the access level. If the edge terminal does not possess the attribute characteristics of all levels, the control platform will determine the level to which it belongs based on the attribute characteristic parameters of the edge terminal, and then determine the subdomain service unit corresponding to the specific attribute characteristic parameters from the subdomain service units of the corresponding level.

[0081] Step 303: Send a registration notification containing the address and the identification information of the edge terminal to the determined subdomain service unit, so that the subdomain service unit can use the address and the identification information to establish a reverse domain record.

[0082] Among them, the identification information of the edge terminal is its unique identity identifier. For example, domain name, URL, physical ID, etc. can all serve as the unique identity identifier of the edge terminal.

[0083] Furthermore, the process of establishing reverse domain records by the subdomain service unit involves reversing the forward mapping relationship between the edge terminal's identification information and its address.

[0084] Specifically, the reverse domain record (PTR) is a half-byte hexadecimal number string separated by ".", stored in the ".IP6.ARPA" field, and the reverse domain record is appended with the suffix ".IP6.ARPA".

[0085] For example, taking the IPv6 address "2001:db01:2:3::1" as an example, the reverse domain record is constructed by reversing the half-byte characters of the IPv6 address and adding the suffix ".IP6.ARPA". Thus, the IPv6 address stored as a reverse domain record is displayed as follows:

[0086] "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.3.0.0.0.2.0.0.0.1.0.bd1.0.0.2.IP6.ARPA"

[0087] It should be noted that, while establishing the reverse resolution domain record, a forward resolution domain record (AAAA) from the edge terminal's identification information to its address can also be established.

[0088] This completes the above. Figure 3 The address allocation process illustrated involves, upon receiving an address request from an edge terminal, matching the subdomain service unit (SSU) corresponding to the edge terminal's attribute characteristics from various levels of SSUs. The SSU then allocates an address to the edge terminal using the address block maintained by the matched SSU. Simultaneously, address registration is performed with the matched SSU to establish a reverse lookup record, facilitating subsequent reverse DNS lookups. Since the edge terminal's reverse lookup record is maintained by the SSU at the level corresponding to the edge terminal's attribute characteristics (i.e., the SSU to which the address assigned to the edge terminal belongs), meaning that reverse lookup records are maintained on SSUs with different attribute characteristics, this maximizes the conservation of SSU storage resources, accelerates subsequent address reverse lookup matching, and improves resolution efficiency.

[0089] Figure 4This is a flowchart illustrating an embodiment of the reverse address resolution method according to an exemplary embodiment of the present invention. The method is applied to a domain name service unit, which is deployed closest to the deployment location of the edge terminal. It is a local domain name service unit configured on the edge terminal itself, hereinafter referred to as the local domain name service unit. It is understood that the local domain name service unit can also be the one described above. Figure 1 The central domain name service unit in the hierarchical domain name service system shown, or the subdomain name service unit in any level, is not limited in this application.

[0090] In combination with the above Figure 1 The hierarchical domain name service system shown, such as Figure 4 As shown, the reverse address resolution method includes the following steps:

[0091] Step 401: Receive a reverse address resolution request sent by the edge terminal, which includes the address to be resolved.

[0092] The address to be resolved carried in the reverse address resolution request can be the address of any edge terminal, and this application does not impose any restrictions on this.

[0093] Step 402: If it is determined that this domain name service unit does not store a reverse resolution record corresponding to the address to be resolved, the reverse address resolution request is forwarded to the central domain name service unit, so that the central domain name service unit can perform reverse resolution on the address to be resolved through its subordinate subdomain name service units at each level, and generate response information corresponding to the reverse address resolution request.

[0094] Typically, the local domain name service unit stores the address and its corresponding reverse lookup record for any address that has been requested and resolved by an edge terminal, so that it can be used for subsequent resolution requests from other edge terminals. Specifically, the reverse lookup record refers to the information obtained through the reverse lookup process, including the identification information of the service terminal corresponding to the address and the attribute feature parameters corresponding to the subdomain service units at each level participating in the reverse lookup.

[0095] Based on this, the process of determining that the domain name service unit does not store the reverse lookup record corresponding to the address to be resolved is to search for the reverse lookup record corresponding to the address to be resolved in the locally cached reverse lookup records. If no record is found, it is determined that the domain name service unit does not store the reverse lookup record corresponding to the address to be resolved.

[0096] Furthermore, if a match is found, the domain name service unit directly returns the reverse resolution record corresponding to the address to be resolved to the edge terminal, saving the search and matching process.

[0097] In one possible implementation, the process involves the central domain name service unit performing reverse DNS lookup of the address to be resolved through its subordinate subdomain service units at each level, and generating response information corresponding to the reverse DNS lookup request. The central domain name service unit proceeds from the first level downwards, matching the address to be resolved with each associated subdomain service unit at the next lower level, and generating a response message containing the attribute parameters of the successfully matched subdomain service units. The matching subdomain service units then continue matching the address to be resolved with each associated subdomain service unit at the next lower level, until the lowest-level subdomain service unit is reached to query the reverse DNS lookup record matching the address to be resolved, and generates a response message containing the queried reverse DNS lookup record.

[0098] This method of resolving the address to be resolved by performing reverse lookup step by step through each level of domain name service unit reduces the load on the central domain name service unit, while also making reverse lookup faster and easier to manage.

[0099] In practice, the process of matching the address to be resolved with each subdomain service unit associated in the next level involves obtaining the first address prefix of the address block contained in each subdomain service unit associated in the next level, and obtaining the second address prefix corresponding to the address to be resolved in the next level. Each first address prefix is ​​then matched with the second address prefix. When any first address prefix matches the second address prefix, a response message containing the attribute feature parameters corresponding to the successfully matched subdomain service unit is generated.

[0100] Since address blocks at the same level have the same prefix boundary, the first address prefix of each subdomain service unit at the same level and the second address prefix of the address to be resolved can be obtained based on the bit length of the interval between the prefix boundaries. This facilitates matching and comparison and is highly efficient.

[0101] Furthermore, when any subdomain service unit at any level determines that each first address prefix and second address prefix fails to match, it queries the local domain name service unit for reverse resolution records that match the address to be resolved. If no reverse resolution record is found, a matching failure message is generated and returned to the local domain name service unit to terminate the reverse resolution process.

[0102] Based on this, when the local domain name service unit receives a matching failure message from any level of subdomain service unit, it indicates that the address requested for resolution by the edge terminal is not within the scope maintained by the hierarchical domain name service system. Therefore, it returns a notification to the edge terminal indicating that the reverse resolution has failed, thereby terminating the query.

[0103] Regarding the hierarchical resolution process described above, taking the address to be resolved as IP1 as an example, two specific resolution methods are given below:

[0104] The first method is iterative parsing:

[0105] (1) The local domain name service unit sends a reverse lookup request for IP1 to the central domain name service unit at the central level. The central domain name service unit queries and matches the first address prefix of the address blocks managed by each of its subordinate first-level subdomain name service units with the second address prefix of IP1 belonging to the first level. If a matching record is obtained, the central domain name service unit returns the deployment address of the first-level subdomain name service unit matched by IP1 and its corresponding attribute feature parameter 1 to the local domain name service unit. (2) The local domain name service unit receives the deployment address of the first-level subdomain name service unit matched by IP1 and its corresponding attribute feature parameter 1 returned by the central domain name service unit, and then sends a reverse lookup request for IP1 to the first-level subdomain name service unit. The first-level subdomain name service unit queries and matches the first address prefix of the address blocks managed by each of its subordinate second-level subdomain name service units with the second address prefix of IP1 belonging to the second level. If a matching record is obtained, the first-level subdomain name service unit returns the deployment address of the second-level subdomain name service unit matched by IP1 and its corresponding attribute feature parameter 2 to the local domain name service unit. (3) The local domain name service unit receives the deployment address of the second-level subdomain service unit that matches IP1 and its corresponding attribute feature parameter 2 returned by the first-level subdomain service unit. Then, it sends a reverse resolution request for IP1 to the second-level subdomain service unit. In this way, the local domain name service unit sends a reverse resolution request for IP1 to each lower-level subdomain service unit in turn. After multiple iterations of querying, it receives the reverse resolution domain record returned by the lowest-level subdomain service unit that matches IP1.

[0106] It is worth noting that during the reverse DNS lookup process, if a subdomain service unit at a certain level cannot obtain a matching record based on the address prefix matching method, it will use IP1 to match the reverse DNS lookup record in the locally stored reverse DNS lookup record. If a reverse DNS lookup record is matched, it means that the allocation of IP1 comes from the address block maintained by the subdomain service unit. This level is the lowest level of the reverse DNS lookup process.

[0107] The second method is recursive parsing:

[0108] First, the local domain name service unit forwards the reverse DNS lookup request for IP1 to the central domain name service unit at the central level. Then, proceeding sequentially from the central domain name service unit downwards, each level of subdomain name service unit matches the first address prefix of the address blocks handled by its subordinate subdomain name service units with the second address prefix corresponding to the level of IP1. It then forwards the reverse DNS lookup request to the next level of subdomain name service units that match IP1, continuing this process level by level until it reaches the subdomain name service unit at the level to which IP1 belongs, where the reverse DNS lookup for IP1 is completed. During this recursive query process, each level of subdomain name service unit also returns its corresponding attribute characteristic parameters to the local domain name service unit, until the lowest level subdomain name service unit returns the reverse DNS lookup record matching IP1, ending the recursive query process.

[0109] Step 403: Receive response information from the central domain name service unit and subdomain name service units at each level, and use the response information to generate reverse resolution records and send them to the edge terminal.

[0110] Based on the description of step 402 above, it can be seen that in the response messages returned by the central domain name service unit and the subdomain name service units at each level, some response messages contain the attribute feature parameters corresponding to the corresponding subdomain name service unit at the same level, and some response messages contain reverse resolution records. Therefore, the generated reverse resolution records include the identification information of the service terminal corresponding to the address to be resolved and the attribute feature parameters corresponding to the subdomain name service units at each level participating in reverse resolution.

[0111] It should be noted that after executing step 403, the local domain name service unit can also store the generated reverse resolution record so that it can directly return the result when other edge terminals request resolution in the future.

[0112] This completes the above. Figure 4 The reverse DNS lookup process shown involves the local DNS service unit (the DNS service unit closest to the deployment location of the terminal device) receiving a reverse DNS lookup request. If the local DNS service unit does not store the corresponding reverse DNS lookup record, it forwards the reverse DNS lookup request to the central DNS service unit. The central DNS service unit then performs the reverse DNS lookup of the address to be resolved through its subordinate DNS service units at various levels. This reduces the load on the central DNS service unit and makes the reverse DNS lookup process faster and easier to manage.

[0113] Furthermore, by adopting a layer-by-layer reverse resolution method, after the edge terminal receives the response returned by the local domain name service unit, it can not only obtain the unique identifier of the service terminal corresponding to the address to be resolved, but also obtain the set of attribute feature parameters corresponding to the service terminal. This provides a flexible reverse domain name resolution service, making the resolution results richer and easier to integrate into other application scenarios.

[0114] The hierarchical domain name system structure, address allocation method, and reverse address resolution method described in the above embodiments will be explained in detail below with a specific embodiment:

[0115] Assume the IPv6 address block obtained by the service provider from the RIR or ISP is 2001:db00:: / 24

[0116] Service providers are categorized into three tiers based on edge terminal attributes: city, owner, and hardware type. IPv6 address blocks are then divided according to these attribute tiers. The deployed hierarchical domain name service system structure is as follows:

[0117] Central Tier NS: Service Provider: XX Company 2001:db00:: / 24

[0118] First-level NS, City: Shenzhen 2001:db01:: / 32

[0119] First-level NS, City: Beijing 2001:db02:: / 32

[0120] First-level NS, City: Shanghai 2001:db03:: / 32

[0121] ...

[0122] Second-tier NS, owned by the main entity (Shenzhen branch): Company A 2001:db01:1:: / 48

[0123] The second-tier NS, owned by the main entity (subsidiary in Shenzhen): Company B 2001:db01:2:: / 48

[0124] The second-tier NS, owned by the main entity (subsidiary in Shenzhen): Company C 2001:2001:db01:3:: / 48

[0125] ...

[0126] Access layer (NS), hardware type (company B): CAMERA 2001:db01:2:1:: / 64

[0127] Access layer (NS), hardware type (company B): LAMP 2001:db01:2:2:: / 64

[0128] Access layer (NS), hardware type (company B subsidiary): BIKE 2001:db01:2:3:: / 64

[0129] ...

[0130] Assume that Company B operates the BIKE1 terminal located in Shenzhen. Its terminal identification information includes: a unique hardware ID of CompanyB_BIKE_0000_0000_0000_0001; and a corresponding domain name of BIKE1.CompanyB.com.

[0131] When terminal BIKE1 goes online, it requests an IPv6 address binding from the control platform. Based on BIKE1's attribute parameters, the control platform assigns it the IPv6 address "2001:db01:2:3::1" and sends a registration notification to the NS (Network Service Provider) at the access layer corresponding to XX Company-Shenzhen-Company B-BIKE, notifying it to add BIKE1's terminal identification information and the assigned IPv6 address. The NS generates a forward resolution record (AAAA) from the terminal identification information to the IPv6 address and a reverse resolution record (PTR) from the IPv6 address to the terminal identification information, which is displayed as follows:

[0132] The IPv6 address binding for terminal BIKE1 is completed by writing "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.3.0.0.0.2.0.0.0.1.0.bd1.0.0.2.IP6.ARPA".

[0133] The process by which any edge terminal requests reverse resolution of the IPv6 address "2001:db01:2:3::1" is as follows:

[0134] 1. The edge terminal sends a reverse DNS lookup request for the IPv6 address "2001:db01:2:3::1" to the local domain name service unit (hereinafter referred to as Local_NS). Local_NS does not find a matching PTR record locally, so it forwards the reverse DNS lookup request to the central NS.

[0135] 2. The central-level NS uses the first-level address prefix "2001:db01::" corresponding to the IPv6 address to match the address prefix of the address block managed by each first-level NS in the local record, and obtains the matching result with the address block maintained by the Shenzhen NS. Then, the central-level NS returns the deployment address and city code of the Shenzhen NS to Local_NS.

[0136] 3. Local_NS forwards the reverse lookup request to Shenzhen NS. Shenzhen NS uses the second-level address prefix "2001:db01:2::" corresponding to the IPv6 address to match the address prefixes of the address blocks managed by each second-level NS in its local records. It obtains the matching result with the address block maintained by the NS to which Company B belongs. Then, Shenzhen NS returns the deployment address and company code of the NS to which Company B belongs to Local_NS.

[0137] 4. Local_NS continues to forward the reverse lookup request to the NS to which Company B belongs. The NS to which Company B belongs uses the third-level address prefix "2001:db01:2:3::" corresponding to the IPv6 address to match the address prefixes of the address blocks managed by each NS at the next lower third level (i.e., the access level) recorded locally, and obtains the matching result with the address block maintained by the NS to which the terminal type BIKE belongs. Then, the NS to which Company B belongs returns the deployment address of the NS to which BIKE belongs and the terminal type code to Local_NS.

[0138] 5. Local_NS sends a reverse lookup request to the NS to which BIKE belongs. The NS to which BIKE belongs matches the IPv6 address "2001:db01:2:3::1" with its stored reverse lookup domain record. The reverse lookup obtains the terminal identification information corresponding to the IPv6 address, including the terminal hardware ID and domain name. Then, the NS to which BIKE belongs returns the resolution result to Local_NS.

[0139] 6. Local_NS packages the received parsing results and the terminal attribute feature parameters obtained from each upper-level NS into a response message and returns it to the edge terminal.

[0140] 7. The edge terminal parses the received response message and obtains the parsing result as follows:

[0141] The IPv6 address “2001:db01:2:3::1” corresponds to the terminal hardware ID CompanyB_BIKE_0000_0000_0000_0001, the domain name BIKE1.CompanyB.com, and has the following attribute characteristics: [Deployment location: Shenzhen; Owner: Company B; Hardware type: BIKE].

[0142] Corresponding to the embodiments of the aforementioned address allocation method, the present invention also provides embodiments of an address allocation device.

[0143] Figure 5 This is a schematic diagram illustrating the structure of an address allocation device according to an exemplary embodiment of the present invention. This device is used to execute the address allocation method provided in any of the above embodiments, such as... Figure 5 As shown, the address allocation device includes:

[0144] The request receiving module 510 is used to receive an address request sent by the edge terminal, the address request including the attribute feature parameters of the edge terminal;

[0145] Address allocation module 520 is used to determine the subdomain service unit corresponding to the attribute feature parameter from the subdomain service units at each level recorded locally, and allocate a free address to the edge terminal from the address block included in the determined subdomain service unit.

[0146] The registration module 530 is used to send a registration notification containing the address and the identification information of the edge terminal to the determined subdomain service unit, so that the subdomain service unit can use the address and the identification information to establish a reverse domain record.

[0147] The specific implementation process of the functions and roles of each unit in the above device can be found in the implementation process of the corresponding steps in the above method, and will not be repeated here.

[0148] Corresponding to the aforementioned embodiments of the reverse address resolution method, the present invention also provides embodiments of the reverse address resolution apparatus.

[0149] Figure 6 This is a schematic diagram illustrating the structure of a reverse address resolution apparatus according to an exemplary embodiment of the present invention. This apparatus is used to execute the reverse address resolution method provided in any of the above embodiments, such as... Figure 6 As shown, the reverse address resolution device includes:

[0150] The request receiving module 610 is used to receive a reverse address resolution request sent by the edge terminal, wherein the reverse address resolution request includes the address to be resolved;

[0151] The reverse resolution module 620 is used to forward the reverse address resolution request to the central domain name service unit when it is determined that the domain name service unit does not store a reverse resolution record corresponding to the address to be resolved, so that the central domain name service unit can perform reverse resolution on the address to be resolved through its subordinate subdomain name service units and generate response information corresponding to the reverse address resolution request.

[0152] The response feedback module 630 is used to receive response information from the central domain name service unit and the subdomain name service units at each level, and to use the response information to generate a reverse resolution record and send it to the edge terminal.

[0153] The reverse resolution record includes the identification information of the service terminal corresponding to the address to be resolved, as well as the attribute feature parameters corresponding to the subdomain service units at each level participating in the reverse resolution.

[0154] The specific implementation process of the functions and roles of each unit in the above device can be found in the implementation process of the corresponding steps in the above method, and will not be repeated here.

[0155] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of the present invention according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0156] The present invention also provides a server corresponding to the reverse address resolution method or address allocation method provided in the foregoing embodiments, for executing the above-described reverse address resolution method or address allocation method.

[0157] Figure 7 This is a hardware structure diagram of a server according to an exemplary embodiment of the present invention. The server includes: a communication interface 601, a processor 602, a memory 603, and a bus 604; wherein the communication interface 601, the processor 602, and the memory 603 communicate with each other through the bus 604. The processor 602 can execute the reverse address resolution method or address allocation method described above by reading and executing machine-executable instructions corresponding to the control logic of the reverse address resolution method or address allocation method in the memory 603.

[0158] The memory 603 mentioned in this invention can be any electronic, magnetic, optical, or other physical storage device, and can contain stored information such as executable instructions, data, etc. Specifically, the memory 603 can be RAM (Random Access Memory), flash memory, storage drive (such as hard disk drive), any type of storage disk (such as optical disc, DVD, etc.), or similar storage media, or combinations thereof. Communication between this system network element and at least one other network element is achieved through at least one communication interface 601 (which can be wired or wireless), and the Internet, wide area network, local area network, metropolitan area network, etc., can be used.

[0159] Bus 604 can be an ISA bus, PCI bus, or EISA bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. The memory 603 is used to store programs, and the processor 602 executes the programs after receiving execution instructions.

[0160] Processor 602 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by the integrated logic circuitry in the hardware of processor 602 or by instructions in software form. The processor 602 can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it can also be a Digital Signal Processor (DSP), an Application-Specific Integrated Circuit (ASIC), an On-Premises Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor.

[0161] The server provided in this application embodiment and the reverse address resolution method or address allocation method provided in this application embodiment are based on the same inventive concept and have the same beneficial effects as the methods they adopt, operate or implement.

[0162] This application also provides a computer-readable storage medium corresponding to the reverse address resolution method or address allocation method provided in the foregoing embodiments. Please refer to... Figure 8 As shown, the computer-readable storage medium is an optical disc 30, on which a computer program (i.e., a program product) is stored. When the computer program is run by a processor, it executes the reverse address resolution method or address allocation method provided in any of the foregoing embodiments.

[0163] It should be noted that examples of the computer-readable storage medium may also include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other optical and magnetic storage media, which will not be elaborated here.

[0164] The computer-readable storage medium provided in the above embodiments of this application and the reverse address resolution method or address allocation method provided in the embodiments of this application are based on the same inventive concept and have the same beneficial effects as the methods adopted, run or implemented by the applications stored therein.

[0165] This application also provides a computer program product corresponding to the data transmission method provided in the foregoing embodiments, including a computer program that is executed by a processor to implement the reverse address resolution method or address allocation method provided in any of the foregoing embodiments.

[0166] Other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of the invention are indicated by the following claims.

[0167] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0168] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A reverse address resolution method, characterized in that, Applied to a domain name service unit, the method includes: Receive a reverse address resolution request sent by an edge terminal, the reverse address resolution request including the address to be resolved; If it is determined that the domain name service unit does not store a reverse resolution record corresponding to the address to be resolved, the reverse address resolution request is forwarded to the central domain name service unit, so that the central domain name service unit performs reverse resolution on the address to be resolved through its subordinate subdomain name service units at each level, and generates response information corresponding to the reverse address resolution request. Receive response information from the central domain name service unit and subdomain name service units at each level, and use the response information to generate a reverse resolution record and send it to the edge terminal; The reverse resolution record includes the identification information of the service terminal corresponding to the address to be resolved and the attribute feature parameters corresponding to the subdomain service units at each level participating in the reverse resolution. The central domain name service unit performs reverse DNS lookup on the address to be resolved through its subordinate subdomain name service units at each level, and generates response information corresponding to the reverse address resolution request, including: The central domain name service unit proceeds from the first level downwards, matching the address to be resolved with each associated subdomain service unit in the next level through the subdomain service units at each level, and generating a response message containing the attribute feature parameters corresponding to the successfully matched subdomain service units. The central domain name service unit then continues to match the address to be resolved with each associated subdomain service unit in the next level through the successfully matched subdomain service units. The process continues until the lowest-level subdomain service unit matches the reverse domain record that matches the address to be resolved, and a response message containing the queried reverse domain record is generated.

2. The method according to claim 1, characterized in that, The step of determining that the domain name service unit does not store a reverse resolution record corresponding to the address to be resolved includes: Search for the reverse solution record corresponding to the address to be resolved in the locally cached reverse solution records; If not found, it is determined that the domain name service unit does not store the reverse resolution record corresponding to the address to be resolved.

3. The method according to claim 1, characterized in that, The address to be resolved is matched with each associated subdomain service unit in the next level through subdomain service units at each level, and a response message containing the attribute feature parameters corresponding to the successfully matched subdomain service units is generated, including: Obtain the first address prefix of the address block contained in each subdomain service unit associated in the next level, and obtain the second address prefix corresponding to the address to be resolved in the next level; Each first address prefix is ​​matched with the second address prefix; When any of the first address prefixes successfully matches the second address prefix, a response message is generated containing the attribute feature parameters corresponding to the successfully matched subdomain service unit.

4. The method according to claim 3, characterized in that, The method further includes: When any subdomain service unit at any level determines that each first address prefix and the second address prefix fail to match, it queries locally for the reverse domain record that matches the address to be resolved. If no reverse domain record is found, a matching failure message is generated.

5. The method according to claim 4, characterized in that, The method further includes: If a matching failure message is received, a notification indicating that reverse parsing failed is returned to the edge terminal.

6. An address allocation method, characterized in that, A control platform applied to a hierarchical domain name service system, the method comprising: Receive an address request sent by an edge terminal, the address request including attribute feature parameters of the edge terminal; From the subdomain service units at each level recorded locally, determine the subdomain service unit corresponding to the attribute feature parameter, and allocate a free address to the edge terminal from the address block included in the determined subdomain service unit; A registration notification containing the address and the identification information of the edge terminal is sent to the determined subdomain service unit so that the subdomain service unit can establish a reverse domain record using the address and the identification information.

7. A hierarchical domain name service system, characterized in that, The system includes a control platform, a central domain name service unit, and subdomain name service units at various levels. Each level has at least one subdomain service unit. The subdomain service unit contains the attribute feature parameters and address blocks of the corresponding level. The subdomain service unit is associated with at least one subdomain service unit in the next level, and the subdomain service unit records the attribute feature parameters and address blocks of each subdomain service unit associated with it in the next level. The control platform is used to allocate idle addresses to edge terminals according to the attribute feature parameters of the edge terminals, and send the addresses and the identification information of the edge terminals to the subdomain service unit corresponding to the attribute feature parameters for registration.

8. The system according to claim 7, characterized in that, When the attribute feature parameters of subdomain service units at all levels belong to the same attribute type, the attribute feature parameters of the next level subdomain service unit are sub-attributes of the attribute feature parameters of the previous level. The subdomain service unit corresponding to the attribute feature parameter of the upper level is associated with the subdomain service unit of the lower level.

9. The system according to claim 7, characterized in that, The address blocks contained in the next level of subdomain service unit are sub-address blocks of the address blocks in the previous level. The subdomain service unit to which the address block at the upper level belongs is associated with the subdomain service unit at the lower level.

10. The system according to claim 7, characterized in that, Address blocks belonging to the same level have the same address prefix length.

11. A reverse address resolution device, characterized in that, Applied to a domain name service unit, the device includes: The request receiving module is used to receive a reverse address resolution request sent by the edge terminal, wherein the reverse address resolution request includes the address to be resolved; The reverse resolution module is used to forward the reverse address resolution request to the central domain name service unit when it is determined that the domain name service unit does not store a reverse resolution record corresponding to the address to be resolved, so that the central domain name service unit can perform reverse resolution on the address to be resolved through its subordinate subdomain name service units and generate response information corresponding to the reverse address resolution request. The response feedback module is used to receive response information from the central domain name service unit and the subdomain name service units at each level, and to use the response information to generate a reverse resolution record and send it to the edge terminal. The reverse resolution record includes the identification information of the service terminal corresponding to the address to be resolved and the attribute feature parameters corresponding to the subdomain service units at each level participating in the reverse resolution. The reverse parsing module is specifically used for: The central domain name service unit proceeds from the first level downwards, matching the address to be resolved with each associated subdomain service unit in the next level through the subdomain service units at each level, and generating a response message containing the attribute feature parameters corresponding to the successfully matched subdomain service units. The central domain name service unit then continues to match the address to be resolved with each associated subdomain service unit in the next level through the successfully matched subdomain service units. The process continues until the lowest-level subdomain service unit matches the reverse domain record that matches the address to be resolved, and a response message containing the queried reverse domain record is generated.

12. An address allocation device, characterized in that, A control platform applied to a hierarchical domain name service system, the device comprising: A request receiving module is used to receive an address request sent by an edge terminal, the address request including attribute feature parameters of the edge terminal; The address allocation module is used to determine the subdomain service unit corresponding to the attribute feature parameter from the subdomain service units at each level recorded locally, and allocate a free address to the edge terminal from the address block included in the determined subdomain service unit. The registration module is used to send a registration notification containing the address and the identification information of the edge terminal to the determined subdomain service unit, so that the subdomain service unit can use the address and the identification information to establish a reverse domain record.

13. A server, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, implements the method as described in any one of claims 1-5 or claim 6.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that is read and executed by a processor to implement the method as described in any one of claims 1-5 or claim 6.

15. A computer program product, comprising a computer program, characterized in that, The computer program is executed by a processor to implement the method as described in any one of claims 1-5 or claim 6.

Images