DNS query intermediate result response method, recursive server and client

By introducing pseudo resource record information and query process control parameters into DNS query requests, the recursive server returns intermediate results when cname chain query fails, solving the problem of no data response when cname chain fails in DNS recursive query, improving query efficiency and User experience.

CN118945141APending Publication Date: 2024-11-12INTERNET DOMAIN NAME SYST BEIJING ENG RES CENT
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411065495.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-05
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

During the DNS recursive query process, when the cname chain fails before obtaining the final result, the recursive server returns a servfail response result without data, resulting in the client waiting time for a long time but not obtaining helpful data, and there is room for optimization.

Method used

By introducing client-defined pseudo-resource record information, including result integrity identification and query process control parameters, the recursive server allows the recursive server to return intermediate results when the complete result cannot be queried, and temporarily according to the timeout and retry strategy Save intermediate results, and return intermediate results and updated result integrity identifiers to the client.

Benefits of technology

It improves the query efficiency of the client during the cname chain query process, avoids long-term waiting, enhances the user experience, and provides more fault tolerance and recovery mechanisms, and optimizes the client query performance in specific scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118945141A_ABST
    Figure CN118945141A_ABST
Patent Text Reader

Abstract

The invention discloses a DNS (Domain Name Server) query intermediate result response method, a recursive server and a client, and aims to solve the problems that a complete result chain is returned when the traditional DNS query succeeds, no record is returned when the traditional DNS query fails, and no intermediate result exists. The DNS query request further comprises pseudo resource record information self-defined by a client, analyzing the DNS query request, initializing session variables in a recursive server according to the query process control parameters, and performing recursive query; and if a complete result cannot be queried according to the set timeout time and the retry strategy about the recursive query, temporarily storing an intermediate result obtained by query, correspondingly updating a result integrity identifier, and returning the intermediate result and the updated result integrity identifier to the client. Compared with the prior art, the method has the advantages that the existing query logic without an intermediate result is optimized, and the query performance of the client is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method for processing a DNS query request. Background Art

[0002] During the DNS (Domain Name System) recursive query process, you may encounter the situation where the query obtains a cname (canonical name) record. At this time, if the record type requested by the client is not the cname type itself, the queried cname record is not the final result required. At this time, the recursive server will switch the domain name pointed to by cname to the domain name currently queried, and re-initiate the recursive query until the required result is obtained.

[0003] In actual applications, there may be multiple levels of cnames, which will increase the pressure on the recursive server and may also increase the delay in the client query results. In extreme cases, if the authoritative end fails to respond to the query corresponding to a certain level of cname, it may also cause the entire client query to time out, and ultimately produce a servfail (DNS server response timeout, resolution failure) response result.

[0004] A typical DNS recursive server implementation will return a servfail result in the above failure scenario, and will not include the found cname chain in the response. The two effects are that the complete result chain is returned on success, and no records are returned on failure, and there is no intermediate result.

[0005] The inventors realize that when the cname chain fails before obtaining the final result, a servfail response result with no data is returned. In this way, the client spends a long waiting time but does not obtain data that is helpful for the query, and there is room for optimization. Summary of the invention

[0006] The present application provides a DNS query intermediate result response method, a recursive server and a client, aiming to solve the problem of returning a servfail response result with no data when the cname chain in the prior art fails before obtaining the final result, so that when the cname chain query process fails, the client's query can also make certain progress.

[0007] In a first aspect, a DNS query intermediate result answering method is provided, the method comprising:

[0008] Receive a DNS query request sent by a client, wherein the DNS query request also includes pseudo resource record information customized by the client, wherein the pseudo resource record information includes a result integrity identifier and a query process control parameter; the result integrity identifier is used to indicate whether a complete result is found; the query process control parameter includes a timeout time and a retry strategy for recursive query set by the client;

[0009] Parsing the DNS query request, and when a recursive query is involved, initializing a session variable inside the recursive server according to the query process control parameter, and performing a recursive query;

[0010] If a complete result is found, the result integrity identifier is updated accordingly, and the complete result and the updated result integrity identifier are returned to the client;

[0011] If a complete result cannot be queried according to the timeout period and retry strategy set for the recursive query, the intermediate result obtained by the query is temporarily stored, the result integrity identifier is updated accordingly, and the intermediate result and the updated result integrity identifier are returned to the client.

[0012] In the above solution, optionally, the query process control parameters include:

[0013] Client timeout, which indicates the total timeout time that the client plans to wait for this query;

