Method for improving intranet domain name resolution performance and related equipment

Abstract

The invention discloses a method for improving intranet domain name resolution performance and related equipment. The method comprises the following steps: acquiring message data of a domain name server; based on time point arrangement corresponding to the message data, a first response duration of a first request response stage and a second response duration of a second request response stage are obtained; and when the first response duration is greater than a preset multiple of the second response duration, issuing a network configuration parameter of the local server to the client, so that the client establishes a domain name service resolution link with the local server. According to the method, the processing delay and cache query overhead of a low-performance router can be effectively avoided, the domain name resolution efficiency and speed are remarkably improved, the network access experience of a user is finally improved, and the method can be widely applied to the technical field of data processing.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a method and related equipment for improving the performance of intranet domain name resolution. Background Technology

[0002] In current routers (including mobile hotspots) operating under DHCP (Dynamic Host Configuration Protocol) scenarios, DNS (Domain Name Server) configuration is often lacking or rarely configured by users. Terminals often directly use the router's IP address (i.e., gateway address) as their DNS server. Resolution can still be achieved in this situation because routers typically provide simple DNS forwarding functionality. That is, when a DNS request comes from a proxy terminal, the router's DNS cache is first checked for a corresponding record. If a record is found, it is retrieved directly from the cache; otherwise, it is forwarded to the DNS server configured on the router (usually the ISP's LDNS). The resolution performance here depends on the router's performance and the size of its cache. In scenarios where a standard or low-end router acts as the internal network exit point, performing simple NAT, slow internet access can occur due to DNS issues. Summary of the Invention

[0003] The main objective of this invention is to provide a method, apparatus, electronic device, storage medium, and program product for improving intranet domain name resolution performance, aiming to solve at least one problem in the prior art.

[0004] To achieve the above objectives, one aspect of this invention proposes a method for improving intranet domain name resolution performance, the method comprising: Obtain message data from the domain name server; The domain name server includes a proxy server and a local server, and the message data includes the first message of the first request-response phase between the client and the proxy server and the second message of the second request-response phase between the proxy server and the local server. Based on the time points corresponding to the message data, the first response duration of the first request-response phase and the second response duration of the second request-response phase are obtained; When the duration of the first response exceeds a preset multiple of the duration of the second response, the network configuration parameters of the local server are sent to the client so that the client can establish a domain name service resolution link with the local server.

[0005] In some embodiments, obtaining message data from a domain name server includes the following steps: When the proxy server does not support deep packet inspection, it identifies packet data based on access control lists. When the proxy server supports deep packet inspection, it identifies packet data based on deep packet inspection or access control lists.

[0006] In some embodiments, the first message includes a first request message sent by the client to the proxy server and a first response message sent by the proxy server. The first response duration of the first request-response phase is obtained by organizing the message data based on the corresponding time points, including the following steps: The first time point is defined as the time when the proxy server receives the first request message from the client. The time when the proxy server sends the first response message to the client is taken as the fourth time point; The first response message is triggered based on the second response message received by the proxy server from the local server; The first response duration is obtained based on the difference between the fourth time point and the first time point.

[0007] In some embodiments, the second message includes a second request message sent by the proxy server to the local server and a second response message sent by the local server. The second response duration of the second request-response phase is obtained by organizing the message data based on the corresponding time points, including the following steps: The time when the proxy server sends the second request message is taken as the second time point; The time when the proxy server receives the second response message from the local server is taken as the third time point; The second response duration is obtained based on the difference between the third time point and the second time point.

[0008] In some embodiments, when the client deploys an agent, the network configuration parameters of the local server are sent to the client, including the following steps: The client re-initiates the interaction process of the Dynamic Host Configuration Protocol using the intelligent agent, and generates a discovery message based on the first phase of the interaction process. In response to the discovery message, the second phase of the interaction process is triggered by the service module of the proxy server, which uses the provision message to send the network configuration parameters of the local server to the client.

[0009] In some embodiments, when the client has not deployed an agent, the network configuration parameters of the local server are sent to the client, including the following steps: Obtain the lease information for the client's Dynamic Host Configuration Protocol (DIP). When the lease information expires, the client re-initiates the dynamic host configuration protocol interaction process and generates a discovery message based on the first phase of the interaction process. In response to the discovery message, the second phase of the interaction process is triggered by the service module of the proxy server, which uses the provision message to send the network configuration parameters of the local server to the client.

[0010] In some embodiments, the method further includes the following steps: When a client triggers a DNS request, the DNS request is sent to the local server based on the domain name service resolution link, so that the local server responds to the DNS request and performs DNS resolution.

[0011] To achieve the above objectives, another aspect of the present invention provides an apparatus for improving intranet domain name resolution performance, the apparatus comprising: The data acquisition module is used to acquire message data from the domain name server; The domain name server includes a proxy server and a local server, and the message data includes the first message of the first request-response phase between the client and the proxy server and the second message of the second request-response phase between the proxy server and the local server. The duration processing module is used to process the message data based on the corresponding time points to obtain the first response duration of the first request response stage and the second response duration of the second request response stage. The link establishment module is used to send the network configuration parameters of the local server to the client when the duration of the first response is greater than a preset multiple of the duration of the second response, so that the client can establish a domain name service resolution link with the local server.

[0012] In some embodiments, the apparatus further includes a request parsing module for performing the following operations: When a client triggers a DNS request, the DNS request is sent to the local server based on the domain name service resolution link, so that the local server responds to the DNS request and performs DNS resolution.

[0013] To achieve the above objectives, another aspect of the present invention provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the aforementioned method.

[0014] To achieve the above objectives, another aspect of the present invention provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the aforementioned method.

[0015] To achieve the above objectives, another aspect of the present invention provides a computer program product, including a computer program that, when executed by a processor, implements the aforementioned method.

[0016] The embodiments of this invention include at least the following beneficial effects: This invention provides a method, apparatus, electronic device, storage medium, and program product for improving intranet domain name resolution performance. This solution obtains message data from a domain name server; wherein the domain name server includes a proxy server and a local server, and the message data includes a first message in the first request-response phase between the client and the proxy server and a second message in the second request-response phase between the proxy server and the local server; based on the time points corresponding to the message data, the first response duration of the first request-response phase and the second response duration of the second request-response phase are obtained; when the first response duration is greater than a preset multiple of the second response duration, the network configuration parameters of the local server are sent to the client, enabling the client to establish a domain name service resolution link with the local server. The embodiments of this invention provide a proactive and intelligent optimization mechanism. By comparing the response durations of the client-proxy server (router) and proxy server-local server (LDNS) phases, it is possible to accurately determine whether the performance bottleneck lies in the router itself. Once confirmed (the first response takes much longer than the second response), the upstream LDNS address is automatically sent directly to the client, enabling the client to establish a direct resolution link to the LDNS. This effectively avoids the processing delays and cache query overhead of low-performance routers, significantly improving the efficiency and speed of domain name resolution, and ultimately improving the user's network access experience. Attached Figure Description

[0017] Figure 1 This is a schematic diagram of an implementation environment for a method to improve intranet domain name resolution performance provided in an embodiment of the present invention; Figure 2 This is a flowchart illustrating a method for improving intranet domain name resolution performance according to an embodiment of the present invention; Figure 3 This is a schematic diagram illustrating the unfolded process of step S100 provided in an embodiment of the present invention; Figure 4 This is a schematic diagram of an implementation process for sending network configuration parameters from a local server to a client, provided by an embodiment of the present invention. Figure 5 This is a schematic diagram illustrating another unfolding process for sending network configuration parameters from a local server to a client, as provided in an embodiment of the present invention. Figure 6 This is a schematic diagram illustrating the overall process of the method for improving intranet domain name resolution performance provided in this embodiment of the invention; Figure 7 This is a schematic diagram illustrating an example of DNS network configuration parameters provided in an embodiment of the present invention; Figure 8 This is a schematic diagram illustrating an example of a ULCL scenario for a 5G industry private network provided in an embodiment of the present invention; Figure 9 This is a schematic diagram of the device for improving intranet domain name resolution performance provided in an embodiment of the present invention; Figure 10 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0018] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. In the following description, when referring to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the embodiments of this invention; they are merely examples of apparatuses and methods consistent with some aspects of the embodiments of this invention as detailed in the appended claims.

