Domain name system (DNS) service for variable length address (VLA) networks

Abstract

A DNS server includes a receiver configured to receive a registration request including a domain name, a local address, and a scope, the registration request requesting registration of the domain name; a processor coupled to the receiver and configured to execute computer instructions that cause the processor to assign an address to the domain name based on the local address and the scope, and generate a registration response including the address; and a transmitter coupled to the processor and configured to transmit the registration response to an endpoint. The processor can also be configured to cache a correspondence between the domain name, the address, and the scope.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 028,363, filed May 21, 2020, which is incorporated herein by reference. Technical Field

[0003] The disclosed embodiments generally relate to DNS, and more specifically to DNS services for VLA networks. Background Technology

[0004] IPvn is a protocol that defines Internet services for Virtual Area Networks (VLAs). A VLA network consists of domains organized in a hierarchical structure, such as a top-level domain, first-level domains within that top-level domain, second-level domains within that first-level domain, and so on. Entities within the same domain communicate using local addresses. However, entities in different domains communicate using addresses that include both local addresses and domain addresses that share higher-level domains. These domain addresses can be appended to the local addresses. This variation in address length provides more available addresses for each domain. Furthermore, headers can use smaller addresses, especially in lower-level domains, thus reducing message processing time and saving device power. Summary of the Invention

[0005] The first aspect relates to a DNS server, the DNS server comprising: a receiver for receiving a registration request including a domain name, a local address, and a scope, the registration request requesting registration of the domain name; a processor coupled to the receiver and configured to execute computer instructions, the computer instructions causing the processor to: allocate an address for the domain name based on the local address and the scope, and generate a registration response including the address; and a transmitter coupled to the processor and configured to send the registration response to an endpoint.

[0006] In this embodiment, there is one DNS server in each domain. In this context, a domain is defined as a collection of network entities that run a common routing protocol, are controlled by a single administrative body, and have the same address length. Entities include devices, services, and other resources. Devices include endpoints, web servers, routers, and DNS servers. Each DNS server knows its own address and the address of the domain above its own, thus knowing the prefix. For DNS registration, a web server registers its domain name with the highest-level DNS server in the highest-level allowed domain or with a local DNS server in its own domain. In the latter case, the local DNS server immediately reports its registration to higher-level DNS servers, all the way up to the highest-level DNS server, or performs the aforementioned reporting process upon receiving a query. For DNS queries, as with other DNS services, the host initiates a recursive query, where the DNS performs most of the work, or an iterative query, where the host performs most of the work. However, unlike other DNS services, the host sends the query to either the highest-level DNS server or the local DNS server. Although the correspondence or mapping between domain names, addresses, and scopes has been discussed, similar concepts may apply to other DNS services or other non-DNS services.

[0007] Alternatively, in any of the above aspects, the domain name is the name of a website.

[0008] Alternatively, in any of the foregoing aspects, the local address is the address of the web server that stores, processes, and transmits the website.

[0009] Alternatively, in any of the foregoing aspects, the scope defines the domains that can access the website.

[0010] Alternatively, in any of the above aspects, the scope is the address length.

[0011] Alternatively, in any of the above aspects, the address length is 8 bits, 16 bits, or 24 bits.

[0012] Optionally, in any of the foregoing aspects, the DNS server is in a domain, wherein the endpoint is in a subdomain of the domain, and the address includes the domain address of the subdomain.

[0013] Alternatively, in any of the foregoing aspects, the DNS server is in a domain, wherein the endpoint is in the domain, and the address does not include a domain address.

[0014] Optionally, in any of the foregoing aspects, the processor is further configured to execute the computer instructions that cause the processor to cache the correspondence between the domain name, the address, and the scope.

[0015] The second aspect relates to a method implemented by a DNS server, the method comprising: receiving a registration request including a domain name, a local address, and a scope, the registration request requesting registration of the domain name; assigning an address to the domain name based on the local address and the scope; generating a registration response including the address; and sending the registration response to an endpoint.