[0014] During the recursive query process, the client timeout period of the client is triggered, and it is considered that the complete result cannot be queried. The intermediate result obtained by the query is temporarily stored, the result integrity identifier is updated accordingly, and the intermediate result and the updated result integrity identifier are returned to the client.

[0015] In the above solution, optionally, the query process control parameter also includes:

[0016] The single cname level query timeout of the recursive server indicates the total timeout that the client expects the recursive server to use when querying each level of cname;

[0017] During the recursive query process, if the single cname level query timeout of any level cname corresponding to the recursive server is triggered, it is considered that the complete result cannot be queried, the intermediate result obtained by the query is temporarily stored, the result integrity identifier is updated accordingly, and the intermediate result and the updated result integrity identifier are returned to the client.

[0018] In the above solution, optionally, the query process control parameter also includes:

[0019] The recursive target server timeout period indicates the timeout period for each outbound recursive query that the client expects the recursive server to have when making outbound queries.

[0020] During the recursive query process, the recursive target server timeout period of the recursive server is triggered, and the recursive server will record the number of retries and continue to use the next recursive server in the recursive server list.

[0021] In the above solution, optionally, the query process control parameter also includes:

[0022] Recursive target server retry count: indicates the number of retries that the client expects the recursive server to perform for each recursive server target used for external recursion when querying externally;

[0023] During the recursive query process, if the number of retries of the recursive target server of each recursive server reaches the upper limit, it is considered that the complete result cannot be queried, the intermediate results obtained by the query are temporarily stored, the result integrity identifier is updated accordingly, and the intermediate results and the updated result integrity identifier are returned to the client.

[0024] In the above scheme, optionally, in the DNS query request, the result integrity flag is set to 0; when a complete result is queried, the result integrity flag is set to 1; when a complete result cannot be queried, the result integrity flag is set to 2, and the other fields of the pseudo resource record information remain consistent with the values ​​sent by the client.

[0025] In a second aspect, a DNS query request method is provided, the method comprising:

[0026] The client sends a DNS query request to the recursive server, wherein the DNS query request also includes pseudo resource record information customized by the client, wherein the pseudo resource record information includes a result integrity identifier and a query process control parameter; the result integrity identifier is used to indicate whether a complete result is found; the query process control parameter includes a timeout time and a retry strategy for the recursive query set by the client;

[0027] After the recursive server completes the recursive query according to the set timeout time and retry strategy for the recursive query, the client receives a response message from the recursive server; if the recursive server obtains a complete result, the response message includes the complete result and the corresponding updated result integrity identifier; if the recursive server only obtains an intermediate result, the response message includes the intermediate result and the corresponding updated result integrity identifier;

[0028] The client parses the response message and determines whether the query request is completed normally based on the result integrity identifier.

[0029] In the above scheme, optionally, if the result integrity identifier obtained by the client's analysis indicates that only an intermediate result is obtained, the client switches to the end of the cname chain according to its own strategy, and then re-initiates a recursive query for the domain name at the end of the cname chain.

[0030] In the above solution, further optionally, the re-initiating of the recursive query for the cname domain name is to initiate a query request to other recursive servers.

[0031] In a third aspect, a recursive server comprises a memory, a processor and a computer program stored in the memory, wherein the recursive server executes the computer program to implement the steps of the method in the first aspect.

[0032] In a fourth aspect, a client comprises a memory, a processor and a computer program stored in the memory, wherein the client executes the computer program to implement the steps of the method in the second aspect.

[0033] Compared with the prior art, this application has at least the following beneficial effects:

[0034] This application is based on further analysis and research of existing technical problems, and recognizes that when a typical recursive server performs a recursive query, it returns a complete result chain when successful, and no records are returned when it fails, and there are no intermediate results. Through the negotiation of timeout and other information, the client can intervene in some behaviors of the server, achieve cooperation with the client, and make certain progress in the client's query. The existing query logic without intermediate results is optimized, and the client query performance in specific scenarios is improved.

[0035] In the above content, this application divides the query results into two categories through the result integrity identifier. The client can distinguish whether the response result is complete or incomplete (i.e., intermediate state) by only parsing the updated result integrity identifier, and thus make different response reactions according to its own strategy.

