In the embodiment of the present disclosure, the edge private network domain name system console delivers the configuration information to the resolver, so that the resolver can accurately perceive which domain name resolution requests may be sent to the authoritative DNS for resolution, and which domain name resolution requests cannot be resolved through the authoritative DNS but can only be sent to the external network for iterative resolution. Through the process that the edge private network domain name system console receives the configuration information configured by the user, delivers the configuration information and makes the configuration information effective, the reliability and flexibility of the domain name resolution process can be effectively improved.

Step S102, converting the first domain name resolution request into a second domain name resolution request, and sending the second domain name resolution request to an authoritative domain name system, wherein the authoritative domain name system is deployed on a second physical machine, and the second physical machine is disposed in a second edge computer room.

The authoritative domain name system deployed on the second physical machine can provide a domain name resolution resource for the virtual device on the first physical machine, and the domain name resolution resource is specifically provided as a shared resource to the virtual machines deployed in the first edge computer room.

The second edge computer room in this embodiment is an edge computer room in an edge computing scenario, and the second edge computer room and the first edge computer room are two independent computer rooms, and the second physical machine in the second edge computer room is communicatively connected to the first physical machine in the first edge computer room. The communication between the first edge computer room and the second edge computer room may be achieved through a leased line or an external network. For example, in the case of the external network, if there is a VPN, the first edge computer room and the second edge computer room may be connected through the VPN. In addition, in this embodiment, the communication data message may be encrypted, and the encryption method may be selected from the related art. The authoritative domain name system in this embodiment, that is, the authoritative DNS, is a server responsible for private network domain name resolution.

In some optional implementations, the second edge computer room is, for example, a central computer room in a central cloud computing scenario, and the second edge computer room in this embodiment is a computer room with high stability. Optionally, the authoritative domain name system in the second edge computer room may reuse the private network authoritative DNS resource of the central computer room.

In some optional implementations, there are at least two second edge computer rooms, which may include, for example, a second edge computer room Y and a second edge computer room Z shown in FIG. 5.

In the embodiments of the present disclosure, the reliability of the response to the domain name resolution request is improved through at least two second edge computer rooms. Even if one of the second edge computer rooms has an unexpected failure, the authoritative DNS resource may still be provided through the second edge computer room without failure, so that the continuity and reliability of the service are guaranteed.

As shown in FIG. 5, the resolver in this embodiment may be, for example, a resolver P (Resolver) or a resolver Q (Resolver). The resolver P (Resolver) is configured to convert the first domain name resolution request sent by a network module M (vSwitch) into a second domain name resolution request, and the resolver Q (Resolver) is configured to convert the first domain name resolution request sent by a network module N (vSwitch) into a second domain name resolution request. Next, the resolver P (Resolver) or the resolver Q (Resolver) is configured to send the second domain name resolution request to the corresponding authoritative DNS. The authoritative DNS includes, for example, an authoritative DNS 11, an authoritative DNS 12, and an authoritative DNS 13 deployed in the second edge computer room Y, and/or an authoritative DNS 14, an authoritative DNS 15, and an authoritative DNS 16 deployed in the second edge computer room Z. Therefore, the Resolver in this embodiment can connect a virtual network and a physical network, and use the physical network to carry DNS data and interact with the authoritative DNS.

In some optional implementations, the sending the second domain name resolution request to the authoritative domain name system includes: sending the second domain name resolution request to a load balance device, wherein the load balance device is configured to allocate the second domain name resolution request to the authoritative domain name system.

In this embodiment, the access to the authoritative domain name system may be responsible for the load balance device, and the external network IP (Internet Protocol) of the load balance device may publish an anycast address (the same IP), so that disaster recovery and local access can be achieved.

As shown in FIG. 5, for the process that the resolver P (Resolver) or the resolver Q (Resolver) sends the second domain name resolution request to the corresponding authoritative DNS, in this embodiment, multiple second domain name resolution requests may be shunted through the load balance device R (LB, Load Balance) or the load balance device S (LB), so that the second domain name resolution requests are distributed to the corresponding authoritative DNS, such as any one of the DNS 11, the authoritative DNS 12, the authoritative DNS 13, the authoritative DNS 14, the authoritative DNS 15, and the authoritative DNS 16. The load balance device in this embodiment may be deployed on a third physical machine in the second edge computer room, and the third physical machine is the same as or different from the second physical machine. The specific process of distributing the multiple second domain name resolution requests to the authoritative DNS through the load balance method may be selected from related solutions, and will not be repeated.