[0016] Alternatively, in any of the above aspects, the domain name is the name of a website.

[0017] Alternatively, in any of the foregoing aspects, the local address is the address of the web server that stores, processes, and transmits the website.

[0018] Alternatively, in any of the foregoing aspects, the scope defines the domains that can access the website.

[0019] Alternatively, in any of the above aspects, the scope is the address length.

[0020] Alternatively, in any of the above aspects, the address length is 8 bits, 16 bits, or 24 bits.

[0021] Optionally, in any of the foregoing aspects, the DNS server is in a domain, wherein the endpoint is in a subdomain of the domain, and the address includes the domain address of the subdomain.

[0022] Alternatively, in any of the foregoing aspects, the DNS server is in a domain, wherein the endpoint is in the domain, and the address does not include a domain address.

[0023] Optionally, in any of the above aspects, the method further includes caching the correspondence between the domain name, the address, and the scope.

[0024] The third aspect relates to an endpoint comprising: a processor for executing computer instructions that cause the processor to generate a query including a domain name and a scope, the domain name being the name of a website, the scope defining the domain for which the query is valid, and the query request being an address corresponding to the domain name; and a transmitter coupled to the processor for sending the query to a domain name system (DNS) server.

[0025] The fourth aspect relates to an endpoint-based method, the method comprising: generating a query including a domain name and a scope, the domain name being the name of a website, the scope defining the domains for which the query is valid, the query request being an address corresponding to the domain name; and sending the query to a domain name system (DNS) server.

[0026] Any of the above embodiments can be combined with any of the other embodiments to create new embodiments. These and other features will become clearer from the following detailed description taken in conjunction with the accompanying drawings and claims. Attached Figure Description

[0027] To gain a more complete understanding of the present invention, reference is made to the following brief description in conjunction with the accompanying drawings and specific embodiments, wherein the same reference numerals denote the same parts.

[0028] Figure 1 This is a schematic diagram of a VLA network, showing DNS registration and DNS queries from top to bottom.

[0029] Figure 2 This is a schematic diagram of a VLA network, showing push DNS registration and DNS queries.

[0030] Figure 3 This is a schematic diagram of a VLA network, showing DNS registration and DNS query pulling.

[0031] Figure 4 This is a flowchart of the DNS registration method.

[0032] Figure 5 This is a flowchart of the DNS query method.

[0033] Figure 6 This is a schematic diagram of the apparatus provided in an embodiment of the present invention. Detailed Implementation

[0034] First, it should be understood that although illustrative implementations of one or more embodiments are provided below, the disclosed systems and / or methods can be implemented using any number of techniques, whether currently known or existing. The invention is by no means limited to the illustrative implementations, drawings, and techniques described below, including the exemplary designs and implementations illustrated and described herein, but can be modified within the full scope of the appended claims and their equivalents.

[0035] The following abbreviations apply:

[0036] AS: Autonomous System

[0037] ASIC: Application-Specific Integrated Circuit

[0038] CPU: Central Processing Unit

[0039] DNS: Domain Name System

[0040] DNSEXT: DNS Extensions

[0041] DSP: Digital Signal Processor

[0042] EO: Electrical-to-optical

[0043] FPGA: Field-Programmable Gate Array

[0044] IESG: Internet Engineering Steering Group

[0045] IPv4: Internet Protocol version 4

[0046] IPv6: Internet Protocol version 6

[0047] IPvn: Internet Protocol version n

[0048] OE: Optical-to-Electrical

[0049] RAM: Random-access memory

[0050] RF: Radio frequency

[0051] RFC: Request for comments

[0052] ROM: Read-only memory

[0053] RX: Receiver unit

[0054] SRAM: Static RAM

[0055] TCAM: Ternary content-addressable memory

[0056] TX: Transmitter unit

[0057] VLA: Variable-length address.