[0036] In the above content, this application controls the query process parameters (i.e., the client timeout, the single cname level query timeout of the recursive server, the recursive target server timeout, and the number of retries of the recursive target server) so that when any parameter is triggered, the intermediate result response process can be executed, so that the client can obtain part of the information earlier and give a corresponding response. While improving the query efficiency, it avoids the client from being in a suspended state for a long time and enhances the user experience. At the same time, since the client can give a response in time according to different situations, it is beneficial to the optimization of resources. The response of the intermediate result provides more fault tolerance and recovery mechanisms for the query process. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 A schematic diagram of an application environment of a DNS query intermediate result response method provided by an embodiment of the present application;

[0038] Figure 2 A flowchart of a method for responding to an intermediate result of a DNS query provided by an embodiment of the present application;

[0039] Figure 3 A flowchart of a DNS query request method provided by an embodiment of the present application;

[0040] Figure 4 is an internal structure diagram of a recursive server in one embodiment;

[0041] Figure 5 FIG. 4 is a diagram showing the internal structure of a client in one embodiment. DETAILED DESCRIPTION

[0042] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0043] In the description of this application: unless otherwise specified, "plurality" means two or more. "Including", "comprising", "having" and other expressions also mean "not limited to" (certain units, components, materials, steps, etc.).

[0044] The DNS query intermediate result response method provided by this application can be applied to Figure 1 In the application environment shown, the client 101 communicates with the DNS server 102 through the network. In this embodiment, the DNS server 102 is usually a recursive server, which can be implemented by an independent server or a server cluster composed of multiple servers.

[0045] In one embodiment, Figure 2 As shown, a DNS query intermediate result answering method is provided, and the method is applied to Figure 1 The server in the example is used to illustrate the following steps:

[0046] Receive a DNS query request sent by a client, wherein the DNS query request also includes pseudo resource record information customized by the client, wherein the pseudo resource record information includes a result integrity identifier and a query process control parameter; the result integrity identifier is used to indicate whether a complete result is found; the query process control parameter includes a timeout time and a retry strategy for recursive query set by the client;

[0047] Parsing the DNS query request, and when a recursive query is involved, initializing a session variable inside the recursive server according to the query process control parameter, and performing a recursive query;

[0048] If a complete result is found, the result integrity identifier is updated accordingly, and the complete result and the updated result integrity identifier are returned to the client;

[0049] If a complete result cannot be queried according to the timeout period and retry strategy set for the recursive query, the intermediate result obtained by the query is temporarily stored, the result integrity identifier is updated accordingly, and the intermediate result and the updated result integrity identifier are returned to the client.

[0050] In the context of DNS queries, the pseudo resource record information can be an extended OPT record that contains specific custom fields. Since the DNS standard itself does not support the direct addition of new RR types, additional options (Option Codes) are usually used in the OPT record to carry these custom data.

[0051] In this embodiment, the session variables of the recursive server are initialized correspondingly by using the query process control parameters through the customized pseudo resource record information, and the result integrity identifier is updated and different contents are returned to the client for different query results, which solves the problem that the traditional DNS recursive server returns a complete result chain when successful, and no records are returned when failed, and there is no intermediate result. Based on the negotiation of timeout and other information, the client can intervene in some behaviors of the server to achieve cooperation with the client. The existing query logic without intermediate results is optimized, and the client query performance in specific scenarios is improved.

[0052] In one embodiment, querying process control parameters includes:

[0053] Client timeout, which indicates the total timeout time that the client plans to wait for this query;

[0054] During the recursive query process, the client timeout period of the client is triggered, and it is considered that the complete result cannot be queried. The intermediate result obtained by the query is temporarily stored, the result integrity identifier is updated accordingly, and the intermediate result and the updated result integrity identifier are returned to the client.

[0055] In one embodiment, querying the process control parameter further includes:

[0056] The single cname level query timeout of the recursive server indicates the total timeout that the client expects the recursive server to use when querying each level of cname;

[0057] During the recursive query process, if the single cname level query timeout of any level cname corresponding to the recursive server is triggered, it is considered that the complete result cannot be queried, the intermediate result obtained by the query is temporarily stored, the result integrity identifier is updated accordingly, and the intermediate result and the updated result integrity identifier are returned to the client.

[0058] In one embodiment, querying the process control parameter further includes:

[0059] The recursive target server timeout period indicates the timeout period for each outbound recursive query that the client expects the recursive server to have when making outbound queries.

[0060] During the recursive query process, the recursive target server timeout period of the recursive server is triggered, and the recursive server will record the number of retries and continue to use the next recursive server in the recursive server list.

[0061] In one embodiment, querying the process control parameter further includes:

[0062] Recursive target server retry count: indicates the number of retries that the client expects the recursive server to perform for each recursive server target used for external recursion when querying externally;

[0063] During the recursive query process, if the number of retries of the recursive target server of each recursive server reaches the upper limit, it is considered that the complete result cannot be queried, the intermediate results obtained by the query are temporarily stored, the result integrity identifier is updated accordingly, and the intermediate results and the updated result integrity identifier are returned to the client.

[0064] When a recursive server sends a query request to a target DNS server, it will wait for a period of time to receive a response. If no response is received within this time, the recursive server will consider that the query attempt has timed out, and then decide whether to send a query request to the same target server again based on the number of retries of the recursive target server in timeouts.

[0065] If a recursive server fails to get a response from a target server after multiple attempts, that is, the recursive target server reaches the upper limit of retries, it will no longer try to send queries to the server, because further attempts are likely to get the same result.

[0066] In this case, the recursive server will not return a failed response immediately, but will check whether there are any intermediate results to return. Intermediate results refer to part of the information that has been obtained during the query process, that is, the CNAME record.

[0067] If there are intermediate results, the recursive server will execute the intermediate result response process. This means that the recursive server will organize these intermediate results into a response, set the result integrity flag in timeouts to 2 (incomplete result), and then send this response to the client that originally issued the query.

[0068] This process enables the client to obtain at least some information collected during the query before the query fails completely. This is valuable to the client because the client can make further decisions based on this information, such as re-initiating the query, or using this limited information to meet its needs. In some scenarios, such as when network conditions are poor or the DNS server is overloaded, the response process of intermediate results can improve the robustness of the query and the user experience.

[0069] In this embodiment, the customized pseudo resource record (OPT) information is named timeouts, and this name will be used to refer to the OPT later.

[0070] timeouts contains the following data fields:

[0071] A) Result integrity flag: A value of 0 means that this field is ignored and filled in during client encapsulation. A value of 1 means that the result is complete, and a value of 2 means that the result is incomplete.

[0072] B) Client timeout: The total timeout that the client plans to wait for this query, a 32-bit value in microseconds.

[0073] C) Single Cname level query timeout of the recursive server: The total timeout that the client expects the recursive server to use when querying each level of Cname, a 32-bit value in microseconds.

[0074] D) Recursive target server timeout: The timeout period for each outbound recursive query that the client expects the recursive server to have when making outbound queries. This is a 32-bit value in microseconds.

[0075] E) Recursive target server retry count: The number of retries that the client expects the recursive server to use for each external recursion when querying the recursive server. This is a 32-bit value.

[0076] In one embodiment, in the DNS query request, the result integrity flag is set to 0; when a complete result is queried, the result integrity flag is set to 1; when a complete result cannot be queried, the result integrity flag is set to 2, and other fields of the pseudo resource record information remain consistent with the values ​​sent by the client.

[0077] In this embodiment, when the client initiates a request, field A of timeouts is irrelevant to the client and is set to 0. Fields B, C, D, and E can be filled according to the client's own needs.

[0078] After receiving the query request, the recursive server will initialize the internal session variables with reference to the fields B, C, D, and E given by the client when recursion is involved.

[0079] The various timeouts used by the server when recursing outward will be added or adjusted based on the client's requirements.

[0080] If the timeout of the recursive server's outbound query is triggered, the number of retries will be recorded and the next recursive server in the recursive server list will be used.

[0081] When the number of retries for each server reaches the upper limit, the query is considered to be unfinished and the intermediate result response process is executed.

[0082] If the total timeout of the outward recursive query corresponding to any level of cname is triggered, the query will be considered unfinished and the intermediate result response process will be executed.

[0083] If the total timeout of the client query is triggered, the intermediate result response process will be executed directly.

[0084] The intermediate data obtained by the recursive server will be temporarily stored and used when responding. For incomplete results, you need to set the timeouts field A to 2 when responding, keep the other fields consistent with the values ​​sent by the client, and then respond. For complete results, set the timeouts field A to 1, keep the other fields consistent with the values ​​sent by the client, and then respond normally.

[0085] In this embodiment, during the recursive query process, when any one of field B (client timeout field), field C (single cname level query timeout field of the recursive server) and field E (recursive target server retry count field) is triggered, the response process of the intermediate result should be executed.