[0019] It is understood that the terms “first,” “second,” etc., used in this invention may be used herein to describe various concepts, but unless specifically stated otherwise, these concepts are not limited by these terms. These terms are used only to distinguish one concept from another. For example, first information may also be referred to as second information without departing from the scope of embodiments of the invention, and similarly, second information may also be referred to as first information. Depending on the context, the words “if,” “when,” or “in response to determination” as used herein may be interpreted as “when…” or “when…” or “in response to determination.”

[0020] The terms “at least one,” “multiple,” “each,” “any,” etc., used in this invention, “at least one” includes one, two, or more than two; “multiple” includes two or more than two; “each” refers to each of the corresponding multiple; and “any” refers to any one of the multiple.

[0021] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. The terminology used herein is for the purpose of describing embodiments of the invention only and is not intended to limit the invention.

[0022] To facilitate understanding of the technical solution of this invention, the technical terms that may be involved in the technical solution of this invention will first be explained: DHCP: Dynamic Host Configuration Protocol, is a protocol used by routers to automatically assign IP addresses, and can also assign DNS addresses. DHCP is a communication protocol that enables network administrators to centrally manage and automatically assign IP network addresses. DNS: Domain Name Server; LDNS: Local DNS server, refers to the DNS server located in the operator's local area; DNS Forwarding: This refers to the DNS not responding directly to DNS resolution requests, but instead forwarding them to other DNS resolution providers. DNS Proxy: DNS proxy; DHCP Discovery: The DHCP Discovery message is the first stage of the DHCP four-step interaction process (discover, offer, request, confirm), and is used by a client to find a DHCP server when logging into the network for the first time.

[0023] DHCP Offer: This is a message type used in the Dynamic Host Configuration Protocol (DHCP) interaction process, belonging to the second stage (Offer) of the four-step DHCP interaction process (Discover, Offer, Request, Confirm). This message is sent by the DHCP server in response to a client's Discovery broadcast request and contains network configuration parameters such as the assigned IP address, default gateway, and DNS server address.