[0058] DNS provides naming services for entities on a network. Entities register their names with a server, which assigns addresses to those names. When other entities query these names, the server responds with the corresponding address. Addresses are 32 bits in IPv4, 128 bits in IPv6, and variable length in IPvn. New DNS services are needed to support VLAs in VLA networks (such as IPvn).

[0059] This document discloses an embodiment of a DNS service for VLA networks. In this embodiment, there is one DNS server in each domain. In this context, a domain is defined as a collection of network entities that run a common routing protocol, are controlled by a single administrative body, and have the same address length. Entities include devices, services, and other resources. Devices include endpoints, web servers, routers, and DNS servers. Each DNS server knows its own address and the address of the domain above its own, thus knowing the prefix. For DNS registration, a web server registers its domain name with the highest-level DNS server in the highest-level allowed domain or with a local DNS server in its own domain. In the latter case, the local DNS server immediately reports its registration to higher-level DNS servers, all the way up to the highest-level DNS server, or performs the above reporting process upon receiving a query. For DNS queries, as with other DNS services, the host initiates a recursive query, where the DNS performs most of the work, or an iterative query, where the host performs most of the work. However, unlike other DNS services, the host sends the query to either the highest-level DNS server or the local DNS server. Although the correspondence or mapping between domain names, addresses, and scopes has been discussed, similar concepts may apply to other DNS services or other non-DNS services.

[0060] Figure 1 This is a schematic diagram 100 of a VLA network, showing top-down DNS registration and DNS lookups. VLA network 100 includes IPv6 domain 165 and domains 170, 175, 180, 185, and 190. In domains 170, 175, 180, 185, and 190, domain 170 is the top-level domain of IPvn, domains 175 and 180 are first-level domains, and domains 185 and 190 are second-level domains.

[0061] VLA network 100 is designated "VLA" because IPv6 domain 165 uses a 128-bit address, while domains 170, 175, 180, 185, and 190 use smaller address values. For example, domain 170 uses a 24-bit address; domains 175 and 180 use 16-bit addresses; and domains 185 and 190 use 8-bit addresses. Other address lengths below 128 bits, or address lengths specified by other protocols, are also possible. For example, 64 bits, 32 bits, and 4 bits are also possible.

[0062] Domains 170, 175, 180, 185, and 190 collectively include Web server 105; DNS servers 110, 120, 130, 140, and 195; routers 115, 125, 145, 150, 155, and 160; and endpoints 135 and 197. Web server 105 stores, processes, and transmits domains, web pages, or websites. DNS servers 110, 120, 130, 140, and 195 provide DNS services. DNS servers 110, 120, 140, and 195 are local DNS servers for entities within their respective domains 175, 180, 185, and 190. DNS server 130 is the top-level DNS server for IPvn. Although domains 170, 175, 180, 185, and 190 are shown as including one DNS server 130, 120, 195, 110, and 140 respectively, domains 170, 175, 180, 185, and 190 may include multiple DNS servers to provide redundancy in the event of a DNS server failure. Routers 115, 125, 145, 150, 155, and 160 forward messages between entities. Router 115 is the gateway to domain 185, router 125 is the gateway to domain 175, router 160 is the gateway to domain 170, router 150 is the gateway to domain 180, and router 145 is the gateway to domain 190. Endpoints 135 and 197 are mobile phones, computers, or other network-supported devices associated with the user.

[0063] For DNS registration, Web server 105 sends a registration request to the top-level DNS server (DNS server 130) via routers 115 and 125. Because Web server 105 registers directly with DNS server 130 and not with lower-level DNS servers, this DNS registration is called top-down registration. The registration request includes the domain name, local address, and scope. The registration request requests the registration of the domain name. The domain name is the name of the website that Web server 105 stores, processes, and transmits. For example, the domain name is example.com. The local address is the address of Web server 105 used to communicate with entities within domain 185. For example, the local address is 10. The scope defines the domains that can access the website. A scope can be defined by address length, domain name, or AS number. For example, the scope is a 24-bit address length so that domain 170, which uses a 24-bit address, and all subdomains of domain 170 (specifically domains 175, 180, 185, and 190) can access example.com. This means that all entities in domains 170, 175, 180, 185, and 190 can also access example.com. However, IPv6 domain 165, which uses a 128-bit address, cannot access example.com.

