Domain name resolution method and device of DPU DNS, equipment and medium

By checking and completing the domain name in the container and calling the core DNS server and DPU DNS server plug-in, the problem of traditional DNS proxy being unable to resolve the high-speed network in the DPU cloud native service grid scenario is solved, and the DPU cluster and headless service is realized Domain name resolution service meets the DNS requirements of high-speed networks and supports load balancing.

CN119094495APending Publication Date: 2024-12-06YUSUR TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411113205.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-14
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

Traditional DNS proxy cannot meet the requirements of high-speed network DNS domain name resolution in DPU cloud native service mesh scenarios, especially for the domain name resolution of headless services, which cannot be effectively supported.

Method used

Provides a DPU DNS domain name resolution method. By checking and completing the domain name in the container, calling the core DNS server and DPU DNS server plug-in, parsing DNS messages and returning the network interface IP of the DPU cluster or headless service based on the results, supporting UDP DNS Deserialization and load balancing of messages.

Benefits of technology

It realizes domain name resolution services for DPU clusters and headless services in high-speed network scenarios, meets the DNS requirements of multiple k8s networks, supports the use habits of native k8s DNS agents, and optimizes performance through load balancing.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119094495A_ABST
    Figure CN119094495A_ABST
Patent Text Reader

Abstract

The invention provides a DPU DNS domain name resolution method, device and equipment and a medium, and the method comprises the steps: initiating a DNS domain name resolution request, and complementing a domain name according to the search function and symbol number of a file to obtain a domain name used for requesting a core DNS; the core DNS server calls server plug-ins before the DPU DNS in sequence, and when the DPU DNS result is not searched, the core DNS server inquires the DPU DNS server plug-ins and receives the DPU DNS server plug-ins to a DNS domain name resolution request; receiving a DNS message, and analyzing the DNS message to obtain the type of the DNS; searching the indexes of the service notifier and the endpoint notifier according to the name of the DNS message attribute, and if the indexes are matched, returning the IP of the DPU cluster or the DPU network interface IP of the container of the headless service; starting a DPU DNS server, monitoring a UDP DNS message, performing deserialization processing on the message, and querying a service notifier and an endpoint notifier according to a processing result to obtain a service and a type; a DNS response is transmitted based on the service and type. Therefore, the DNS domain name resolution service in a special scene can be satisfied.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present application relate to the field of network communication technology, and in particular to a DPU DNS domain name resolution method, device, equipment and medium. Background Art

[0002] In a multi-network scenario, the k8s container network may be connected to the management network and the high-speed DPU network at the same time. The existing k8s DNS proxy supports resolving the service's DNS domain name into the actual cluster IP address. The headless service domain name will be resolved into the actual IP address of the first network interface.

[0003] However, in the DPU cloud-native service mesh scenario, the high-speed network port is usually the second interface, so the traditional DNS proxy cannot meet the DNS domain name resolution requirements of the high-speed network scenario. Summary of the invention

[0004] The embodiment of the present application provides a DPU DNS domain name resolution method to meet the DNS domain name resolution service of high-speed network scenarios.

[0005] In a first aspect, an embodiment of the present application provides a DPU DNS domain name resolution method, including:

[0006] The first container initiates a DNS domain name resolution request, the resolution request includes a first domain name, and checks a first file corresponding to the resolution request in the first container;

[0007] According to the search function and the number of symbols of the first file, the first domain name is completed to obtain a second domain name, where the second domain name is used to request a core DNS server;

[0008] The core DNS server calls the server plug-in before the DPU DNS in order. When the DPU DNS server plug-in does not search for the DPU DNS result, the core DNS server queries the DPU DNS server plug-in and connects the DPU DNS server interface to the DNS domain name resolution request.

[0009] Receiving a DNS message, parsing the DNS message, and determining the type of the DNS according to the parsing result;

[0010] Search the index of the service notifier and the index of the endpoint notifier according to the name of the DNS message attribute, and return the IP of the corresponding DPU cluster or the IP of the DPU network interface of the container of the headless service if they match;