[0024] In related technologies, current routers (including mobile hotspots) in DHCP (Dynamic Host Configuration Protocol) scenarios often lack or have very few DNS (Domain Name Server) configurations. Terminals often directly use the router's IP address (i.e., gateway address) as their DNS server. Resolution can still be achieved in this situation because routers often provide simple DNSForwarding functionality. That is, when a DNS request comes from a proxy terminal, the router's DNS cache is first checked for a corresponding record. If a record is found, it is retrieved directly from the cache; otherwise, it is forwarded to the DNS server configured on the router (usually the ISP's LDNS). The resolution performance here depends on the router's performance and the size of its cache. In scenarios where a regular or low-end router acts as the internal network exit, performing simple NAT, slow internet access can occur due to DNS issues.

[0025] In view of this, this invention provides a method and related equipment for improving intranet domain name resolution performance. This solution obtains message data from a domain name server; wherein the domain name server includes a proxy server and a local server, and the message data includes a first message in the first request-response phase between the client and the proxy server and a second message in the second request-response phase between the proxy server and the local server; based on the time points corresponding to the message data, the first response duration of the first request-response phase and the second response duration of the second request-response phase are obtained; when the first response duration is greater than a preset multiple of the second response duration, the network configuration parameters of the local server are sent to the client, enabling the client to establish a domain name service resolution link with the local server. This invention provides a proactive and intelligent optimization mechanism. By comparing the response durations of the client-proxy server (router) and proxy server-local server (LDNS) phases, it is possible to accurately determine whether the performance bottleneck lies in the router itself. Once confirmed (the first response takes much longer than the second response), the upstream LDNS address is automatically sent directly to the client, enabling the client to establish a direct resolution link to the LDNS. This effectively avoids the processing delays and cache query overhead of low-performance routers, significantly improving the efficiency and speed of domain name resolution, and ultimately improving the user's network access experience.

[0026] It is understood that the method for improving intranet domain name resolution performance provided by this invention can be applied to any computer device with data processing and computing capabilities, and this computer device can be various terminals or servers. When the computer device in the embodiment is a server, the server is an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. Optionally, the terminal can be a smartphone, tablet, laptop, or desktop computer, but it is not limited to these.

[0027] like Figure 1 The diagram shown is a schematic representation of an implementation environment provided by an embodiment of the present invention. (Refer to...) Figure 1 The implementation environment includes at least one terminal 102 and a server 101. The terminal 102 and the server 101 can be connected via a network, either wirelessly or via a wired connection, to complete data transmission and exchange.

[0028] Server 101 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms.

[0029] Additionally, server 101 can also be a node server in a blockchain network. Blockchain is a novel application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and encryption algorithms.

[0030] Terminal 102 can be a smartphone, tablet, laptop, desktop computer, smart speaker, smartwatch, etc., but is not limited to these. Terminal 102 and server 101 can be directly or indirectly connected via wired or wireless communication, and this embodiment of the invention does not impose any limitations.

[0031] For example, based on Figure 1 The implementation environment shown in this embodiment of the invention provides a method for improving the performance of intranet domain name resolution. The following description uses the application of this method for improving the performance of intranet domain name resolution in server 101 as an example. It can be understood that this method for improving the performance of intranet domain name resolution can also be applied to terminal 102.

[0032] Reference Figure 2 , Figure 2 This is an optional flowchart of a method for improving intranet domain name resolution performance provided in an embodiment of the present invention. The execution subject of this method for improving intranet domain name resolution performance can be any of the aforementioned computer devices (including servers or terminals). Figure 2 The method may include, but is not limited to, steps S100 to S300.

[0033] Step S100: Obtain message data from the domain name server; The domain name server includes a proxy server and a local server, and the message data includes the first message of the first request-response phase between the client and the proxy server and the second message of the second request-response phase between the proxy server and the local server. It should be noted that in some embodiments, such as Figure 3 As shown, step S100 may include the following steps: S110, when the proxy server does not support deep packet inspection, packet data is identified based on access control lists; S120, when the proxy server supports deep packet inspection, packet data is identified based on deep packet inspection or access control lists.

[0034] For example, in some specific implementations, DNS packets can be identified based on Deep Packet Inspection (DPI) or Access Control Lists (ACLs). Specifically, this can be achieved by identifying the UDP port 53 of uplink packets, as well as four types of DNS packets: forwarded packets, response packets, and more (all of which can be identified by identifying IP addresses and port numbers using ACLs). If the router itself supports DPI, its capabilities can also be utilized.

[0035] In some specific application scenarios, when the routers in the network are low-end models with limited computing power and lack deep packet inspection (DPI) capabilities, an access control list (ACL)-based approach is used. Network devices (or service modules embedded in the router) are pre-configured with ACL rules designed to identify IP packet characteristics related to DNS services. Specifically, the rule can be configured to capture all packets with a source or destination port number of UDP 53 (the default port for DNS services). In this way, the system can accurately identify and collect all DNS request and response packets (i.e., the first and second packets) between the client and the router, and between the router and the upstream LDNS, without needing to parse the packet payload content. This approach has low requirements for device performance and good compatibility.

[0036] In addition, when the routers in the network are high-performance models with deep packet inspection (DPI) capabilities, two methods can be used for implementation: Using ACL (same as the aforementioned implementation method): as a basic implementation scheme, it is equally effective.

[0037] The DPI (Deep Interface) approach (enhanced solution) utilizes the router's DPI engine to perform deep parsing of network packets. This not only checks IP addresses and port numbers but also analyzes whether the packet payload conforms to the DNS protocol's packet format and characteristics (such as specific identification fields, flags, and the structure of query records). The DPI approach enables more accurate identification and filtering of DNS packets, even when DNS communication occurs on non-standard ports, enhancing the accuracy and reliability of the solution in complex network environments.

[0038] Specifically, the embodiments of the present invention enhance the deployability and adaptability of the solution. By providing two packet data identification methods (ACL and DPI), the technical solution is compatible with router devices of different performance and models. For low-end routers that do not support Deep Packet Inspection (DPI), the less performance-required Access Control List (ACL) method can be used for identification, lowering the implementation threshold of the technical solution and ensuring applicability on a wide range of devices.

[0039] Step S200: Based on the time points corresponding to the message data, the first response duration of the first request-response phase and the second response duration of the second request-response phase are obtained. It should be noted that the first message includes a first request message sent by the client to the proxy server and a first response message sent by the proxy server. In some embodiments, the first response duration of the first request-response phase is obtained by organizing the time points corresponding to the message data, which may include the following steps: taking the time point when the proxy server receives the first request message sent by the client as the first time point; taking the time point when the proxy server sends the first response message to the client as the fourth time point; wherein, the first response message is triggered by the proxy server receiving a second response message from the local server; and the first response duration is obtained based on the difference between the fourth time point and the first time point.

[0040] In some specific application scenarios, the calculation process for the first response time can be implemented as follows: 1. Record the first time point (T1): When the router receives a DNS query request message (i.e., the first request message) from a client (such as a laptop) through its WLAN (Wireless Local Area Network) interface, record the current time point as T1.

[0041] 2. Record the fourth time point (T4): Subsequently, when the router sends a DNS query response message (i.e., the first response message) to the laptop through the same WLAN interface, record the current time point as T4. It should be noted that this response message may be replied to directly by the router from its cache, or it may be forwarded after receiving a response from the upstream LDNS.

[0042] 3. Calculate the first response duration (ΔT1): The first response duration is the difference between the two time points mentioned above (ΔT1 = T4 - T1). This duration ΔT1 fully measures the total latency perceived by the client from sending a request to receiving a response, including all time spent on internal router cache lookups, processing, and possible upstream queries and network transmissions.

[0043] The key to this invention is that it uses the router itself as the reference point for time recording, accurately measuring the "end-to-end" time spent processing DNS proxy services, thus providing the most direct performance indicators for the client's experience.

[0044] Specifically, embodiments of the present invention provide an accurate and reliable method for calculating the first response time. This method explicitly uses the proxy server (router) as the anchor point for time recording, measuring the total processing time from when it receives a client request to when it finally sends out a response. This time encompasses the latency of all processing stages within the router itself, including cache lookups, forwarding decisions, waiting for upstream responses, and packet transmission. It can accurately and comprehensively reflect the router's performance as a DNS proxy, providing a solid data foundation for accurately identifying bottlenecks.

[0045] It should be noted that the second message includes a second request message sent by the proxy server to the local server and a second response message sent by the local server. In some embodiments, the second response duration of the second request-response phase is obtained by organizing the time points corresponding to the message data, which may include the following steps: taking the time point when the proxy server sends the second request message as the second time point; taking the time point when the proxy server receives the second response message from the local server as the third time point; and obtaining the second response duration based on the difference between the third time point and the second time point.

[0046] In some specific application scenarios, the calculation process for the first response time can be implemented as follows: 1. Record the second time point (T2): After the router receives the client's request (T1), if no match is found in its local cache, it needs to query upstream. At this time, the router will send a DNS query request message (i.e., the second request message) to the local DNS server (LDNS) designated by the operator through its WAN (Wide Area Network) interface, and record the current time point as T2 when sending the message.

[0047] 2. Record the third time point (T3): After a period of waiting, when the router receives a DNS response message (i.e., the second response message) from LDNS through its WAN interface, record the current time point as T3.

[0048] 3. Calculate the second response time (ΔT2): The second response time is the difference between the two time points mentioned above (ΔT2 = T3 - T2). This time ΔT2 mainly measures the time taken for a complete DNS query between the router and the upstream LDNS, which mainly includes the network round-trip time (RTT) and the processing time of the LDNS server itself.

[0049] The key to this invention lies in its isolation of the overhead of internal router processing, focusing solely on measuring the core performance of the "network + upstream server" combination. This provides a crucial benchmark for determining whether the performance bottleneck resides within the router or in the external network. Since the router and client are on the same network side (CE side), this ΔT2 can be approximated as the performance level achievable by the client if it directly connects to the LDNS.

[0050] Specifically, embodiments of the present invention provide an accurate and reliable method for calculating the second response time. This method measures the core latency of network communication and processing between the proxy server (router) and the upstream LDNS, namely, the network transmission time plus the LDNS server's own processing time. This data serves as a performance benchmark for comparison with the first response time, thereby clearly separating the impact of network latency and the router's own performance overhead, making the judgment that "the router is the performance bottleneck" more scientific and accurate.

[0051] For example, in some specific implementations, the time point when the router receives the DNS_Query_Request from the client is T1, the time point when the router sends the DNS_Query_Response is T4, the time point when the router sends the DNS_Query_Request to the LDNS is T2, and the time point when the router receives the LDNS's Response is T3. Since both the router and the PC are located on the CE (Customer Edge) side of the network from the perspective of the LDNS, the response time of the request to the LDNS can be compared with the response time of the PC (i.e., the client) directly sending a request to the LDNS.

[0052] Step S300: When the duration of the first response is greater than a preset multiple of the duration of the second response, the network configuration parameters of the local server are sent to the client so that the client can establish a domain name service resolution link with the local server. It should be noted that in some embodiments, such as Figure 4 As shown, when the client deploys an agent, the network configuration parameters of the local server can be sent to the client, which may include the following steps: S311, the client uses the agent to re-initiate the interaction process of the dynamic host configuration protocol, and generates a discovery message according to the first stage of the interaction process; S312, in response to the discovery message, the second stage of the interaction process is triggered by the service module of the proxy server, and the network configuration parameters of the local server are sent to the client using a provision message.

[0053] For example, in some specific implementations, where an agent can be deployed on the client side, the agent can re-initiate the DHCP Discovery process. The router's DHCP Server module then reissues the IP address and lease information via DHCP Offer, and simultaneously issues the DNS configuration. The LDNS is issued directly, so the next time the terminal initiates a DNS request, it will directly send it to the LDNS, bypassing the router proxy and forwarding.

[0054] In some specific application scenarios, taking an enterprise office computer (client) pre-installed with a network optimization agent software, and this computer currently accessing the internet through an outdated gateway router with its DNS set to the router's IP address as an example, when the agent is deployed on the client, the network configuration parameters of the local server can be sent to the client to configure the domain name service resolution link as follows: 1. The agent receives and triggers instructions: After the service module in the gateway router (proxy server) determines that its own DNS proxy performance is a bottleneck, it generates an optimization instruction containing the upstream operator's LDNS address and sends it to the agent on the office computer through the network.

[0055] 2. Initiating a DHCP Discovery Message (Phase 1): Upon receiving the instruction, the agent immediately and proactively operates the office computer's network adapter to re-initiate the DHCP interaction process. The agent first broadcasts a DHCP Discovery message on behalf of the client within the network to search for a DHCP server.

[0056] 3. Router Response and Provision of New Configuration (Phase Two): After the DHCP service module within the gateway router detects the discovery message, it triggers the second phase of the interaction process. The router then replies to the office computer with a DHCP Offer message. In this message, in addition to basic information such as IP address allocation and lease period, the key is that the LDNS server address obtained from the ISP is directly entered in the "DNS Server" option field, instead of the router's own IP address.

[0057] 4. Client updates configuration and establishes new link: The office computer accepts the offer message and completes the subsequent DHCP request and acknowledgment (Ack) process. Ultimately, the DNS server address in its network configuration is updated to the LDNS address.

[0058] Effect achieved: From this point on, whenever a user triggers any DNS request on this office computer, the query message will be sent directly to the LDNS server, bypassing the proxy and forwarding processes of the old router. This completely avoids the router's performance bottleneck and significantly improves domain name resolution speed.

[0059] Specifically, embodiments of the present invention provide a proactive and rapid configuration update mechanism. When a client deploys an agent, a DHCP re-interaction process can be triggered immediately, without waiting for the lease to expire. This enables optimization strategies to take effect in real time, minimizing the duration of performance issues perceived by the user and improving the immediacy and proactivity of the optimization experience.

[0060] It should be noted that in some embodiments, such as Figure 5 As shown, when the client has not deployed an agent, sending the network configuration parameters of the local server to the client may include the following steps: S322, obtaining the lease information of the client's Dynamic Host Configuration Protocol (DMP); S323, when the lease expires, re-initiating the DMP interaction process through the client, and generating a discovery message according to the first stage of the interaction process; S324, in response to the discovery message, triggering the second stage of the interaction process through the service module of the proxy server, and sending the network configuration parameters of the local server to the client using a provision message.

[0061] For example, in some specific implementations, in cases where an Agent cannot be deployed on the client or is not deployed on the client, the LDNS needs to be issued when the Client's DHCP lease expires and the DHCP Discovery process is re-initiated. The next time the terminal initiates a DHCP Discovery process, the router's DHCP Server module reissues the IP address and lease information via DHCP Offer, and simultaneously issues the DNS configuration. Alternatively, if the LDNS is issued directly, the next DNS request from the terminal will be sent directly to the LDNS, bypassing the router's proxy and forwarding.

[0062] In some specific application scenarios, consider an employee's personal mobile phone (client) connecting to the company network. This phone, as an external device, does not have and does not need to have any specific agent software installed. Taking the DNS proxy performance of the company's outgoing router as a bottleneck, when the client does not have an agent deployed, sending the network configuration parameters from the local server to the client to configure the domain name service resolution link can achieve the following: 1. Obtain Lease Information and Wait: After making an optimization decision, the service module of the company's outbound router (proxy server) first queries its DHCP server's address lease pool to obtain the DHCP lease information of the mobile phone, including its IP address and lease duration. Subsequently, the service module does not actively terminate the connection but waits for the current lease to expire.

[0063] 2. Client-initiated renewal (Phase 1): When the DHCP lease expires (or after a reboot), the DHCP client within the operating system will automatically re-initiate the DHCP interaction process according to the standard protocol. The phone first broadcasts a DHCP discovery message on the local network.

[0064] 3. Router Response and Provision of New Configuration (Phase Two): After the company router's DHCP service module detects this discovery message, it triggers the second phase of the interaction process. The router then replies to the mobile phone with a DHCP Offer message. In this message, the ISP's LDNS server address is directly entered in the "DNS Server" field, replacing the router's own address.

[0065] 4. Client accepts and updates configuration: After receiving this message, the mobile phone goes through the subsequent request and acknowledgment process and finally accepts the new network configuration, and its DNS server address is updated to the LDNS address.

[0066] Effect achieved: From then on, when a user triggers any DNS request using this mobile phone, the query message will be sent directly to the LDNS server, without going through the company router's proxy and forwarding processing.

[0067] Specifically, this invention provides a highly compatible and robust configuration update mechanism. For traditional clients without deployed intelligent agents, this method utilizes the existing DHCP lease renewal mechanism to achieve configuration updates. This is a "natural" optimization approach that requires no modifications to existing clients, avoids compatibility issues, ensures that the technical solution can smoothly cover all terminal devices in the network, and enhances the universality and operability of the solution.

[0068] It should be noted that in some embodiments, the method may further include the following steps: when the client triggers a DNS request, the DNS request is sent to the local server based on the domain name service resolution link, so that the local server responds to the DNS request and performs DNS resolution.

[0069] For example, in some specific implementations, taking the case where a user's personal computer (client) has successfully updated its DNS server address to the operator's LDNS address through a DHCP process, subsequent DNS resolution (e.g., when a user tries to access a video website in daily use) can be achieved as follows: 1. Client triggers DNS request: The user enters the URL of a video website in their browser and presses Enter. In order to establish a connection, the operating system needs to resolve the domain name into an IP address. Therefore, the system triggers a DNS request for that domain name.

[0070] 2. The request is sent via the newly established resolution link: Based on the latest network configuration, the operating system will no longer send this DNS query message to the router's IP address. Instead, it will send the DNS request directly to the ISP's high-performance local DNS server (LDNS) based on the network configuration parameters of the distributed Local DNS Server (LDNS). This direct communication path is the established "Domain Name Service Resolution Link".

[0071] 3. The local server responds and completes the resolution: After receiving the direct request, the ISP's LDNS server looks up the IP address in its cache or performs an iterative query on behalf of the client. Finally, it successfully completes the DNS resolution and returns the corresponding IP address as a response message to the client.

[0072] Result: After obtaining an IP address, the client can establish a TCP connection with the video server and begin smoothly loading video content. Because the entire resolution process completely bypasses the low-performance egress router, avoiding the latency and processing bottlenecks that might be introduced by its proxy forwarding and cache queries, the speed and success rate of domain name resolution are significantly improved, thus fundamentally solving the problem of "slow internet access due to DNS issues" in the background technology.

[0073] Specifically, the embodiments of this invention clarify the final implementation effect of the technical solution. After the intelligent configuration is distributed, subsequent DNS requests from the client will be directly sent to the higher-performance LDNS, completely bypassing the performance bottleneck of the original router. This ultimately achieves a substantial improvement in domain name resolution performance, verifies the effectiveness and value of the entire technical solution, and directly solves the core problem of "slow internet access performance due to DNS issues" raised in the background technology.

[0074] To explain in detail the principle of the technical solution of the present invention, the overall process of the present invention will be described below with reference to some specific embodiments. It is easy to understand that the following is an explanation of the technical principle of the present invention and should not be regarded as a limitation of the present invention.

[0075] First, it's important to note that in scenarios where a standard or low-end router serves as the internal network exit point and performs simple NAT, slow internet access can occur due to DNS issues. This is primarily due to the DNS performance of the exit router itself (often related to the router's CPU, memory, or design). However, relying solely on the router's inherent performance for DNS resolution is ultimately pointless and can be completely mitigated by modifying DNS-related network configurations.