[0064] Registration requests can indicate the scope in the format specified in J. Damas et al., “Extended Mechanisms for DNS (EDNS(0))” (RFC 6891, April 2013). This format provides an option code field, an option length field, and an option data field. The option code field is assigned by an expert review process defined by the DNSEXT working group and IESG, and the option length field is the size of the option data field (in octets), which varies depending on the option code. For example, a registration request might indicate a 24-bit address length in the option data field.

[0065] In response to the registration request, DNS server 130 registers the domain name. Specifically, DNS server 130 determines the address based on the local address and the scope. For example, when the scope is a 24-bit address length, the address includes the local address of web server 105 and is appended to the domain addresses of all domains below domain 170 that use 24-bit addresses. Specifically, this address is appended to the domain addresses of domains 175 and 185. Therefore, the address is 40-10-10, where 40 is the domain address of domain 175, the middle 10 is the domain address of domain 185, and the rightmost 10 is the local address of web server 105. This address is unique within domain 170. DNS server 130 generates a registration response including the address and sends the registration response to web server 105 via routers 125 and 115. Finally, DNS server 130 caches the mapping between domain names, addresses, and scopes in a database.

[0066] In the first alternative, the scope is a 128-bit address length instead of 24 bits, and the web server 105 registers with the DNS server in IPv6 domain 165. Therefore, the address is unique within IPv6 domain 165 and includes the address 2001::40-10-10, where 2001 is the domain address of IPv6 domain 165, 40 is the domain address of domain 175, the middle 10 is the domain address of domain 185, and the rightmost 10 is the local address of the web server 105. In the second alternative, the scope is a 16-bit address length. Therefore, the address is unique within domain 175 and includes the domain address of domain 185, or the address is unique within domain 180 and includes the domain address of domain 190. In the third alternative, the scope is an 8-bit address length. Therefore, the address is unique within either domain 185 or domain 190 and does not include the domain address.

[0067] For DNS queries, endpoint 135 sends the query to the local DNS server (DNS server 140). The query includes the domain name and the scope. The query requests the address corresponding to the domain name. For example, the domain name is example.com. The scope defines the domains for which the query is valid. A scope can be defined by address length, domain name, or AS number. For example, a scope is a 24-bit address length so that the query is valid in domain 170, which uses 24-bit addresses, and all subdomains of domain 170 (specifically domains 175, 180, 185, and 190). However, the query is invalid in IPv6 domain 165, which uses 128-bit addresses. Therefore, if example.com is not hosted in domains 170, 175, 180, 185, or 190, but is hosted in IPv6 domain 165, no address should be returned in response to the query. The query can indicate the scope in the format described above.

[0068] DNS server 140 forwards the query to the top-level DNS server. For example, if the scope is a 24-bit address length, corresponding to domain 170, then DNS server 140 forwards the query to the DNS server in domain 170, specifically DNS server 130, via routers 145, 150, 155, and 160. DNS server 130 queries its database to find the address corresponding to the domain name, generates a query response including that address, and sends the response to DNS server 140 via routers 160, 155, 150, and 145. For example, the address is 40-10-10, as described above. DNS server 140 caches the mapping between domain names and addresses in its database. Finally, DNS server 140 forwards the query response to endpoint 135.