[0086] Since fields B, C, and E are filled according to the client's own needs, when any one of fields B, C, and E is triggered, the response process of the intermediate result is executed. The client can obtain some information earlier and decide whether to continue waiting, adjust the query strategy, or perform other operations in advance, thereby avoiding the client from being in a suspended state for a long time and consuming a large amount of system resources due to continued waiting, providing more fault tolerance and recovery mechanisms for the query process.

[0087] The timeout of the recursive server's outward query is triggered, that is, the time of the recursive server's outward query exceeds the custom recursive target server timeout field (field D). At this time, the number of retries of the recursive server needs to be recorded and the next server in the server list needs to be used to query.

[0088] In one embodiment, Figure 3 As shown, a DNS query request method is provided, which is applied to Figure 1 The following steps are used as an example to illustrate the client:

[0089] The client sends a DNS query request to the recursive server, wherein the DNS query request also includes pseudo resource record information customized by the client, wherein the pseudo resource record information includes a result integrity identifier and a query process control parameter; the result integrity identifier is used to indicate whether a complete result is found; the query process control parameter includes a timeout time and a retry strategy for the recursive query set by the client;

[0090] After the recursive server completes the recursive query according to the set timeout time and retry strategy for the recursive query, the client receives a response message from the recursive server; if the recursive server obtains a complete result, the response message includes the complete result and the corresponding updated result integrity identifier; if the recursive server only obtains an intermediate result, the response message includes the intermediate result and the corresponding updated result integrity identifier;

[0091] The client parses the response message and determines whether the query request is completed normally based on the result integrity identifier.

[0092] In one embodiment, if the integrity identifier of the result parsed by the client indicates that only an intermediate result is obtained by the query, the client switches to the end of the cname chain according to its own strategy, and then re-initiates a recursive query for the domain name at the end of the cname chain.

[0093] In one embodiment, the re-initiating of the recursive query for the cname domain name is to initiate a query request to other recursive servers.

[0094] After receiving the response, the client will check field A. If it is a complete result, it can end normally. If it is an intermediate result, it will switch to the end of the cname chain according to its own strategy, and then re-initiate a recursive query for the cname domain name (you can choose to initiate a query to other recursive servers).

[0095] The cname record in DNS allows one domain name to become an alias of another domain name. For example, www.example.com can be set as the cname of example.com, so that visiting www.example.com is equivalent to visiting example.com.

[0096] However, cname records may form a chain structure, that is, a cname record points to another cname record, and so on, until a record without a cname is reached. This chain structure will cause additional delays because the DNS resolver needs to resolve the cname records one by one until the final target IP address is found.

[0097] In order to avoid performance problems caused by too many cname jumps, some DNS resolvers will jump directly to the end of the cname chain, that is, directly resolve to the last domain name without a cname record, and then initiate a recursive query for this domain name.

[0098] Assume the following cname record chain:

[0099] 1.`www.example.com`->`cdn.example.net`

[0100] 2.`cdn.example.net`->`static.example.org`

[0101] 3. `static.example.org` -> `192.168.1.1` (this is an A record, not a cname)

[0102] When a DNS resolver receives a query request for `www.example.com`, according to the traditional resolution process, it will first resolve the cname record of `www.example.com` to obtain `cdn.example.net`, then continue to resolve `cdn.example.net` to obtain `static.example.org`, and finally resolve `static.example.org` to obtain the final IP address `192.168.1.1`.

[0103] However, if the DNS resolver implements the above optimization strategy, it may recognize the existence of the cname chain during the first resolution, and be able to skip the intermediate cname and directly query `static.example.org`, thereby reducing one or more unnecessary DNS queries and improving resolution efficiency.

[0104] This strategy can significantly reduce resolution delay and improve user experience when the cname chain is very long.

[0105] In one embodiment, a recursive server is provided, whose internal structure diagram can be as follows: Figure 4 As shown. The recursive server includes a processor, a memory and a network interface connected through a system bus. The processor of the recursive server is used to provide computing and control capabilities, and the network interface is used to communicate with an external terminal through a network connection. The recursive server loads and runs a computer program to implement the above-mentioned DNS query intermediate result answering method.

[0106] In one embodiment, a client is provided, whose internal structure diagram can be as follows: Figure 5 As shown. The client includes a processor, a memory and a network interface connected through a system bus. The processor of the client is used to provide computing and control capabilities, and the network interface is used to communicate with an external terminal through a network connection. The client implements the above-mentioned DNS query request method by loading and running a computer program.

[0107] Those skilled in the art will understand that Figure 4-Figure 5 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0108] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

Claims