[0011] Start the DPU DNS server and monitor the UDP DNS message, deserialize the UDP DNS message, and query the service notifier and endpoint notifier according to the deserialized message to obtain the service and type;

[0012] Based on the service and the type, a DNS response is sent.

[0013] In a possible implementation, the DNS response includes a service IP, and the service IP includes: an IP of a DPU cluster or an IP of a DPU network interface.

[0014] In a possible implementation, the client sends a DNS domain name resolution request to the server based on the service IP.

[0015] In a possible implementation, the DNS domain name resolution request is processed to obtain a resolution result;

[0016] When the resolution result is the IP of the DPU cluster, load balancing is performed when passing through the DPU proxy to obtain the IP of the DPU virtual interface; or

[0017] In the case of the IP of the virtual interface of the DPU in the analysis result, no load balancing is performed.

[0018] In a second aspect, an embodiment of the present application provides a domain name resolution device of a DPU DNS, including:

[0019] An initiating module, configured to initiate a DNS domain name resolution request in a first container, wherein the resolution request includes a first domain name, and check a first file corresponding to the resolution request in the first container;

[0020] A completion module, used to complete the first domain name according to the search function and the number of symbols of the first file to obtain a second domain name, where the second domain name is used to request a core DNS server;

[0021] The calling module is used for the core DNS server to call the server plug-in before the DPU DNS in order. When the DPU DNS result is not searched before the DPU DNS server plug-in, the core DNS server queries the DPU DNS server plug-in and connects the DPU DNS server interface to the DNS domain name resolution request;

[0022] A receiving module, used to receive a DNS message, parse the DNS message, and determine the type of DNS according to the parsing result;

[0023] A search module, used to search for the index of the service notifier and the index of the endpoint notifier according to the name of the DNS message attribute, and return the IP of the corresponding DPU cluster or the IP of the DPU network interface of the container of the headless service if they match;

[0024] A startup module is used to start the DPU DNS server, monitor the UDP DNS message, deserialize the UDP DNS message, and query the service notifier and endpoint notifier according to the deserialized message to obtain the service and type;

[0025] A sending module is used to send a DNS response based on the service and the type.

[0026] In a possible implementation, the DNS response includes a service IP, and the service IP includes: an IP of a DPU cluster or an IP of a DPU network interface.

[0027] In a possible implementation, the sending module is further used for: the client sends a DNS domain name resolution request to the server based on the service IP.

[0028] In a possible implementation, the device further includes a resolution module, which is used to: resolve the DNS domain name request to obtain a resolution result;

[0029] When the resolution result is the IP of the DPU cluster, load balancing is performed when passing through the DPU proxy to obtain the IP of the DPU virtual interface; or, when the resolution result is the IP of the DPU virtual interface, load balancing is not performed.

[0030] In a third aspect, an embodiment of the present application further provides an electronic device, the electronic device comprising:

[0031] at least one processor;

[0032] and a memory communicatively coupled to the at least one processor;

[0033] Among them, the memory stores instructions that can be executed by at least one processor, and the instructions are executed by at least one processor to enable the electronic device to execute a method corresponding to any embodiment in the first aspect of the embodiments of the present application.

[0034] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, in which computer-readable storage medium is stored computer execution instructions, which, when executed by a processor, are used to implement any method of the first aspect of the embodiment of the present application.

[0035] In a fifth aspect, the present disclosure further provides a computer program product, which includes computer execution instructions, and the computer execution instructions are used to implement the method when executed by a processor.

[0036] In summary, the method shown in the embodiment of the present application solves the limitations of routing in traditional scenarios, so that different networks can be selected according to domain names within the same network namespace, and the domain name resolution method for headless services matches the native k8s, so that users can use multiple k8s networks including DPU high-speed networks according to their previous usage habits, and can meet the DNS domain name resolution service of high-speed network scenarios. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0038] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0039] Figure 1 A flowchart of a domain name resolution method of a DPU DNS provided in an embodiment of the present application;

[0040] Figure 2 A schematic diagram of a device for a domain name resolution method of a DPU DNS provided in an embodiment of the present application;