[0069] In the first alternative, DNS server 140 does not forward the query directly to DNS server 130 via routers 145, 150, 155, and 160. Instead, DNS server 140 forwards the query upwards to one domain at a time. Therefore, DNS server 140 first forwards the query to DNS server 195 via router 145, and then DNS server 195 forwards the query to DNS server 130 via routers 150, 155, and 160. In the second alternative, endpoint 197 sends a query to DNS server 110 via router 115, and DNS server 110 sends a query response to endpoint 197 via router 115. The address in the query response is 10 instead of 40-10-10 because the query originates from the same domain as DNS server 110, thus eliminating the need for addresses of domains 185 and 175. In the third alternative, the scope is a 128-bit address length, so endpoint 135 sends the query to DNS server 140, DNS server 140 forwards the query to the DNS server in IPv6 domain 165, the DNS server in IPv6 domain 165 sends the query response to DNS server 140, DNS server 140 forwards the query response to endpoint 135, and caches the mapping between domain names and addresses.

[0070] Figure 2 This is a schematic diagram of VLA network 200, illustrating push DNS registration and DNS queries. VLA network 200 is similar to VLA network 100, and the DNS registration and DNS queries described for VLA network 200 are similar to those described for VLA network 100. Specifically, VLA network 200 includes domains 255, 260, and 265. Within domains 255, 260, and 265, domain 260 is the top-level domain of IPvn and includes subdomains 255 and 265, which are first-level subdomains. Domains 255, 260, and 265 include endpoints 205 and 250; DNS servers 210, 225, and 245; a web server 215; and routers 220, 230, 235, and 240.

[0071] For DNS registration, web server 215 sends a registration request to DNS server 210, as described above. In response to the registration request, DNS server 210 performs the registration, generates a registration response, sends the registration response to web server 215, and caches the mapping between domain names, addresses, and scopes in the database, as described above. For example, since web server 215 and DNS server 210 are in the same domain 255, the address is 10, which is the local address of web server 215.

[0072] When the scope of the registration request indicates domain 260, DNS server 225 is the top-level DNS server. Therefore, DNS server 210 forwards or pushes the registration request to DNS server 225 via router 220. This push is called push registration. In response to the registration request, DNS server 225 generates a registration response, sends it to DNS server 210, and caches the mapping between domain names, addresses, and scopes in its database, as described above. For example, the address is 10-10, where the left 10 is the domain address of domain 260, and the right 10 is the local address of web server 215.

[0073] For DNS queries, when endpoint 205 sends a query to DNS server 210, DNS server 210 sends a query response with local address 10 to host 205. When endpoint 250 sends a query to DNS server 225 through DNS server 245 and router 240, DNS server 225 sends a query response with address 10-10 to endpoint 250 through DNS server 245 and router 240.

[0074] Figure 3 This is a schematic diagram 300 of a VLA network, illustrating DNS registration and DNS lookup. VLA network 300 is similar to VLA network 200, and the DNS registration and DNS lookup described for VLA network 300 are similar to those described for VLA network 200. Specifically, VLA network 300 includes domains 355, 360, and 365. Domains 355, 360, and 365 include endpoints 305 and 350; DNS servers 310, 325, and 345; a web server 315; and routers 320, 330, 335, and 340.

[0075] For DNS registration, web server 315 sends a registration request to DNS server 310, as described above. In response to the registration request, DNS server 310 performs the registration, generates a registration response, sends the response to web server 315, and caches the mapping between domain names, addresses, and scopes in its database, as described above. For example, the address is 10. However, DNS server 310 does not forward or push the registration request to DNS server 325 through router 320.

[0076] For DNS queries, when endpoint 305 sends a query to DNS server 310, DNS server 310 sends a query response with local address 10 to host 305. When endpoint 350 sends a query to DNS server 325 via DNS server 345 and router 340, DNS server 325 sends a query response with address 10-10 to endpoint 350 via router 340 and DNS server 345, and DNS server 345 caches the mapping between domain name, address, and scope. However, before DNS server 325 sends its query response, DNS server 325 forwards the query to DNS server 310 via router 320, and DNS server 310 sends a query response with address 10-10 to DNS server 325 via router 320, and DNS server 325 caches the mapping between domain name, address, and scope. Because the address is pulled from DNS server 310 to DNS server 325, this query is called a pull query.