[0076] In view of this, the present invention provides a method for improving the performance of intranet domain name resolution to identify this situation and automatically complete the configuration changes accordingly, such as... Figure 6As shown, the method for improving intranet domain name resolution performance according to the present invention can be implemented through the following process: 1. Identify DNS packets using Deep Packet Inspection (DPI) or Access Control Lists (ACLs); 2. Based on the interval between the DNS_QUERY_REQUEST message sent by the client and the DNS_QUERY_RESPONSE message recovered by the router, determine whether the DNS resolution response time exceeds the threshold. 3. Based on the DNS server configured on the router (used here for FORWARDING), send the DNS server configuration to the Client via DHCP.

[0077] In some specific application scenarios, embodiments of the present invention can be used when a low-to-mid-range router is used as a network management device to access the Internet or other large networks. In such cases, where DHCP does not allocate DNS by default, the network management device's DNS forwarding performance is poor, resulting in a poor network experience for the end user. Specifically, the solution of this invention is to redirect (in one go) the poorly performing DNS request and subsequent DNS requests from the terminal to the correct LDNS through a series of sequential protocol processes. This reconfiguration requires no manual intervention from the customer. Figure 6 As shown, the method for improving intranet domain name resolution performance according to the present invention can be specifically implemented as follows: 1) Identify DNS messages: By identifying the UDP port 53 of the uplink packets, as well as the four types of DNS packets (forwarding packets, response packets, etc.) (all of which can be identified by ACLs to identify IP and port numbers), if the router itself supports DPI, the DPI capability can also be utilized. 2) Compare and calculate response times: The time point when the router receives the DNS_Query_Request from the Client is T1, the time point when the router sends the DNS_Query_Response is T4, the time point when the router sends the DNS_Query_Request to the LDNS is T2, and the time point when the router receives the LDNS's Response is T3.