In the embodiments of the present disclosure, the load balance device is used for distributing the second domain name resolution requests. Even in the case of a large number of second domain name resolution requests and a high concurrency, the load of each authoritative DNS can still be reasonably adjusted, so that the authoritative DNS resources can be fully utilized to ensure the high availability of the authoritative DNS.

In some optional implementations, in the process of sending the second domain name resolution request to the corresponding authoritative DNS, the resolver in this embodiment may forward the second domain name resolution request through the network address translation device (NAT, Network Address Translation) shown in FIG. 5, so that the second domain name resolution request is first sent to the load balance device, and then the load balance device distributes the second domain name resolution request to the corresponding authoritative DNS.

Step S103, receiving a resolution result of the second domain name resolution request by the authoritative domain name system, and forwarding the resolution result to the virtual device through the network module.

In this embodiment, the authoritative domain name system can resolve the received second domain name resolution request to obtain the resolution result. The authoritative domain name system can parse a VNI from the second domain name resolution request, and perform the tenant-isolated domain name resolution according to the VNI. The resolution result may be a DNS data packet.

In some optional implementations, while converting the first domain name resolution request into the second domain name resolution request, the domain name resolution method further includes: maintaining a session connection between the resolver and the network module.

Specifically, in this embodiment, the session connection between the resolver and the network module is maintained by storing quintuple data in the first domain name resolution request, and then the original session connection may be found by receiving the quintuple data of the message when responding to the first domain name resolution request.

In some optional implementations, the forwarding the resolution result to the virtual device through the network module includes: forwarding the resolution result to the virtual device through the network module based on the session connection between the resolver and the network module.

The session connection between the resolver and the network module may be achieved by acquiring the pre-stored quintuple data in the first domain name resolution request.

In this embodiment, the resolution result is fed back by maintaining an existing session connection, so that the communication efficiency is improved, and the response result is guaranteed to be accurately sent to the virtual machine that sends the corresponding private network domain name resolution request.

The domain name resolution method for edge computing provided in this embodiment is specifically a method for implementing a private network DNS applied in an edge computing scenario. In this embodiment, the resolver deployed on the first physical machine in the first edge computer room is used for converting the first domain name resolution request forwarded by the virtual device through the network module, and send the second domain name resolution request obtained through conversion to the authoritative domain name system deployed on the second physical machine in the second edge computer room for resolution, and send the resolution result fed back by the authoritative domain name system to the virtual device. It can be seen that in the solution for domain name resolution provided in this embodiment, the authoritative domain name system and the virtual device resource are deployed separately on the basis of implementing the function of domain name resolution, so that the case where a set of domain name system is deployed for each edge computer room is avoided, and the problems in the related art that the scale of the domain name system in the edge cloud computing scenario is large, the maintenance is difficult, and the deployment cost is high are effectively overcome. Compared with the related art, this embodiment can greatly reduce the scale of the domain name system, reduce the difficulty of maintenance, and reduce the deployment cost in the edge cloud computing scenario.

In this embodiment, a domain name resolution method for edge computing is provided, which can be applied to a resolver. FIG. 2 is a flowchart of a domain name resolution method for edge computing according to an embodiment of the present disclosure. As shown in FIG. 2, the process includes the following steps.

Step S201, acquiring a first domain name resolution request forwarded by a virtual device through a network module, wherein the virtual device, the network module, and the resolver are deployed on a first physical machine, and the first physical machine is disposed in a first edge computer room. The first domain name resolution request is a virtual extensible local area network (VXLAN) message.

In some optional implementations, the network module is a virtual switch (vSwitch), and the virtual switch is configured to encapsulate a domain name resolution message sent by the virtual device into a virtual extensible local area network (VXLAN) message. The domain name resolution message is the private network domain name resolution request.

The virtual machine in this embodiment may encapsulate the domain name resolution message through a customized protocol or an extended domain name resolution protocol to obtain the virtual extensible local area network message, and the virtual extensible local area network message is the first domain name resolution request.