1. A DNS query intermediate result answering method, characterized in that: include: Receive a DNS query request sent by a client, wherein the DNS query request further includes pseudo resource record information customized by the client, wherein the pseudo resource record information includes a result integrity identifier and a query process control parameter; the result integrity identifier is used to indicate whether a complete result is found; The query process control parameters include the timeout time and retry strategy for recursive query set by the client; Parsing the DNS query request, and when a recursive query is involved, initializing a session variable inside the recursive server according to the query process control parameter, and performing a recursive query; If a complete result is found, the result integrity identifier is updated accordingly, and the complete result and the updated result integrity identifier are returned to the client; If a complete result cannot be queried according to the timeout period and retry strategy set for the recursive query, the intermediate result obtained by the query is temporarily stored, the result integrity identifier is updated accordingly, and the intermediate result and the updated result integrity identifier are returned to the client.

2. The DNS query intermediate result answering method according to claim 1, characterized in that: The query process control parameters include: Client timeout, which indicates the total timeout time that the client plans to wait for this query; During the recursive query process, the client timeout period of the client is triggered, and it is considered that the complete result cannot be queried. The intermediate result obtained by the query is temporarily stored, the result integrity identifier is updated accordingly, and the intermediate result and the updated result integrity identifier are returned to the client.

3. The DNS query intermediate result answering method according to claim 1, characterized in that: The query process control parameters also include: The single cname level query timeout of the recursive server, which indicates the total timeout that the client expects the recursive server to use when querying each level of cname; During the recursive query process, if the single cname level query timeout of any level cname corresponding to the recursive server is triggered, it is considered that the complete result cannot be queried, the intermediate result obtained by the query is temporarily stored, the result integrity identifier is updated accordingly, and the intermediate result and the updated result integrity identifier are returned to the client.

4. The DNS query intermediate result answering method according to claim 1, characterized in that: The query process control parameters also include: The recursive target server timeout period indicates the timeout period for each outbound recursive query that the client expects the recursive server to have when making outbound queries. During the recursive query process, the recursive target server timeout period of the recursive server is triggered, and the recursive server will record the number of retries and continue to use the next recursive server in the recursive server list.

5. The DNS query intermediate result answering method according to claim 1, characterized in that: The query process control parameters also include: Recursive target server retry count: indicates the number of retries that the client expects the recursive server to perform for each recursive server target used for external recursion when querying externally; During the recursive query process, if the number of retries of the recursive target server of each recursive server reaches the upper limit, it is considered that the complete result cannot be queried, the intermediate results obtained by the query are temporarily stored, the result integrity identifier is updated accordingly, and the intermediate results and the updated result integrity identifier are returned to the client.

6. The DNS query intermediate result answering method according to claim 1, characterized in that: include: In the DNS query request, the result integrity flag is set to 0; When a complete result is found, the result integrity flag is set to 1; when a complete result cannot be found, the result integrity flag is set to 2; other fields of the pseudo resource record information remain consistent with the values ​​sent by the client.

7. A DNS query request method, characterized in that: include: The client sends a DNS query request to the recursive server, wherein the DNS query request also includes pseudo resource record information customized by the client, wherein the pseudo resource record information includes a result integrity identifier and a query process control parameter; the result integrity identifier is used to indicate whether a complete result is found; The query process control parameters include the timeout time and retry strategy for recursive query set by the client; After the recursive server completes the recursive query according to the set timeout time and retry strategy for the recursive query, the client receives a response message sent by the recursive server; If the recursive server queries a complete result, the response message includes the complete result and the corresponding updated result integrity identifier; If the recursive server only obtains an intermediate result through query, the response message includes the intermediate result and the corresponding updated result integrity identifier; The client parses the response message and determines whether the query request is completed normally based on the result integrity identifier.

8. The DNS query request method according to claim 7, characterized in that: include: If the integrity identifier of the result parsed by the client indicates that only an intermediate result is obtained by the query, the client switches to the end of the cname chain according to its own strategy, and then re-initiates a recursive query for the domain name at the end of the cname chain.

9. The DNS query request method according to claim 8, characterized in that: include: The re-initiating of the recursive query for the cname domain name is to initiate a query request to other recursive servers.

10. A recursive server, comprising a memory, a processor and a computer program stored in the memory, characterized in that: The recursive server executes the computer program to implement the steps of the method according to any one of claims 1 to 6.

11. A client comprising a memory, a processor and a computer program stored in the memory, characterized in that: The client executes the computer program to implement the steps of the method according to any one of claims 7 to 9.