[0078] Since both the router and the PC are located on the CE (Customer Edge) side of the network for the LDNS, the response time for requests to the LDNS can be compared with the response time for requests directly from the PC (i.e., the Client) to the LDNS.

[0079] If T4-T1>2*(T3-T2), it can be considered to exceed the threshold. Here, we take a preset multiple of 2 as an example. The preset multiple can be adjusted according to actual needs. For example, if the network requirements are higher, it can be adjusted to 1.5. If the network requirements are more relaxed, it can be adjusted to 3. That is, the time added after DNS proxy is much greater than the time of normal resolution by LDNS.

[0080] 3) In the next DHCP process, DNS is issued via DHCP Offer: Scenario 1: In cases where an agent can be deployed on the client side, the agent can re-initiate the DHCP Discovery process. The router's DHCP Server module will then reissue the IP address and lease information via DHCP Offer, and simultaneously issue the DNS configuration (e.g., ...). Figure 7 The image shows an example of DNS network configuration parameters. The LDNS is directly deployed, so the next time a terminal initiates a DNS request, it will be sent directly to the LDNS, bypassing the router proxy and forwarding.

[0081] Scenario 2: For situations where an Agent cannot be deployed on the client or is not deployed on the client, the LDNS needs to be issued when the Client's DHCP lease expires and the DHCP Discovery process is re-initiated. The next time the terminal initiates a DHCP Discovery process, the router's DHCP Server module reissues the IP address and lease information via DHCP Offer, and simultaneously issues the DNS configuration. Alternatively, the LDNS can be issued directly, so the next DNS request from the terminal will be sent directly to the LDNS, bypassing the router's proxy and forwarding.