As shown in FIG. 6, taking encapsulating the domain name resolution message through the extended domain name resolution protocol as an example, the structure of the obtained virtual extensible local area network message includes: an outer Ethernet header (Outer Ethernet header), an outer IP header (Outer IP header), an outer UDP header (Outer UDP header), a VXLAN header (VXLAN header), an inner Ethernet header (Inner Ethernet header), an inner IP header (Inner IP header), and a domain name resolution payload (DNS Payload). The VXLAN header (VXLAN header) includes a flag (Flags), a first reserved bit (Reserved), a virtual extensible local area network identifier (VNI), and a second reserved bit (Reserved). The length of the first reserved bit (Reserved) is greater than the length of the second reserved bit (Reserved), and the functions of each part in the structure of the virtual extensible local area network message may be referred to the EDNS protocol, which will not be repeated.

In this embodiment, the network module implemented through the vSwitch supports configuration of more virtual devices, and has the advantages of strong expandability, high performance, and low cost, so that the solution in this embodiment can be better adapted to the private network DNS resolution in the edge cloud computing scenario.

Step S202, converting the first domain name resolution request into a second domain name resolution request, and sending the second domain name resolution request to an authoritative domain name system, wherein the authoritative domain name system is deployed on a second physical machine, and the second physical machine is disposed in a second edge computer room.

Specifically, the above step S202 includes the following steps.

Step S2021, parsing outer network information, a virtual extensible local area network identifier, and message payload information from the virtual extensible local area network message.

As shown in FIG. 6, the outer network information includes an outer Ethernet header (Outer Ethernet header) and an outer IP header (Outer IP header), and the message payload information includes a domain name resolution payload (DNS Payload).

The virtual extensible local area network identifier in this embodiment represents an ID (Identity Document) that can be used for achieving tenant isolation, different virtual extensible local area network identifiers may correspond to different tenants, and the virtual extensible local area network identifier is specifically a VNI (VXLAN Network ID).

The resolver (Resolver) in this embodiment parses and strips the VXLAN header and the Inner header to obtain the VNI in the message, and then inserts the VNI into the EDNS field of the DNS message (the virtual extensible local area network message in this embodiment). Option Code reserved in the EDNS protocol may be used for specific arrangement. As shown in FIG. 7 which is a schematic structural diagram of a message constructed based on the extended domain name resolution protocol, the structure of the message includes a transaction ID (Transaction ID), a flag (Flags), the number of questions (Questions), the number of answer resource records (Answer RRs), the number of authority resource records (Authority RRs), the number of additional resource records (Additional RRs), a query (Queries), the number of answers (Answers), an authoritative name server (Authoritative nameservers), an extended return code (EXTENDED-RCODE), a version (VERSION), an option code (OPTION-CODE), an option length (OPTION-LENGTH), and option data (OPTION-DATA). The option data in this embodiment is specifically VNI&IDC (a virtual extensible local area network identifier and computer room encoding information). Additional information (Additional records) includes an option code (OPTION-CODE), an option length (OPTION-LENGTH), and option data (OPTION-DATA).

Step S2022, generating the second domain name resolution request based on the outer network information, the virtual extensible local area network identifier, and the message payload information.

Specifically, in this embodiment, the related information such as the outer network information, the virtual extensible local area network identifier, and the message payload information may be encapsulated into a message representing the second domain name resolution request.

Step S203, receiving a resolution result of the second domain name resolution request by the authoritative domain name system, and forwarding the resolution result to the virtual device through the network module. For details, please refer to step S103 of the embodiment shown in FIG. 1, which will not be repeated here.

In the domain name resolution method provided in this embodiment, the VNI can be parsed from the virtual extensible local area network message, so that a set of tenant-isolated domain name resolution process is implemented. By specifying the VNI in each domain name resolution rule, the domain configurations of different VNIs can be independent and non-conflicting, thereby achieving the purpose of private network domain name resolution.

In this embodiment, a domain name resolution method for edge computing is provided, which can be applied to a resolver. FIG. 3 is a flowchart of a domain name resolution method for edge computing according to an embodiment of the present disclosure. As shown in FIG. 3, the process includes the following steps.