[0041] Figure 3 A schematic diagram of an electronic device for the domain name resolution method of the DPU DNS provided in an embodiment of the present application. DETAILED DESCRIPTION

[0042] When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments are only examples of devices and methods consistent with some aspects of the embodiments of the present application as detailed in the appended claims.

[0043] The following specific embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. The following will describe the embodiments of the present application in conjunction with the accompanying drawings.

[0044] It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0045] DPU: Data Processing Unit, as a dedicated hardware accelerator, is a new generation of data-centric computing processors that integrates complete data center functions into a single chip. Together with CPU and GPU, it constitutes the three pillars of new computing. By using specially designed hardware accelerators to quickly process data packets entering the DPU, processing delays can be reduced and processing throughput can be improved.

[0046] K8S: Its full name is kubernetes, and K8S is its abbreviation, with the word "8" replacing the eight characters of "ubernete". It is a container-based cluster management platform, which can also be called an open source container orchestration platform, used to automate the deployment, expansion and management of containerized applications. It provides a flexible and scalable way to manage containerized applications, and provides a range of features to simplify application deployment, scheduling, self-healing and expansion.

[0047] Pod: An abbreviation for Point of Delivery, Kubernetes encapsulates one or more containers into a high-level structure called a pod. Any container in the same pod will share the same namespace and local network. Containers can easily communicate with other containers in the same container, just as if they were on the same machine while maintaining a certain degree of isolation.

[0048] dpu.cluster.local: The default internal Kubernetes cluster domain name.

[0049] in-addr.arpa and ip6.arpa: Domain names used for reverse DNS queries.

[0050] fallthrough: If no matching record is found in the dpu dns plugin, the query will "fall through" to the next plugin.

[0051] The following is a detailed description of the lightweight DPU protocol proxy configuration method involved in the present invention.

[0052] Figure 1 A domain name resolution method of a DPU DNS is provided in an embodiment of the present application. Figure 1 The method includes steps S101 to S107. Each step is described in detail as follows.

[0053] S101: A first container initiates a DNS domain name resolution request, where the resolution request includes a first domain name, and checks a first file corresponding to the resolution request in the first container.

[0054] For example, when service A accesses service B, if B.default.svc.cluster.local (domain name) is used for access, it will be resolved to the cluster IP of serviceB. If B.default.svc.dpu.cluster.local is used for access, it will be resolved to the cluster IP of servcieB's DPU, and DNS load balancing is enabled in the envoy of soc (the data plane network agent of the grid on the DPU), which can be resolved to the IP of the network interface (dpuvf) of pod B's DPU.

[0055] If Service B is a headless service, the dpu dns server will resolve it into the dpuvf address of Pod B, which is consistent with the native k8s headless resolution solution and supports the dpu network.

[0056] The dpu dns resolver can be integrated into k8s through the core DNS (coredns) plug-in. At the same time, the search function of dpu.svc.cluster.local (domain name) is set in the first file (resolve). The search function is very useful for local domain names, because when dealing with local domain names and fully qualified domain names (FQDN) in the cluster, especially local domain names, they do not contain top-level domain names (TLDs) and are not fully qualified.

[0057] S102: According to the search function and the number of symbols of the first file, the first domain name is completed to obtain a second domain name, where the second domain name is used to request a core DNS server.

[0058] In the embodiment of the present application, when performing DNS resolution on a local domain name, it is usually necessary to combine the DNS search domain (such as specified by the domain or search directive in / etc / resolv.conf) to form a complete domain name. Then, by setting the value of the number of dots (ndots) of the domain name, the behavior of the DNS query is optimized, especially in an environment with multiple search domains configured.

[0059] Add the number of "ndots" (dots) in the domain name. For example, add 6 to indicate the number of dots in the domain name. If a domain name has fewer dots than the set value of 6, the DNS will first try to treat the domain name as a local domain name when performing DNS resolution.