[0082] Specifically, embodiments of the present invention can automatically optimize the DNS process without requiring customers to be proficient in router configuration. By identifying and correcting errors, it improves the efficiency of DNS resolution and reduces the impact of slow DNS resolution caused by router performance issues, thus affecting the final customer's internet experience. Furthermore, for 5G industry private networks, especially in ULCL scenarios, mobile hotspots and DTUs often serve as gateways for converting 5G into Wi-Fi intranets. Mobile devices and other terminals not only have generally low performance but also find it difficult to manually configure and distribute DNS. Optimizing the DNS resolution mode through the methods of the present invention can improve the user experience and reduce network management pressure and its impact. Specifically, as... Figure 8As shown, in a 5G ULCL dual-domain industry private network, terminals often access the 5G private network through CPE or even mobile hotspots. In this case, the mobile phone acts as a DHCP server and DHCP proxy, resulting in poor performance. Moreover, it is difficult to manually configure DHCP-related options on the mobile phone. However, the technical solution of this invention can guide the end user to directly interact with the LDNS from the network side, thereby improving performance.

[0083] In summary, this invention, through a novel process design combining DNS and DHCP procedures, replaces the terminal DNS in slow DNS resolution scenarios. This redirects internal DNS resolution requests, originally directed to the local network management router, to LDNS, lowering the barrier to DNS processing for network administrators, improving the end-user experience, and reducing the complexity of network configuration optimization. Simultaneously, it addresses the DNS resolution experience in scenarios such as mobile hotspots where DNS configuration is inconvenient, thus enhancing the final network access experience.

