CN-115668889-B - Domain Name System (DNS) service for Variable Length Address (VLA) networks

Abstract

A DNS server includes 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 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 may be further configured to cache a correspondence between the domain name, the address, and the scope.

Inventors

• QU YINGZHEN
• SONG HAOYU
• MICHAEL MCBRIDE
• JAMES N GUICHARD

Assignees

• 华为技术有限公司

Dates

Publication Date

20260508

Application Date

20210511

Priority Date

20200521

Claims (18)

1. 1. A Domain Name System (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, the scope defining a domain in which a website can be accessed; a processor coupled to the receiver and configured to execute computer instructions that cause the processor to: assigning an address to the domain name based on the local address and the scope, Generating a registration response including the address; a transmitter is coupled to the processor and configured to transmit the registration response to the endpoint.
2. 2. The DNS server according to claim 1, wherein the domain name is a name of a website.
3. 3. The DNS server according to claim 2, wherein the local address is an address of a Web server storing, processing and transmitting the Web site.
4. 4. A DNS server according to any of the claims 1 to 3, characterized in that the scope is an address length.
5. 5. A DNS server according to any of claims 1 to 3, wherein the address length is 8 bits, 16 bits or 24 bits.
6. 6. A DNS server according to any of claims 1 to 3, wherein the DNS server is in a domain, wherein the endpoint is in a subdomain of the domain, the address comprising a domain address of the subdomain.
7. 7. A DNS server according to any of claims 1 to 3, wherein the DNS server is in a domain, wherein the endpoint is in the domain, the address not comprising a domain address.
8. 8. A DNS server according to any of the claims 1 to 3, wherein the processor is further configured to execute the computer instructions, the computer instructions causing the processor to cache the correspondence between the domain name, the address and the scope.
9. 9. A method implemented by a Domain Name System (DNS) server, comprising: Receiving a registration request comprising a domain name, a local address and a scope, the registration request requesting registration of the domain name, the scope defining a domain in which a website can be accessed; Assigning an address to the domain name based on the local address and the scope; Generating a registration response including the address; The registration response is sent to the endpoint.
10. 10. The method of claim 9, wherein the domain name is a name of a website.
11. 11. The method of claim 10, wherein the local address is an address of a Web server that stores, processes, and transmits the Web site.
12. 12. The method according to any of claims 9 to 11, wherein the scope is an address length.
13. 13. The method according to any one of claims 9 to 11, wherein the address length is 8 bits, 16 bits or 24 bits.
14. 14. The method of any of claims 9 to 11, wherein the DNS server is in a domain, wherein the endpoint is in a subdomain of the domain, and wherein the address comprises a domain address of the subdomain.
15. 15. The method of any of claims 9 to 11, wherein the DNS server is in a domain, wherein the endpoint is in the domain, and wherein the address does not include a domain address.
16. 16. The method of any of claims 9 to 11, further comprising caching a correspondence between the domain name, the address, and the scope.
17. 17. An endpoint, comprising: A processor for executing computer instructions that cause the processor to generate a query comprising a domain name and a scope, the domain name being a name of a website, the scope defining a domain in which the query is valid, the query requesting an address corresponding to the domain name; A sender coupled to the processor and configured to send the query to a Domain Name System (DNS) server, the DNS server being a highest level DNS server in a highest level domain in a variable length address VLA network or a local DNS server, the DNS server being configured to perform the method of any of claims 9-16 upon DNS registration.
18. 18. A method implemented by an endpoint, comprising: Generating a query comprising a domain name and a scope, wherein the domain name is the name of a website, the scope defines a domain in which the query is valid, and the query requests an address corresponding to the domain name; the query is sent to a Domain Name System (DNS) server, which is a highest level DNS server in a highest level domain in a variable length address VLA network or a local DNS server, for performing the method of any of claims 9-16 at DNS registration.

Description

Domain Name System (DNS) service for Variable Length Address (VLA) networks Cross Reference to Related Applications The present application claims priority from U.S. provisional patent application No. 63/028,363, filed 5/21 in 2020, which is incorporated herein by reference. Technical Field The disclosed embodiments relate generally to DNS and, more particularly, to DNS services for VLA networks. Background IPvn is a protocol defining internet services for VLA networks. The VLA network includes domains organized in a hierarchy such that there is a top-level domain, a first-level domain in the top-level domain, a second-level domain in the first-level domain, and so on. Entities in the same domain communicate using a local address. But entities in different domains communicate using addresses including local addresses and domain addresses sharing higher-level domains. These domain addresses may be appended before or after the local address. The change in address length provides more available addresses for each domain. Furthermore, the header may use smaller addresses, particularly in the low-level domain, thereby reducing message processing time and saving device power. Disclosure of Invention A first aspect relates to a DNS server comprising a receiver for receiving a registration request comprising 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 comprising the address, and a transmitter coupled to the processor and configured to transmit the registration response to an endpoint. In an embodiment, there is one DNS server in each domain. In this context, a domain is defined as a collection of network entities running a common routing protocol, controlled by a single administrative authority, and having the same address length. Entities include devices, services, and other resources. The device includes an endpoint, a Web server, a router, and a DNS server. Each DNS server knows its own address and knows the address of the domain above its domain and thus the prefix. For DNS registration, the Web server registers its domain name to the highest level DNS server in the highest level domain allowed or to a local DNS server in its own domain. In the latter case, the local DNS server immediately reports its registration to the higher level DNS server, up to the highest level DNS server, or at the time of query. For DNS queries, like other DNS services, a host initiates a recursive query, where DNS performs most of the work, or initiates an iterative query, where the host performs most of the work. But unlike other DNS services, the host sends the query to the highest level DNS server or local DNS server. Although correspondence or mapping between domain names, addresses, and scopes is discussed, similar concepts may be applicable to other DNS services or other non-DNS services. Optionally, in any of the above aspects, the domain name is a name of a website. Optionally, in any of the above aspects, the local address is an address of a Web server storing, processing and transmitting the website. Optionally, in any of the above aspects, the scope defines a domain that can access the website. Optionally, in any of the above aspects, the scope is an address length. Optionally, in any of the above aspects, the address length is 8 bits, 16 bits, or 24 bits. Optionally, in any of the above aspects, the DNS server is in a domain, wherein the endpoint is in a subdomain of the domain, and the address comprises a domain address of the subdomain. Optionally, in any of the above aspects, the DNS server is in a domain, wherein the endpoint is in the domain, and the address does not include a domain address. Optionally, in any of the above aspects, the processor is further configured to execute the computer instructions, the computer instructions causing the processor to cache a correspondence between the domain name, the address, and the scope. A second aspect relates to a method implemented by a DNS server, the method comprising receiving a registration request comprising 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 comprising the address, and sending the registration response to an endpoint. Optionally, in any of the above aspects, the domain name is a name of a website. Optionally, in any of the above aspects, the local address is an address of a Web server storing, processing and transmitting the website. Optionally, in any of the above aspects, the scope defines a domain that can access the website. Optionally, in any of the above aspects, the scope is