[0077] Figure 4 This is a flowchart of DNS registration method 400. DNS server implementation method 400: In step 410, a registration request including a domain name, local address, and scope is received. The registration request requests the registration of the domain name. In step 420, an address is assigned to the domain name based on the local address and scope. In step 430, a registration response including the address is generated. In step 440, the registration response is sent to the endpoint.

[0078] Method 400 can implement additional embodiments. For example, a domain name is the name of a website. A local address is the address of a web server that stores, processes, and transmits the website. The scope defines the domains that can access the website. The scope is the address length. The address length can be 24 bits, 16 bits, or 8 bits. The DNS server is in the domain, the endpoint is in a subdomain of the domain, and the address includes the domain address of the subdomain. The DNS server is in the domain, the endpoint is in the domain, and the address does not include the domain address. The method also includes caching the mapping between domain names, addresses, and scopes.

[0079] Figure 5 This is a flowchart of DNS query method 500. Endpoint implementation method 500. In step 510, a query including the domain name and scope is generated. The domain name is the name of the website, and the scope defines the domains for which the query is valid. The query request corresponds to the address of the domain name. In step 520, the query is sent to the DNS server.

[0080] Figure 6This is a schematic diagram of a device 600 provided in one embodiment of the present invention. Device 600 can implement the disclosed embodiments. Device 600 includes: an input port 610 and an RX 620 or receiving module for receiving data; a processor 630 or processing module, or logic unit, baseband unit, or CPU for processing data; a TX 640 or transmitting module for transmitting data and an output port 650; and a memory 660 or data storage module for storing data. Device 600 may further include OE components, EO components, or RF components coupled to the input port 610, RX 620, TX 640, and output port 650 to provide input and output of optical signals, electrical signals, or RF signals.

[0081] Processor 630 is any combination of hardware, middleware, firmware, or software. Processor 630 includes any combination of one or more CPU chips, cores, FPGAs, ASICs, or DSPs. Processor 630 communicates with ingress port 610, RX 620, TX 640, egress port 650, and memory 660. Processor 630 includes DNS component 670 implementing the disclosed embodiments. Therefore, including DNS component 670 significantly improves the functionality of device 600 and enables transitions between different states of device 600. Alternatively, memory 660 stores DNS component 670 as instructions, and processor 630 executes these instructions.

[0082] Memory 660 includes any combination of disk, tape drive, or solid-state drive. Device 600 may use memory 660 as an overflow data storage device to store programs when device 600 selects them for execution, and to store instructions and data read by device 600 during the execution of these programs. Memory 660 may be volatile or non-volatile, and may be any combination of ROM, RAM, TCAM, or SRAM.

[0083] The computer program product may include computer-executable instructions stored in a non-transitory medium, which, when executed by a processor, cause the device to perform any embodiment. The non-transitory medium may be memory 660, the processor may be processor 630, and the device may be device 600.

[0084] In one embodiment, the DNS server includes a receiving module, a processing module coupled to the receiving module, and a sending module coupled to the processing module. The receiving module receives a registration request including a domain name, a local address, and a scope. The registration request requests the registration of a domain name. The processing module executes computer instructions that cause it to assign an address to the domain name based on the local address and scope, and generate a registration response including the address. The sending module sends the registration response to the endpoint.

[0085] While this invention provides several embodiments, it should be understood that the disclosed systems and methods can also be embodied in many other specific forms without departing from the spirit or scope of the invention. These examples are intended to be illustrative rather than restrictive and are not intended to be limited to the details given herein. For example, various elements or components may be combined or integrated into another system, or some features may be omitted or not implemented.