[0084] Compared with the prior art, the main advantages of the embodiments of the present invention are: 1. The embodiments of the present invention are very close to the usual usage scenarios of end users, and correct a large number of functional points with poor end-user experience, and the correction does not require manual intervention. The prior art has not considered such problems.

[0085] 2. The embodiments of this invention effectively reduce the deployment and configuration costs of commercial scenarios such as 5G industry private networks, and provide solutions to improve the experience of a large number of low-end routers, general-performance CPEs / DTUs, and the increasingly common mobile hotspot scenarios. It has a wide range of applications and good compatibility.

[0086] Compared to existing technologies, the main inventiveness of this invention lies in: 1. Focusing on details, we provide configuration-free optimization services at key experience points to enhance customer experience; 2. It creatively combines DHCP Forwarding and DHCP, automatically eliminating forwarding performance issues and lowering the barrier to entry for using routers, DTUs, and mobile hotspots; 3. The final effect can be achieved whether the terminal has an agent or not.

[0087] 4. Low requirements for mobile terminals, CPEs, etc.

[0088] Specifically, the application scenarios of the embodiments of the present invention include, but are not limited to: 1. It can be widely used in the configuration of home routers and low-end enterprise routers, or as an option provided by the router; 2. It can be widely used in mobile hotspots, and is especially recommended for use in industry private network ULCL scenarios.

[0089] Specifically, embodiments of the present invention significantly improve the performance of mobile hotspots and router DNS through automated, configuration-free methods, thereby enhancing the user experience. Furthermore, embodiments of the present invention can reduce the obstacles to the promotion of 5G industry private networks, campus private networks, and the like.

[0090] like Figure 9 As shown, this embodiment of the invention also provides a device 900 for improving intranet domain name resolution performance, which can implement the above-described method. This device may include: The data acquisition module 910 is used to acquire message data from the domain name server; The domain name server includes a proxy server and a local server, and the message data includes the first message of the first request-response phase between the client and the proxy server and the second message of the second request-response phase between the proxy server and the local server. The duration processing module 920 is used to process the message data based on the corresponding time points to obtain the first response duration of the first request response stage and the second response duration of the second request response stage. The link establishment module 930 is used to send the network configuration parameters of the local server to the client when the duration of the first response is greater than a preset multiple of the duration of the second response, so that the client can establish a domain name service resolution link with the local server.

[0091] In some embodiments, the apparatus may further include a request parsing module for performing the following operations: When a client triggers a DNS request, the DNS request is sent to the local server based on the domain name service resolution link, so that the local server responds to the DNS request and performs DNS resolution.

[0092] It is understood that the content of the above method embodiments is applicable to the present device embodiments. The specific functions implemented by the present device embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0093] This invention also provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the method described above. This electronic device can be any smart terminal, including tablet computers, in-vehicle computers, etc.

[0094] It is understood that the content of the above method embodiments is applicable to this device embodiment. The specific functions implemented by this device embodiment are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0095] like Figure 10 As shown, Figure 10The hardware structure of an electronic device 1000 according to another embodiment is illustrated. The electronic device 1000 includes: The processor 1001 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (aSIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present invention. The memory 1002 can be implemented as a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RaM). The memory 1002 can store the operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 1002 and is called and executed by the processor 1001. Input / output interface 1003 is used to implement information input and output; The communication interface 1004 is used to enable communication and interaction between this device and other devices. Communication can be achieved through wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.). Bus 1005 transmits information between various components of the device (e.g., processor 1001, memory 1002, input / output interface 1003, and communication interface 1004); The processor 1001, memory 1002, input / output interface 1003 and communication interface 1004 are connected to each other within the device via bus 1005.

[0096] The electronic device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0097] This invention also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described method.

[0098] It is understood that the content of the above method embodiments is applicable to this storage medium embodiment. The specific functions implemented in this storage medium embodiment are the same as those in the above method embodiments, and the beneficial effects achieved are also the same as those achieved in the above method embodiments.