Step S301, acquiring a first domain name resolution request forwarded by a virtual device through a network module, wherein the virtual device, the network module, and the resolver are deployed on a first physical machine, and the first physical machine is disposed in a first edge computer room. For details, please refer to step S201 of the embodiment shown in FIG. 2, which will not be repeated here.

Step S302, converting the first domain name resolution request into a second domain name resolution request, and sending the second domain name resolution request to an authoritative domain name system, wherein the authoritative domain name system is deployed on a second physical machine, and the second physical machine is disposed in a second edge computer room.

Specifically, the above step S302 includes the following steps.

Step S3021, parsing outer network information, a virtual extensible local area network identifier, and message payload information from the virtual extensible local area network message. For details, please refer to step S2021 of the embodiment shown in FIG. 2, which will not be repeated here.

Step S3022, generating the second domain name resolution request based on the outer network information, the virtual extensible local area network identifier, and the message payload information.

Specifically, the above step S3022 includes the following steps.

Step S30221, acquiring computer room encoding information corresponding to the first domain name resolution request.

The computer room encoding information is, for example, a computer room ID, and specifically a first edge computer room ID. In this embodiment, the computer room encoding information may be configured on the resolver (Resolver), that is, the computer room ID information is configured on the resolver, and the computer room ID is used for distinguishing between different first edge computer rooms.

Step S30222, generating the second domain name resolution request using the outer network information, the virtual extensible local area network identifier, the message payload information, and the computer room encoding information.

As shown in FIG. 8, in this embodiment, the outer network information, the virtual extensible local area network identifier, the message payload information, and the computer room encoding information may be encapsulated into a message representing the second domain name resolution request. The outer network information may include an outer Ethernet header (Outer Ethernet header) and an outer IP header (Outer IP header), and the virtual extensible local area network identifier and the message payload information are encapsulated in a DNS payload with EDNS (DNS Payload with EDNS).

In the domain name resolution method for edge computing provided in this embodiment, the different second domain name resolution requests are further distinguished through the computer room encoding information, so that the different second domain name resolution requests can still be distinguished in the case that the virtual extensible local area network identifiers are the same, thereby achieving a better tenant isolation effect in the domain name resolution process.

In some optional implementations, the above step S30222 includes: encapsulating the outer network information, the virtual extensible local area network identifier, the message payload information, and the computer room encoding information into an extended domain name resolution message based on an extended domain name resolution protocol, wherein the second domain name resolution request is the extended domain name resolution message.

In this embodiment, the extended domain name resolution protocol is an EDNS (Extension Mechanisms for DNS) protocol. The outer network information, the virtual extensible local area network identifier, the message payload information, and the computer room encoding information are encapsulated through the EDNS protocol, which can provide a larger DNS message size and support the expansion of functions and options. Moreover, the message encapsulated based on the EDNS protocol can improve the communication efficiency between the Resolver and the authoritative DNS, and reduce the delay of the DNS query.

Step S303, receiving a resolution result of the second domain name resolution request by the authoritative domain name system, and forwarding the resolution result to the virtual device through the network module.

Specifically, after receiving the extended domain name resolution message, the authoritative domain name system performs the tenant-isolated domain name resolution through the VNI&IDC. The resolution result is responded to the resolver of the corresponding first physical machine as a DNS data packet. The resolver may find the original session connection by receiving the quintuple data of the message, and then obtain the address of the Inner part to be encapsulated, and then encapsulate the VXLAN header for the DNS data packet to form a new VXLAN (virtual extensible local area network) data packet. The original address and the target address in the header of the response message as the resolution result need to be exchanged, and the final message is sent to the virtual machine that sends the domain name resolution request through the virtual switch (vSwitch).

It should be understood that in the edge computing scenario, the physical machines disposed in the edge computer rooms specifically involved in the present disclosure, for example, may include but are not limited to the aforementioned first physical machine and second physical machine, may be understood as a kind of edge computing nodes.

As shown in FIG. 5, in this embodiment, a domain name resolution system for edge computing is provided, and the domain name resolution system for edge computing includes but is not limited to a virtual device, a network module, a resolver, and an authoritative domain name system.

The virtual device is configured to send a private network domain name resolution request to the network module.

The network module is configured to convert the private network domain name resolution request into the first domain name resolution request, and send the first domain name resolution request to the resolver.