[0060] That is, the container will add the locally defined search domain after the domain name (specified by the search or domain directive in the resolv.conf file, such as svc.dpu.cluster.local) to make a resolution attempt. Only when the number of dots in the domain name reaches or exceeds the value of 6 set by ndots, the DNS resolver will treat it as a fully qualified domain name and resolve it directly without adding any local search domains.

[0061] S103, the core DNS server calls the server plug-in before the DPU DNS in order. When the DPU DNS result is not found before the DPU DNS server plug-in, the core DNS server queries the DPU DNS server plug-in and connects the DPU DNS server interface to the DNS domain name resolution request.

[0062] In an embodiment of the present application, the specific way in which the plug-in accesses the dpu dns resolver can be achieved by setting a core file configuration mapping resource (Corefile configmap). This configuration file is the configuration file of CoreDNS, which defines how the CoreDNS server responds to DNS requests.

[0063] S104: Receive a DNS message, parse the DNS message, and determine the type of DNS according to the parsing result.

[0064] S105. Search for the index of the service notifier and the index of the endpoint notifier according to the name of the DNS message attribute, and return the IP of the corresponding DPU cluster or the IP of the DPU network interface of the container of the headless service if they match.

[0065] In an embodiment of the present application, the DPU DNS service implements a service DNS (ServiceDNS) plug-in interface, which receives information of a DNS message (r dns.msg dns) request, parses the request message, completes the DNS type judgment, and searches the index (indexer) of the service notifier (serviceinformer) and the index (indexer) of the endpoint notifier (endpointsinformer) by the name of the attribute of the root DNS message. If a match is found, the IP address of the corresponding DPU cluster or the IP address of the DPU network interface of the container of the headless service is returned. If there is no match, a name error (RcodeNameError) is returned.

[0066] S106: Start the DPU DNS server and monitor the UDP DNS message, deserialize the UDP DNS message, and query the service notifier and endpoint notifier according to the deserialized message to obtain the service and type.

[0067] In the embodiment of the present application, when the DPU DNS server starts the service, it listens to UDP data packets. It receives data loops to continuously listen to and process incoming DNS queries. It receives DNS queries and deserializes them. Based on the parsed information, it queries the indexer cache of the informer to obtain service and type information, and gives a DNS response, including:

[0068] a) Create DNS response: Create a new DNS Message object as a response, including the query ID and query record.

[0069] b) Query the service IP through the service notifier: Call the service notifier to get the object (ServiceInformer.GetObj) to find the k8s service object that matches the DNS query. Assume that this method queries the k8s service by service name and returns the V1Service service object.

[0070] c) Handling unfound services: If ServiceInformer.GetObj returns null, it means that the corresponding service is not found.

[0071] d) Process the found services:

[0072] (1) If the service is found and the service type is not headless, the cluster IP address is obtained from the service Spec (specific information) and a DNS response record (ARecord) is created. The response record contains the IP address of the service.

[0073] (2) If the queried service is of headless type, it is also necessary to query the endpoints object corresponding to the dpu dns domain name through EndpointsInformer (endpoint notifier). Assume that this method queries the Kubernetes service by service name and returns the V1Endpints object. Processing unfound services: If ServiceInformer.GetObj returns null, it means that the corresponding service is not found. Processing found services: If the service is found, get the address from the Subsets of Endpoints and create a DNS answer record (ARecord) containing this IP address.

[0074] e) Prepare response data: Convert the response message into byte format for sending over the network.

[0075] f) Send Response: Create a new DatagramPacket to send the response and use the serverSocket.send method to send it back to the source address and port of the query.

[0076] S107: Send a DNS response based on the service and the type.

[0077] In a possible implementation, the DNS response includes a service IP, and the service IP includes: an IP of a DPU cluster or an IP of a DPU network interface.

[0078] In a possible implementation, the client sends a DNS domain name resolution request to the server based on the service IP.

[0079] In a possible implementation, the DNS domain name resolution request is processed to obtain a resolution result;

[0080] When the resolution result is the IP of the DPU cluster, load balancing is performed when passing through the DPU proxy to obtain the IP of the DPU virtual interface; or

