Domain name resolution method and device, storage medium and computer device

Abstract

The application is suitable for the technical field of communication, and provides a domain name resolution method and device, a storage medium and a computer device. The method comprises the following steps: constructing a DNS resolution server group, wherein the DNS resolution server group comprises a plurality of DNS resolution servers; receiving a domain name resolution request; randomly selecting a DNS resolution server from the DNS resolution server group as a target DNS resolution server; and performing domain name resolution on the target DNS resolution server according to the domain name resolution request. Therefore, the application can avoid centralized processing of DNS traffic by the resolution server, can protect customer privacy, and can improve the reliability of DNS traffic processing.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, and in particular to a domain name resolution method and device, a storage medium and a computer device. BACKGROUND

[0002] The Domain Name System (DNS) provides the basic function of mapping human-readable names to IP addresses (Internet Protocol Addresses) and is the center of operation for most Internet services. DNS has been around for nearly 40 years, and recent concerns about user privacy have focused attention on the privacy leakage risk that exists in DNS queries and responses. For example, DNS queries can expose the websites (and web pages) that users are visiting and the connected devices they own, and even how users interact with these devices in the physical world. When DNS queries and responses are typically transmitted in plaintext, any entity that can observe DNS can also observe a large amount of private information. Therefore, there are proposals to encrypt DNS queries and responses, including transmitting DNS queries and responses over Transport Layer Security (DNS-over-TLS, or DoT) and Secure HTTP (DNS-over-HTTPS, or DoH). The deployment method in the prior art is to configure a single recursive resolver on the client device, which is responsible for terminating the encrypted communication channel and resolving all DNS queries of the client. In the Firefox browser of Mozilla, this resolver is called the Trusted Recursive Resolver (TRR). In the case of DoT, the client software can be the operating system (for example, the Android operating system has a "Private DNS" option that routes all DNS traffic to Google's DoT resolver) or the browser (for example, the Firefox browser has an option to enable DoH, which causes all DNS traffic to be exchanged with Cloudflare). These architectures cause all DNS traffic of a customer to be exchanged with a single entity, even if the customer changes networks and physical locations, thereby introducing new privacy and reliability issues.

[0003] In summary, the prior art is obviously inconvenient and defective in actual use, and therefore needs to be improved. SUMMARY

[0004] In view of the above defects, the present application aims to provide a domain name resolution method, device, storage medium and computer device, which can avoid centralized processing of DNS traffic by the resolution server, protect customer privacy and improve the reliability of DNS traffic processing.

[0005] In order to achieve the above-mentioned purpose, the present application provides a domain name resolution method, comprising:

[0006] Construct a DNS resolution server group, which includes a plurality of DNS resolution servers;

[0007] Receive a domain name resolution request;

[0008] Randomly select one DNS resolution server from the DNS resolution server group as a target DNS resolution server;

[0009] The target DNS resolution server resolves the domain name according to the domain name resolution request.

[0010] According to the domain name resolution method, the method further comprises:

[0011] Send the domain name resolution request to a DNS proxy server;

[0012] The DNS proxy server queries whether the corresponding domain name and IP address in the domain name resolution request are cached in the DNS proxy server, and if so, the DNS proxy server resolves the domain name according to the cached domain name and IP address.

[0013] According to the domain name resolution method, the method further comprises:

[0014] Establish a server mapping relationship list;

[0015] Obtain the second-level domain name corresponding to the domain name in the domain name resolution request;

[0016] Establish a server mapping relationship between the second-level domain name and the target DNS resolution server, and save the server mapping relationship in the server mapping relationship list.

[0017] According to the domain name resolution method, the method further comprises:

[0018] Query whether the server mapping relationship of the second-level domain name corresponding to the domain name resolution request is saved in the server mapping relationship list, and if so, obtain the target DNS resolution server according to the server mapping relationship, and the target DNS resolution server resolves the domain name according to the domain name resolution request.

[0019] According to the domain name resolution method, the method further comprises:

[0020] Pre-set a time period, and if the time period is reached, empty the server mapping relationship list and re-establish it.

[0021] According to the domain name resolution method, the method further comprises:

[0022] calculating a first total number of all the server mapping relationships in the server mapping relationship list;

[0023] calculating a second total number of each target DNS resolution server in all the server mapping relationships;

[0024] calculating a ratio of each second total number to the first total number;

[0025] if at least one of the ratios is greater than a preset threshold, then emptying the server mapping relationship list and re-establishing.

[0026] According to the domain name resolution method, the DNS resolution server group further comprises an Internet service provider and / or an autonomous system to which each DNS resolution server belongs, and the random selection of a DNS resolution server from the DNS resolution server group as a target DNS resolution server comprises:

[0027] obtaining an Internet service provider and / or an autonomous system to which a corresponding domain name in the domain name resolution request belongs;

[0028] randomly selecting the target DNS resolution server from each DNS resolution server whose Internet service provider and / or autonomous system is the same as that of the domain name.

[0029] To achieve the above-mentioned purposes, the application further provides a domain name resolution device, comprising:

[0030] a construction module for constructing a DNS resolution server group, wherein the DNS resolution server group comprises a plurality of DNS resolution servers;

[0031] a receiving module for receiving a domain name resolution request;

[0032] a selection module for randomly selecting a DNS resolution server from the DNS resolution server group as a target DNS resolution server;

[0033] a resolution module for performing domain name resolution on the target DNS resolution server according to the domain name resolution request.

[0034] To achieve the above-mentioned purposes, the application further provides a storage medium for storing a computer program for executing any of the above-mentioned domain name resolution methods.

[0035] In order to achieve the above object, the application further provides a computer device, comprising a storage medium, a processor and a computer program stored in the storage medium and executable on the processor, wherein the processor implements the domain name resolution method according to any one of the above embodiments when executing the computer program.

[0036] The application can avoid centralized processing of DNS traffic by the resolution server, protect customer privacy and improve the reliability of DNS traffic processing by constructing a DNS resolution server group comprising a plurality of DNS resolution servers, receiving a domain name resolution request, randomly selecting a DNS resolution server from the DNS resolution server group as a target DNS resolution server and performing domain name resolution on the target DNS resolution server according to the domain name resolution request. BRIEF DESCRIPTION OF DRAWINGS

[0037] Figure 1 is a flow chart of a domain name resolution method according to an embodiment of the application;

[0038] Figure 2 is a module schematic diagram of a domain name resolution device according to an embodiment of the application;

[0039] Figure 3 is a module schematic diagram of a domain name resolution device according to an embodiment of the application;

[0040] Figure 4 is a structural schematic diagram of a computer device according to the application. DETAILED DESCRIPTION

[0041] In order to make the object, technical scheme and advantages of the application clearer, the application is further described in detail below with reference to the drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the application and do not limit the application.

[0042] It should be noted that the use of "one embodiment", "an embodiment", "example embodiment" and the like in the specification indicates that the described embodiment can include a particular feature, structure or characteristic, but not every embodiment necessarily includes the particular feature, structure or characteristic. In addition, such expressions are not necessarily referring to the same embodiment. Further, when a particular feature, structure or characteristic is described in connection with an embodiment, it is within the knowledge of those skilled in the art to incorporate such feature, structure or characteristic into other embodiments whether or not it is explicitly described.

[0043] Furthermore, certain terms are used in the specification and subsequent claims to refer to specific components or parts. Those skilled in the art will understand that manufacturers may use different names or terms to refer to the same component or part. This specification and subsequent claims do not distinguish components or parts by differences in name, but rather by differences in function. The terms "comprising" and "including" used throughout the specification and subsequent claims are open-ended and should be interpreted as "including but not limited to." Additionally, the term "connection" here includes any direct and indirect electrical connection means. Indirect electrical connection means include connections made through other means.

[0044] See Figure 1 , Figure 1 A flowchart of a domain name resolution method according to a first embodiment of the present invention is shown. The domain name resolution method includes:

[0045] Step S101: Construct a DNS resolution server group, which includes multiple DNS resolution servers;

[0046] Step S102: Receive a domain name resolution request;

[0047] Step S103: Randomly select a DNS resolution server from the DNS resolution server group as the target DNS resolution server;

[0048] Step S104: The target DNS resolution server performs domain name resolution based on the domain name resolution request.

[0049] In this embodiment, as operating systems and browsers encrypt DNS, the number of DNS resolution servers run by various independent entities (such as Google, Firefox, etc.) surges. To avoid centralized processing of encrypted DNS traffic (which is typically handled by DNS servers with IP addresses of 8.8.8.8 or 114.114.114.114 in the prior art), encrypted DNS queries are randomly distributed across various DNS resolution servers within a DNS resolution server group. This avoids centralization, preserves the confidentiality advantage of encrypted DNS traffic, allows customers to realize the privacy benefits of encrypted DNS, and also alleviates the pressure on DNS resolution servers. Furthermore, the random selection of target DNS resolution servers improves the reliability of the DNS resolution servers.

[0050] As an optional embodiment, the steps preceding step S103 include:

[0051] Send the domain name resolution request to the DNS proxy server;

[0052] The DNS proxy server queries whether the domain name and IP address mapping relationship corresponding to the domain name in the domain name resolution request is cached according to the domain name resolution request, and if yes, the DNS proxy server performs domain name resolution according to the domain name and IP address mapping relationship.

[0053] In this embodiment, the cache mechanism of the DNS proxy server is utilized. When the domain name corresponding to the domain name resolution request sent by the client has been resolved before, the domain name resolution result will be cached by the DNS proxy server (i.e. the domain name and IP address mapping relationship corresponding to the domain name in the domain name resolution request is cached), so that when the domain name resolution of the corresponding domain name is performed again, the domain name resolution result can be quickly obtained. Thus, when the domain name resolution request sent by the client is received, local cache query is performed through the DNS proxy server. If the corresponding domain name and IP address mapping relationship is cached, the DNS proxy server performs domain name resolution according to the domain name and IP address mapping relationship, so that the domain name resolution speed can be accelerated. Otherwise, a DNS resolution server is randomly selected from the DNS resolution server group as a target DNS resolution server to perform domain name resolution.

[0054] As an optional embodiment, the method further comprises:

[0055] establishing a server mapping relationship list;

[0056] obtaining the second-level domain name of the domain name corresponding to the domain name resolution request;

[0057] establishing the server mapping relationship between the second-level domain name and the target DNS resolution server, and saving the server mapping relationship into the server mapping relationship list.

[0058] Specifically, before a DNS resolution server is randomly selected from the DNS resolution server group as a target DNS resolution server, the method further comprises:

[0059] querying whether the server mapping relationship of the second-level domain name corresponding to the domain name resolution request is saved in the server mapping relationship list, and if yes, obtaining the target DNS resolution server according to the server mapping relationship, and performing domain name resolution by the target DNS resolution server according to the domain name resolution request.

[0060] In this embodiment, when a domain name resolution request of a corresponding domain name is first sent, a target DNS resolution server is randomly selected to perform domain name resolution, and at this time, each domain name is distributed to each DNS resolution server to perform domain name resolution. Since the DNS resolution server has a cache mechanism, when a domain name resolution request of the corresponding domain name is sent again, in order to speed up the domain name resolution, the DNS resolution server used last time to perform domain name resolution of the domain name is used again to perform domain name resolution. Therefore, by establishing the server mapping relationship list, in order to enable the subdomain names of the second level domain (SLD) to also use the DNS resolution server to perform domain name resolution again, the server mapping relationship between the second level domain and the target DNS resolution server is established, and thus, when a domain name resolution request is sent by each subdomain name of the same second level domain (for example, a.xxx.com, b.xxx.com, and c.xxx.com), if the server mapping relationship of the corresponding second level domain in the domain name resolution request is saved in the server mapping relationship list, the target DNS resolution server is obtained by using the server mapping relationship to perform domain name resolution, and the domain name resolution speed is improved.

[0061] As an optional embodiment, the method further includes:

[0062] A preset time period is set, and if the time period is reached, the server mapping relationship list is emptied and then re-established.

[0063] In this embodiment, in order to improve the reliability of domain name resolution and avoid the influence of the increase or decrease of the DNS resolution servers in the DNS resolution server group, after a preset time period is reached, the server mapping relationship list is emptied and then re-established. Since the server mapping relationship list is emptied, there is no server mapping relationship, and thus, the target DNS resolution server is randomly selected again for the corresponding domain name.

[0064] As an optional embodiment, the method further includes:

[0065] A first total number of all server mapping relationships in the server mapping relationship list is calculated;

[0066] A second total number of each target DNS resolution server in all server mapping relationships is calculated;

[0067] The ratio of each second total number to the first total number is calculated respectively;

[0068] If at least one ratio is greater than a preset threshold, the server mapping relationship list is emptied and then re-established.

[0069] In this embodiment, in order to avoid overloading of at least one DNS resolution server, the server mapping relationship list can be emptied and then re-established. Assuming that there are 100 server mapping relationships in the server mapping relationship list (i.e., the first total number is 100), there are 40 server mapping relationships in the server mapping relationship of target DNS resolution server A (i.e., the second total number of target DNS resolution server A is 40), there are 20 server mapping relationships in the server mapping relationship of target DNS resolution server B (i.e., the second total number of target DNS resolution server B is 20), there are 20 server mapping relationships in the server mapping relationship of target DNS resolution server C (i.e., the second total number of target DNS resolution server C is 20), there are 20 server mapping relationships in the server mapping relationship of target DNS resolution server D (i.e., the second total number of target DNS resolution server D is 20), and the preset threshold is 0.25. Since the ratio of the second total number 40 of target DNS resolution server A to the first total number 100 is 0.4, which is greater than the preset threshold 0.25, it is necessary to re-establish the server mapping relationship.

[0070] As an optional embodiment, the DNS resolution server group further includes an Internet service provider and / or an autonomous system to which each DNS resolution server belongs, and step S103 includes:

[0071] obtaining an Internet service provider and / or an autonomous system to which the corresponding domain name in the domain name resolution request belongs;

[0072] randomly selecting a target DNS resolution server from each DNS resolution server whose Internet service provider and / or autonomous system is the same as the Internet service provider and / or autonomous system to which the domain name belongs.

[0073] In this embodiment, when the Internet service provider and / or autonomous system to which the domain name belongs is the same as the Internet service provider and / or autonomous system to which the DNS resolution server belongs, the domain name resolution can be completed more quickly.

[0074] Referring to Figures 2-3 , Figures 2-3 A module schematic diagram of a domain name resolution device 100 provided by a second embodiment of the application is shown, and the device 100 includes:

[0075] A construction module 10 is configured to construct a DNS resolution server group, and the DNS resolution server group includes a plurality of DNS resolution servers.

[0076] A receiving module 20 is configured to receive a domain name resolution request.

[0077] A selection module 30 is configured to randomly select one DNS resolution server from the DNS resolution server group as a target DNS resolution server.

[0078] The resolving module 40 is configured to resolve the domain name according to the domain name resolution request.

[0079] As an optional embodiment, the apparatus 100 further comprises a first querying module 50, configured to:

[0080] send the domain name resolution request to the DNS proxy server;

[0081] query whether the DNS proxy server caches the website mapping relationship between the corresponding domain name and IP address in the domain name resolution request, and if yes, the DNS proxy server resolves the domain name according to the website mapping relationship.

[0082] As an optional embodiment, the apparatus 100 further comprises a list establishing module 60, configured to:

[0083] establish the server mapping relationship list;

[0084] obtain the second-level domain name of the corresponding domain name in the domain name resolution request;

[0085] establish the server mapping relationship between the second-level domain name and the target DNS resolving server, and save the server mapping relationship into the server mapping relationship list.

[0086] As an optional embodiment, the apparatus 100 further comprises a second querying module 70, configured to:

[0087] query whether the server mapping relationship list saves the server mapping relationship of the corresponding second-level domain name in the domain name resolution request, and if yes, obtain the target DNS resolving server according to the server mapping relationship, and the target DNS resolving server resolves the domain name according to the domain name resolution request.

[0088] As an optional embodiment, the apparatus 100 further comprises a first list reconstructing module 80, configured to:

[0089] preset a time period, and when the time period is reached, empty the server mapping relationship list and then re-establish it.

[0090] As an optional embodiment, the apparatus 100 further comprises a second list reconstructing module 90, configured to:

[0091] calculate the first total number of the server mapping relationships in the server mapping relationship list;

[0092] Calculate a second total number of each target DNS resolution server in all server mapping relationships;

[0093] Calculate the ratio of each second total number and the first total number respectively;

[0094] If at least one ratio is greater than a preset threshold, then empty the server mapping relationship list and re-establish.

[0095] As an optional embodiment, the DNS resolution server group further includes an Internet service provider and / or an autonomous system to which each DNS resolution server belongs, and the selection module 30 is specifically used for:

[0096] Obtaining an Internet service provider and / or an autonomous system to which the corresponding domain name in the domain name resolution request belongs;

[0097] Randomly selecting a target DNS resolution server from each DNS resolution server whose Internet service provider and / or autonomous system is the same as the Internet service provider and / or autonomous system to which the domain name belongs.

[0098] It should be noted that the domain name resolution device 100 provided by the embodiment of the application has the same specific implementation and technical effects as the foregoing method embodiments, and for brief description, the part of the device 100 embodiment not mentioned can refer to the corresponding content in the foregoing method embodiments.

[0099] The application also provides a storage medium for storing a computer program for executing any one of the above domain name resolution methods. For example, computer program instructions, when executed by a computer, can call or provide methods and / or technical solutions according to the present application through the operation of the computer. The program instructions for calling the method of the present application can be stored in a fixed or removable storage medium, and / or transmitted and / or stored in the storage medium of the computer device running according to the program instructions through the data stream in the broadcast or other signal bearing media. Here, according to one embodiment of the present application, a computer device 400 as shown in Figure 4 The computer device 400 preferably includes a storage medium 200 for storing a computer program and a processor 300 for executing the computer program, wherein when the computer program is executed by the processor 300, the computer device 400 is triggered to execute the method and / or technical solutions based on the foregoing multiple embodiments.

[0100] It is noted that the present application can be implemented in software and / or in a combination of software and hardware, e.g., using application specific integrated circuits (ASICs), general purpose computers, or any other similar hardware devices. In one embodiment, software programs implementing the present application can be executed by a processor to perform the steps or functions described herein. Similarly, software programs (including related data structures) of the present application can be stored in computer-readable storage media, such as RAM memory, magnetic or optical drives or disks, and any other volatile or non-volatile storage devices. In addition, some of the steps or functions can be implemented using hardware, e.g., as circuitry that co-operates with the processor to perform the various steps or functions.

[0101] The method according to the present application can be implemented on a computer as a computer implemented method, or in dedicated hardware, or in a combination of both. Executable code for the method according to the present application, or parts thereof, can be stored on a computer program product. Examples of computer program products include memory devices, optical storage devices, integrated circuits, servers, online software etc. Preferably, the computer program product comprises non-transitory program code means stored on a computer readable medium for performing the method according to the present application when the program product is executed on a computer.

[0102] In a preferred embodiment, the computer program comprises computer program code means adapted to perform all the steps of the method according to the present application when the computer program is run on a computer. Preferably, the computer program is embodied on a computer readable medium.

[0103] In summary, the present application can avoid centralized processing of DNS traffic by constructing a DNS resolution server group including multiple DNS resolution servers, receiving a domain name resolution request, randomly selecting a DNS resolution server from the DNS resolution server group as a target DNS resolution server, and performing domain name resolution on the target DNS resolution server according to the domain name resolution request, can protect customer privacy and improve the reliability of DNS traffic processing.

[0104] Of course, the present application can have other various embodiments, and those skilled in the art can make various corresponding changes and modifications according to the present application without departing from the spirit and essence of the present application, but these corresponding changes and modifications should all belong to the protection scope of the claims attached to the present application.

Claims

1. A domain name resolution method, characterized by, The application comprises the following steps: constructing a DNS resolution server group, which comprises a plurality of DNS resolution servers; receiving a domain name resolution request; randomly selecting a DNS resolution server from the DNS resolution server group as a target DNS resolution server; making the target DNS resolution server perform domain name resolution according to the domain name resolution request; The application further comprises the following steps: establishing a server mapping relationship list; obtaining a second-level domain name of a corresponding domain name in the domain name resolution request; establishing a server mapping relationship between the second-level domain name and the target DNS resolution server, and saving the server mapping relationship in the server mapping relationship list; The application further comprises the following steps before the step of randomly selecting a DNS resolution server from the DNS resolution server group as a target DNS resolution server: querying whether the server mapping relationship of the second-level domain name corresponding to the domain name resolution request is saved in the server mapping relationship list, and if yes, obtaining the target DNS resolution server according to the server mapping relationship, and making the target DNS resolution server perform domain name resolution according to the domain name resolution request.

2. The domain name resolution method of claim 1, wherein, The application further comprises the following steps before the step of randomly selecting a DNS resolution server from the DNS resolution server group as a target DNS resolution server: sending the domain name resolution request to a DNS proxy server; querying whether a website mapping relationship between the domain name and an IP address corresponding to the domain name resolution request is cached by the DNS proxy server according to the domain name resolution request, and if yes, performing domain name resolution by the DNS proxy server according to the website mapping relationship.

3. The domain name resolution method of claim 1, wherein, The application further comprises the following steps: presetting a time period, and if the time period is reached, emptying the server mapping relationship list and re-establishing it.

4. The domain name resolution method of claim 1, wherein, The application further comprises the following steps: calculating a first total number of all server mapping relationships in the server mapping relationship list; calculating a second total number of each target DNS resolution server in all server mapping relationships; calculating the ratio of each second total number to the first total number respectively; if at least one ratio is greater than a preset threshold value, emptying the server mapping relationship list and re-establishing it.

5. The domain name resolution method of claim 1, wherein, The DNS resolution server group further comprises an Internet service provider and / or an autonomous system to which each DNS resolution server belongs, and the step of randomly selecting a DNS resolution server from the DNS resolution server group as a target DNS resolution server comprises the following steps: obtaining an Internet service provider and / or an autonomous system to which a corresponding domain name in the domain name resolution request belongs; determining each DNS resolution server whose Internet service provider and / or autonomous system is the same as the Internet service provider and / or autonomous system to which the corresponding domain name in the domain name resolution request belongs, and randomly selecting the target DNS resolution server from the determined DNS resolution servers.

6. A domain name resolution apparatus characterized by comprising: The application comprises the following steps: a constructing module, which is configured to construct a DNS resolution server group, which comprises a plurality of DNS resolution servers; a receiving module, which is configured to receive a domain name resolution request; The selecting module is configured to randomly select one DNS resolution server from the group of DNS resolution servers as a target DNS resolution server; The resolving module is configured to enable the target DNS resolution server to perform domain name resolution according to the domain name resolution request. The device further comprises a list establishing module configured to: establish a server mapping relationship list; obtain the second-level domain name of the corresponding domain name in the domain name resolution request; establish a server mapping relationship between the second-level domain name and the target DNS resolution server, and save the server mapping relationship in the server mapping relationship list; The device further comprises a second query module configured to, before the step of randomly selecting one DNS resolution server from the group of DNS resolution servers as a target DNS resolution server: query whether the server mapping relationship of the second-level domain name corresponding to the domain name resolution request is saved in the server mapping relationship list, and if so, obtain the target DNS resolution server according to the server mapping relationship, and enable the target DNS resolution server to perform domain name resolution according to the domain name resolution request.

7. The domain name resolution apparatus according to claim 6, wherein The device further comprises a first query module configured to, before the step of randomly selecting one DNS resolution server from the group of DNS resolution servers as a target DNS resolution server: send the domain name resolution request to a DNS proxy server; query whether the DNS proxy server caches the website mapping relationship between the corresponding domain name and IP address in the domain name resolution request according to the domain name resolution request, and if so, enable the DNS proxy server to perform domain name resolution according to the website mapping relationship.

8. The domain name resolution apparatus according to claim 6, characterized by The device further comprises a first list re-establishing module configured to: pre-set a time period, and when the time period is reached, empty the server mapping relationship list and re-establish it.

9. The domain name resolution apparatus according to claim 6, characterized by The device further comprises a second list re-establishing module configured to: calculate a first total number of the server mapping relationships in the server mapping relationship list; calculate a second total number of each target DNS resolution server in all the server mapping relationships; calculate the ratio of each second total number to the first total number, respectively; if at least one of the ratios is greater than a preset threshold, empty the server mapping relationship list and re-establish it.

10. The domain name resolution apparatus according to claim 6, wherein The group of DNS resolution servers further comprises an Internet service provider and / or an autonomous system to which each DNS resolution server belongs, and the selecting module is specifically configured to: obtain the Internet service provider and / or the autonomous system to which the corresponding domain name in the domain name resolution request belongs; determine each DNS resolution server whose Internet service provider and / or autonomous system is the same as the Internet service provider and / or autonomous system to which the corresponding domain name in the domain name resolution request belongs, and randomly select the target DNS resolution server from the determined DNS resolution servers.

11. A storage medium, characterized by A computer program for executing the domain name resolution method of any one of claims 1-5.

12. A computer device comprising a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, characterized in that, The processor executes the computer program to implement the domain name resolution method of any one of claims 1-5.

Images