The resolver is configured to convert the first domain name resolution request into a second domain name resolution request, and send the second domain name resolution request to the authoritative domain name system. The virtual device, the network module, and the resolver are deployed on the first physical machine, and the first physical machine is disposed in the first edge computer room.

The authoritative domain name system is configured to resolve the second domain name resolution request to obtain the resolution result. The authoritative domain name system is further configured to send the resolution result to the resolver. The authoritative domain name system is deployed on the second physical machine, The second physical machine is disposed in the second edge computer room.

The resolver is further configured to forward the resolution result to the network module.

The network module is further configured to forward the resolution result to the virtual device.

The present embodiment provides a distributed private network DNS system suitable for an edge computing scenario, which can be deployed in discrete edge computer rooms in a distributed manner, so that the problem of complex DNS deployment in the edge computing scenario is solved. In addition, the architecture of the domain name resolution system provided in the present embodiment does not require a set of DNS system to be deployed in each edge computer room independently. Thus, the authoritative domain name system and the virtual device resource are deployed separately on the basis of implementing the function of domain name resolution, so that the case where a set of domain name system is deployed for each edge computer room is avoided, and the problems in the related art that the scale of the domain name system in the edge cloud computing scenario is large, the maintenance is difficult, and the deployment cost is high are overcome. The domain name resolution architecture for edge computing provided in the embodiments of the present disclosure is applied to the private network DNS in the edge computing scenario, and provides a complete set of DNS solutions, and can also solve the problem of tenant isolation for the DNS resolution in the edge computing scenario. The domain name resolution system for edge computing provided in the present embodiment has a wide range of applications, and can greatly reduce the DNS resource consumption in the edge computing environment.

In some optional implementations, the first domain name resolution request is a virtual extensible local area network message.

Specifically, the resolver is configured to parse outer network information, a virtual extensible local area network identifier, and message payload information from the virtual extensible local area network message, and generate the second domain name resolution request based on the outer network information, the virtual extensible local area network identifier, and the message payload information.

In some optional implementations, the resolver is specifically configured to acquire computer room encoding information corresponding to the first domain name resolution request; and the resolver is specifically configured to generate the second domain name resolution request using the outer network information, the virtual extensible local area network identifier, the message payload information, and the computer room encoding information.

In some optional implementations, the resolver is specifically configured to encapsulate the outer network information, the virtual extensible local area network identifier, the message payload information, and the computer room encoding information into an extended domain name resolution message based on an extended domain name resolution protocol, wherein the second domain name resolution request is the extended domain name resolution message.

In some optional implementations, the network module is a virtual switch, and the virtual switch is configured to encapsulate a domain name resolution message sent by the virtual device into a virtual extensible local area network message.

In some optional implementations, the resolver is specifically configured to maintain a session connection between the resolver and the network module, and forward the resolution result to the virtual device through the network module based on the session connection between the resolver and the network module.

In some optional implementations, the resolver is further configured to acquire configuration information delivered by an edge private network domain name system console, wherein the configuration information is used for characterizing a resolution rule for a target domain name resolution request, and the target domain name resolution request includes the first domain name resolution request.

In some optional implementations, the domain name resolution system for edge computing further includes a load balance; and the resolver is specifically configured to send the second domain name resolution request to a load balance device, wherein the load balance device is configured to allocate the second domain name resolution request to the authoritative domain name system.

In some optional implementations, there are at least two second edge computer rooms.

For the detailed implementations of the components included in the domain name resolution system, such as the virtual device, the network module, the resolver, and the authoritative domain name system, they have been described in detail in the aforementioned embodiments, and will not be repeated here.

In this embodiment, a domain name resolution apparatus for edge computing is further provided, and the apparatus is configured to implement the above embodiments and preferred implementations, which will not be repeated. As used below, the term “module” may be a combination of software and/or hardware that implements a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceived.

In this embodiment, a domain name resolution apparatus for edge computing is provided. As shown in FIG. 10, the apparatus includes:

- an acquiring unit 1001, configured to acquire a first domain name resolution request forwarded by a virtual device through a network module, wherein the virtual device, the network module, and a resolver are deployed on a first physical machine, and the first physical machine is disposed in a first edge computer room;