[0081] In the case of the IP of the virtual interface of the DPU in the analysis result, no load balancing is performed.

[0082] It can be seen that through this method, when supporting the DPU DNS domain name of the IP type service of the DPU cluster, it can be resolved to the IP of the DPU cluster of the service of the DPU network. When supporting the DPUDNS domain name of the headless type service, the high-speed network interface IP of the DPU container can be resolved. And it is seamlessly connected to the k8s cluster and integrated into the DNS service of k8s in the form of a plug-in. Users can configure this DPU DNS plug-in to the appropriate order through the core file (corefile) to identify the DPU DNS domain name in the k8s cluster.

[0083] In summary, the method shown in the embodiment of the present application solves the limitations of routing in traditional scenarios, so that different networks can be selected according to domain names within the same network namespace, and the domain name resolution method for headless services matches the native k8s, so that users can use multiple k8s networks including DPU high-speed networks according to their previous usage habits, and can meet the DNS domain name resolution service of high-speed network scenarios.

[0084] Figure 2 A DPU DNS domain name resolution device is provided for an embodiment of the present application, including:

[0085] An initiating module 201 is used for initiating a DNS domain name resolution request in a first container, where the resolution request includes a first domain name, and checking a first file corresponding to the resolution request in the first container;

[0086] A completion module 202, configured to complete the first domain name according to the search function and the number of symbols of the first file to obtain a second domain name, wherein the second domain name is used to request a core DNS server;

[0087] The calling module 203 is used for the core DNS server to call the server plug-in before the DPU DNS in order. When the DPU DNS server plug-in does not search for the DPU DNS result, the core DNS server queries the DPU DNS server plug-in and connects the DPU DNS server interface to the DNS domain name resolution request;

[0088] The receiving module 204 is used to receive a DNS message, parse the DNS message, and determine the type of the DNS according to the parsing result;

[0089] A search module 205 is used to search for an index of a service notifier and an index of an endpoint notifier according to the name of the DNS message attribute, and if they match, return the IP of the corresponding DPU cluster or the IP of the DPU network interface of the container of the headless service;

[0090] The start module 206 is used to start the DPU DNS server, monitor the UDP DNS message, deserialize the UDP DNS message, and query the service notifier and the endpoint notifier according to the deserialized message to obtain the service and type;

[0091] The sending module 207 is used to send a DNS response based on the service and the type.

[0092] In a possible implementation, the DNS response includes a service IP, and the service IP includes: an IP of a DPU cluster or an IP of a DPU network interface.

[0093] In a possible implementation, the sending module is further used for: the client sends a DNS domain name resolution request to the server based on the service IP.

[0094] In a possible implementation, the device further includes a resolution module, which is used to: resolve the DNS domain name request to obtain a resolution result;

[0095] When the resolution result is the IP of the DPU cluster, load balancing is performed when passing through the DPU proxy to obtain the IP of the DPU virtual interface; or, when the resolution result is the IP of the DPU virtual interface, load balancing is not performed.

[0096] The above device is used to achieve Figure 1 The method of any corresponding embodiment.

[0097] Figure 3 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application is shown in FIG. Figure 3 As shown, the electronic device 300 includes: a memory 310 and a processor 320 .

[0098] The memory 310 stores a computer program that can be executed by at least one processor 320. The computer program is executed by at least one processor 320 to enable the electronic device to implement the method provided in any of the above embodiments.

[0099] The memory 310 and the processor 320 may be connected via a bus 330 .

[0100] The relevant instructions can be understood by referring to the relevant descriptions and effects corresponding to the method embodiments, which will not be repeated here.

[0101] An embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, and the computer program is executed by a processor to implement the following Figure 1 The method of any corresponding embodiment.

[0102] Among them, the computer-readable storage medium may be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

[0103] An embodiment of the present application provides a computer program product, which includes computer-executable instructions, which are used to implement the following when the computer-executable instructions are executed by a processor: Figure 1 The method of any corresponding embodiment.

[0104] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of modules is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.

[0105] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the disclosure disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope of the present application is indicated by the claims.