[0099] This invention also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0100] It is understood that the content of the above method embodiments is applicable to the embodiments of this program product. The specific functions implemented by the embodiments of this program product are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0101] Memory, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory may optionally include memory remotely located relative to the processor, and these remote memories can be connected to the processor via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0102] The present invention provides a method, apparatus, electronic device, storage medium, and program product for improving intranet domain name resolution performance. This method acquires message data from a domain name server. The domain name server includes a proxy server and a local server. The message data includes a first message from the first request-response phase between the client and the proxy server, and a second message from the second request-response phase between the proxy server and the local server. Based on the time points corresponding to the message data, the first response duration of the first request-response phase and the second response duration of the second request-response phase are obtained. When the first response duration is greater than a preset multiple of the second response duration, the network configuration parameters of the local server are sent to the client, enabling the client to establish a domain name service resolution link with the local server. The present invention provides a proactive and intelligent optimization mechanism. By comparing the response durations of the client-proxy server (router) and proxy server-local server (LDNS) phases, it is possible to accurately determine whether the performance bottleneck lies in the router itself. Once confirmed (the first response takes much longer than the second response), the upstream LDNS address is automatically sent directly to the client, enabling the client to establish a direct resolution link to the LDNS. This effectively avoids the processing delays and cache query overhead of low-performance routers, significantly improving the efficiency and speed of domain name resolution, and ultimately improving the user's network access experience.

[0103] The embodiments described in this invention are for the purpose of more clearly illustrating the technical solutions of the embodiments of this invention, and do not constitute a limitation on the technical solutions provided by the embodiments of this invention. As those skilled in the art will know, with the evolution of technology and the emergence of new application scenarios, the technical solutions provided by the embodiments of this invention are also applicable to similar technical problems.

[0104] Those skilled in the art will understand that the technical solutions shown in the figures do not constitute a limitation on the embodiments of the present invention, and may include more or fewer steps than shown, or combine certain steps, or different steps.

[0105] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0106] Those skilled in the art will understand that all or some of the steps in the methods disclosed above, as well as the functional modules / units in the systems and devices, can be implemented as software, firmware, hardware, or suitable combinations thereof.

[0107] The terms "first," "second," "third," "fourth," etc. (if present) in the specification and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0108] It should be understood that in this invention, "at least one (item)" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0109] In the several embodiments provided by this invention, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of the units described above is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0110] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0111] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0112] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes multiple instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing programs, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0113] The preferred embodiments of the present invention have been described above with reference to the accompanying drawings, but this does not limit the scope of the claims of the present invention. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and spirit of the present invention should be within the scope of the claims of the present invention.

Claims

1. A method for improving the performance of intranet domain name resolution, characterized in that, The method includes the following steps: Obtain message data from the domain name server; The domain name server includes a proxy server and a local server, and the message data includes a first message in the first request-response phase between the client and the proxy server and a second message in the second request-response phase between the proxy server and the local server. Based on the time points corresponding to the message data, the first response duration of the first request-response phase and the second response duration of the second request-response phase are obtained; When the duration of the first response is greater than a preset multiple of the duration of the second response, the network configuration parameters of the local server are sent to the client so that the client can establish a domain name service resolution link with the local server.

2. The method according to claim 1, characterized in that, The process of obtaining message data from the domain name server includes the following steps: When the proxy server does not support deep packet inspection, the packet data is identified based on the access control list. When the proxy server supports the deep packet inspection, it identifies the packet data based on the deep packet inspection or the access control list.

3. The method according to claim 1, characterized in that, The first message includes a first request message sent by the client to the proxy server and a first response message sent by the proxy server. The step of calculating the first response duration of the first request-response phase based on the time points corresponding to the message data includes the following steps: The time point at which the proxy server receives the first request message sent by the client is taken as the first time point; The time point at which the proxy server sends the first response message to the client is taken as the fourth time point; The first response message is triggered based on the second response message received by the proxy server from the local server; The first response duration is obtained based on the difference between the fourth time point and the first time point.

4. The method according to claim 1, characterized in that, The second message includes a second request message sent by the proxy server to the local server and a second response message sent by the local server. The step of calculating the second response duration of the second request-response phase based on the time points corresponding to the message data includes the following steps: The time point at which the proxy server sends the second request message is taken as the second time point; The time when the proxy server receives the second response message from the local server is taken as the third time point; The second response duration is obtained based on the difference between the third time point and the second time point.

5. The method according to claim 1, characterized in that, When the client has an agent deployed, the step of sending the network configuration parameters of the local server to the client includes the following steps: The client re-initiates the interaction process of the Dynamic Host Configuration Protocol using the intelligent agent, and generates a discovery message according to the first phase of the interaction process. In response to the discovery message, the second phase of the interaction process is triggered by the service module of the proxy server, which sends the network configuration parameters of the local server to the client using a provision message.

6. The method according to claim 1, characterized in that, When the client has not deployed an agent, the step of sending the network configuration parameters of the local server to the client includes the following steps: Obtain the lease information of the Dynamic Host Configuration Protocol (DIP) of the client; When the lease information expires, the client re-initiates the interaction process of the dynamic host configuration protocol and generates a discovery message according to the first stage of the interaction process. In response to the discovery message, the second phase of the interaction process is triggered by the service module of the proxy server, which sends the network configuration parameters of the local server to the client using a provision message.

7. The method according to any one of claims 1 to 6, characterized in that, The method further includes the following steps: When the client triggers a DNS request, it sends the DNS request to the local server based on the domain name service resolution link, so that the local server responds to the DNS request and performs DNS resolution.

8. A device for improving the performance of intranet domain name resolution, characterized in that, The device includes: The data acquisition module is used to acquire message data from the domain name server; The domain name server includes a proxy server and a local server, and the message data includes a first message in the first request-response phase between the client and the proxy server and a second message in the second request-response phase between the proxy server and the local server. The duration processing module is used to process the message data based on the time points corresponding to the first request-response phase and the second response phase. The link establishment module is used to send the network configuration parameters of the local server to the client when the duration of the first response is greater than a preset multiple of the duration of the second response, so that the client can establish a domain name service resolution link with the local server.

9. An electronic device, characterized in that, The electronic device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the method according to any one of claims 1 to 7.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method of any one of claims 1 to 7.

Images