[0086] Furthermore, the technologies, systems, subsystems, and methods described and illustrated as discrete or separate in the various embodiments may be combined or integrated with other systems, components, technologies, or methods without departing from the scope of the invention. Coupling shown or described may be direct coupling or indirect coupling or communication via some interface, device, or intermediate component, either electrically, mechanically, or otherwise. Those skilled in the art can identify other examples of changes, substitutions, and modifications, and may make changes, substitutions, and modifications without departing from the spirit and scope of the invention.

Claims

1. A Domain Name System (DNS) server, characterized in that, include: A receiver is configured to receive a registration request that includes a domain name, a local address, and a scope, wherein the registration request requests the registration of the domain name and the scope defines the domains that can access the website; A processor, coupled to the receiver and used to execute computer instructions that cause the processor to: Assign an address to the domain name based on the local address and the scope. Generate a registration response including the stated address; A transmitter, coupled to the processor, is used to send the registration response to the endpoint.

2. The DNS server according to claim 1, characterized in that, The domain name is the name of the website.

3. The DNS server according to claim 2, characterized in that, The local address is the address of the web server that stores, processes, and transmits the website.

4. The DNS server according to any one of claims 1 to 3, characterized in that, The scope is the address length.

5. The DNS server according to any one of claims 1 to 3, characterized in that, The address length can be 8 bits, 16 bits, or 24 bits.

6. The DNS server according to any one of claims 1 to 3, characterized in that, The DNS server is in a domain, wherein the endpoint is in a subdomain of the domain, and the address includes the domain address of the subdomain.

7. The DNS server according to any one of claims 1 to 3, characterized in that, The DNS server is in a domain, wherein the endpoint is in the domain, and the address does not include the domain address.

8. The DNS server according to any one of claims 1 to 3, characterized in that, The processor is also configured to execute the computer instructions that cause the processor to cache the correspondence between the domain name, the address, and the scope.

9. A method implemented by a Domain Name System (DNS) server, characterized in that, include: Receive a registration request that includes a domain name, a local address, and a scope, wherein the registration request requests the registration of the domain name and the scope defines the domains that can access the website; Assign an address to the domain name based on the local address and the scope; Generate a registration response including the stated address; Send the registration response to the endpoint.

10. The method according to claim 9, characterized in that, The domain name is the name of the website.

11. The method according to claim 10, characterized in that, The local address is the address of the web server that stores, processes, and transmits the website.

12. The method according to any one of claims 9 to 11, characterized in that, The scope is the address length.

13. The method according to any one of claims 9 to 11, characterized in that, The address length can be 8 bits, 16 bits, or 24 bits.

14. The method according to any one of claims 9 to 11, characterized in that, The DNS server is in a domain, wherein the endpoint is in a subdomain of the domain, and the address includes the domain address of the subdomain.

15. The method according to any one of claims 9 to 11, characterized in that, The DNS server is in a domain, wherein the endpoint is in the domain, and the address does not include the domain address.

16. The method according to any one of claims 9 to 11, characterized in that, It also includes caching the correspondence between the domain name, the address, and the scope.

17. An endpoint, characterized in that, include: A processor for executing computer instructions that cause the processor to generate a query including a domain name and a scope, wherein the domain name is the name of a website, the scope defines the domain in which the query is valid, and the query request is an address corresponding to the domain name; A transmitter, coupled to the processor, is used to send the query to a domain name system (DNS) server; the DNS server is the highest-level DNS server in the highest-level domain of a variable-length address (VLA) network or a local DNS server, and the DNS server is used to perform the method of any one of claims 9-16 during DNS registration.

18. A method implemented by endpoints, characterized in that, include: Generate a query that includes a domain name and a scope, where the domain name is the name of the website, the scope defines the domains for which the query is valid, and the query request corresponds to the address of the domain name; The query is sent to a Domain Name System (DNS) server; the DNS server is the highest-level DNS server in the highest-level domain of a Variable Length Address (VLA) network or a local DNS server, and the DNS server is used to execute the method of any one of claims 9-16 during DNS registration.

Images