[0106] It should be understood that the present application is not limited to the exact construction that has been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof.

Claims

1. A domain name resolution method for DPU DNS, characterized in that: include: The first container initiates a DNS domain name resolution request, the resolution request includes a first domain name, and checks a first file corresponding to the resolution request in the first container; According to the search function and the number of symbols of the first file, the first domain name is completed to obtain a second domain name, where the second domain name is used to request a core DNS server; The core DNS server calls the server plug-in before the DPU DNS in order. When the DPU DNS server plug-in does not search for the DPU DNS result, the core DNS server queries the DPU DNS server plug-in and connects the DPUDNS server interface to the DNS domain name resolution request. Receiving a DNS message, parsing the DNS message, and determining the type of the DNS according to the parsing result; Search the index of the service notifier and the index of the endpoint notifier according to the name of the DNS message attribute, and return the IP of the corresponding DPU cluster or the IP of the DPU network interface of the container of the headless service if they match; Start the DPU DNS server and monitor the UDP DNS message, deserialize the UDP DNS message, and query the service notifier and endpoint notifier according to the deserialized message to obtain the service and type; Based on the service and the type, a DNS response is sent.

2. The method according to claim 1, characterized in that: include: The DNS response includes a service IP, and the service IP includes: an IP of a DPU cluster or an IP of a DPU network interface.

3. The method according to claim 2, characterized in that The method further comprises: The client sends a DNS domain name resolution request to the server based on the service IP.

4. The method according to claim 3, characterized in that The method further comprises: obtaining a resolution result for the DNS domain name resolution request; When the resolution result is the IP of the DPU cluster, load balancing is performed when passing through the DPU proxy to obtain the IP of the DPU virtual interface; or In the case of the IP of the virtual interface of the DPU in the analysis result, no load balancing is performed.

5. A domain name resolution device for DPU DNS, characterized in that: include: An initiating module, configured to initiate a DNS domain name resolution request in a first container, wherein the resolution request includes a first domain name, and check a first file corresponding to the resolution request in the first container; a completion module, configured to complete the first domain name according to the search function and the number of symbols of the first file to obtain a second domain name, wherein the second domain name is used to request a core DNS server; The calling module is used for the core DNS server to call the server plug-in before the DPU DNS in order. When the DPU DNS result is not searched before the DPU DNS server plug-in, the core DNS server queries the DPU DNS server plug-in and connects the DPU DNS server interface to the DNS domain name resolution request; A receiving module, used to receive a DNS message, parse the DNS message, and determine the type of DNS according to the parsing result; A search module, used to search for the index of the service notifier and the index of the endpoint notifier according to the name of the DNS message attribute, and return the IP of the corresponding DPU cluster or the IP of the DPU network interface of the container of the headless service if they match; A startup module is used to start the DPU DNS server, monitor the UDP DNS message, deserialize the UDP DNS message, and query the service notifier and endpoint notifier according to the deserialized message to obtain the service and type; A sending module is used to send a DNS response based on the service and the type.

6. The device according to claim 5, characterized in that include: The DNS response includes a service IP, and the service IP includes: an IP of a DPU cluster or an IP of a DPU network interface.

7. The device according to claim 6, characterized in that The sending module is further used for: The client sends a DNS domain name resolution request to the server based on the service IP.

8. The device according to claim 7, characterized in that The device also includes a parsing module, which is used to: obtain a parsing result for the DNS domain name parsing request; When the resolution result is the IP of the DPU cluster, load balancing is performed when passing through the DPU proxy to obtain the IP of the DPU virtual interface; or In the case of the IP of the virtual interface of the DPU in the analysis result, no load balancing is performed.

9. An electronic device, characterized in that: include: at least one processor; and a memory communicatively coupled to the at least one processor; The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the electronic device to perform the method as claimed in any one of claims 1 to 4.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 4 when executed by a processor.

11. A computer program product comprising computer executable instructions, characterized in that: The computer-executable instructions are used to implement the method according to any one of claims 1 to 4 when executed by a processor.