CN116266832A - Domain name resolution method, device, storage medium and computer equipment - Google Patents
Domain name resolution method, device, storage medium and computer equipment Download PDFInfo
- Publication number
- CN116266832A CN116266832A CN202111549813.2A CN202111549813A CN116266832A CN 116266832 A CN116266832 A CN 116266832A CN 202111549813 A CN202111549813 A CN 202111549813A CN 116266832 A CN116266832 A CN 116266832A
- Authority
- CN
- China
- Prior art keywords
- domain name
- server
- resolution
- dns
- dns resolution
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention is applicable to the technical field of communication, and provides a domain name resolution method, a device, a storage medium and computer equipment, wherein 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 carrying out domain name resolution on the target DNS resolution server according to the domain name resolution request. Therefore, the invention can avoid centralized processing of DNS traffic by the analysis server, protect the privacy of clients and improve the reliability of DNS traffic processing.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a domain name resolution method, a domain name resolution device, a storage medium, and a computer device.
Background
The domain name system (Domain Name System, DNS) provides the basic functionality of mapping human-readable names to IP addresses (Internet Protocol Address, internet protocol addresses) and is the center for most internet service operations. DNS has been a history of nearly 40 years, and recent attention to user privacy has focused on the risk of privacy disclosure that exists in DNS queries and responses. For example, DNS queries may expose websites (and web pages) that users are visiting and the connected devices they own, even in the physical world how users interact with these devices. While DNS queries and responses are typically transmitted in the clear, any entity that is able to observe DNS can also observe a large amount of private information. Proposals have therefore emerged to encrypt DNS queries and responses, including the transmission of 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 scheme is to configure a single recursion 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 parser is called a trusted recursive parser (TRR). In the case of DoT, the client software may be an operating system (e.g., android operating system has a "private DNS" option, doT resolver routing all DNS traffic to ***) or a browser (e.g., firefox browser has an option to enable DoH, resulting in all DNS traffic being exchanged with cloudflash). These architectures result in all DNS traffic for a client being exchanged with a single entity even though the client changes network and physical locations, introducing new privacy and reliability issues.
In view of the foregoing, the prior art has obvious inconveniences and drawbacks in practical use, so that improvements are needed.
Disclosure of Invention
In view of the above drawbacks, an object of the present invention is to provide a domain name resolution method, a device, a storage medium, and a computer device, which can avoid centralized processing of DNS traffic by a resolution server, protect customer privacy, and improve reliability of DNS traffic processing.
In order to achieve the above object, the present invention provides a domain name resolution method, including:
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 carrying out domain name resolution on the target DNS resolution server according to the domain name resolution request.
According to the domain name resolution method, before randomly selecting one DNS resolution server from the DNS resolution server set as the target DNS resolution server, the method includes:
sending the domain name resolution request to a DNS proxy server;
and inquiring whether the DNS proxy server caches the website mapping relation between the corresponding domain name and the IP address in the domain name resolution request according to the domain name resolution request, and if so, carrying out domain name resolution according to the website mapping relation by the DNS proxy server.
According to the domain name resolution method, the method further comprises:
establishing a server mapping relation list;
acquiring a secondary domain name of a corresponding domain name in the domain name resolution request;
and establishing a server mapping relation between the secondary domain name and the target DNS resolution server, and storing the server mapping relation into the server mapping relation list.
According to the domain name resolution method, before randomly selecting one DNS resolution server from the DNS resolution server set as the target DNS resolution server, the method includes:
inquiring whether the server mapping relation list stores the server mapping relation of the corresponding secondary domain name in the domain name resolution request, if so, acquiring the target DNS resolution server according to the server mapping relation, and performing domain name resolution by the target DNS resolution server according to the domain name resolution request.
According to the domain name resolution method, the method further comprises:
and presetting a time period, and if the time period is reached, clearing the server mapping relation list and then reestablishing.
According to the domain name resolution method, the method further comprises:
calculating a first total number of all the server mapping relations in the server mapping relation list;
calculating a second total number of each target DNS resolution server in all the server mapping relations;
calculating the ratio of each second total to the first total;
and if at least one ratio is larger than a preset threshold, clearing the server mapping relation list and then reestablishing.
According to the domain name resolution method, the DNS resolution server set further includes an internet service provider and/or an autonomous system to which each DNS resolution server belongs, and the randomly selecting one DNS resolution server from the DNS resolution server set as the target DNS resolution server includes:
acquiring an Internet service provider and/or an autonomous system to which a corresponding domain name belongs in the domain name resolution request;
and randomly selecting the target DNS resolution server from all DNS resolution servers of which the internet service provider and/or the autonomous system belongs to are the same as the internet service provider and/or the autonomous system of which the domain name belongs to.
In order to achieve the above object, the present invention further provides a domain name resolution device, including:
the construction module is used for constructing a DNS resolution server group, wherein the DNS resolution server group comprises a plurality of DNS resolution servers;
the receiving module is used for receiving the domain name resolution request;
the selection module is used for randomly selecting one DNS resolution server from the DNS resolution server group to serve as a target DNS resolution server;
and the resolution module is used for carrying out domain name resolution on the target DNS resolution server according to the domain name resolution request.
In order to achieve the above object, the present invention also provides a storage medium storing a computer program for executing any one of the domain name resolution methods described above.
In order to achieve the above object, the present invention further provides a computer device, including a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, where the processor implements the domain name resolution method according to any one of the above when executing the computer program.
The method comprises the steps of constructing a DNS analysis server group, wherein the DNS analysis server group comprises a plurality of DNS analysis 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 carrying out domain name resolution on the target DNS resolution server according to the domain name resolution request, so that centralized processing of DNS traffic by the resolution server can be avoided, customer privacy can be protected, and reliability of DNS traffic processing can be improved.
Drawings
FIG. 1 is a flow chart of a domain name resolution method according to an embodiment of the invention;
FIG. 2 is a schematic diagram of a domain name resolution device according to an embodiment of the invention;
FIG. 3 is a second block diagram of a domain name resolution device according to an embodiment of the invention;
fig. 4 is a schematic structural diagram of a computer device provided by the present invention.
Detailed Description
The present invention will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present invention more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
It should be noted that references in the specification to "one embodiment," "an example embodiment," etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Furthermore, such phrases are not intended to refer to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
Furthermore, certain terms are used throughout the specification and the claims that follow to refer to particular components or parts, and it will be understood by those of ordinary skill in the art that manufacturers may refer to a component or part by different terms or terminology. The present specification and the following claims do not take the form of an element or component with the difference in name, but rather take the form of an element or component with the difference in function as a criterion for distinguishing. In the following description and in the claims, the terms "include" and "comprise" are used in an open-ended fashion, and thus should be interpreted to mean "include, but not limited to. The term "coupled," as used herein, includes any direct or indirect electrical connection. Indirect electrical connection means include connection via other devices.
Referring to fig. 1, fig. 1 shows a flowchart of a domain name resolution method according to a first embodiment of the present invention, the domain name resolution method including:
step S101, constructing a DNS analysis server group, wherein the DNS analysis server group comprises a plurality of DNS analysis servers;
step S102, receiving a domain name resolution request;
step S103, randomly selecting a DNS resolution server from the DNS resolution server group as a target DNS resolution server;
step S104, the target DNS resolution server carries out domain name resolution according to the domain name resolution request.
In this embodiment, DNS resolution servers run by various independent entities (e.g., ***, firefox, etc.) proliferate as DNS is encrypted by the operating system and browser. In order to avoid centralized processing of encrypted DNS traffic (typically processed by DNS servers with IP addresses 8.8.8.8 or 114.114.114.114 in the prior art), by constructing a DNS resolution server group to randomly distribute encrypted DNS queries over each DNS resolution server in the DNS resolution server group, centralization can be avoided, the confidentiality advantage of the encrypted DNS traffic is maintained, the privacy benefit of the encrypted DNS is realized for the client, and the pressure of the DNS resolution servers can be relieved. And the target DNS analysis server is randomly selected, so that the reliability of the DNS analysis server can be improved.
As an alternative embodiment, step S103 includes, before:
sending a domain name resolution request to a DNS proxy server;
inquiring whether the DNS proxy server caches the corresponding website mapping relation between the domain name and the IP address in the domain name resolution request according to the domain name resolution request, and if so, carrying out domain name resolution according to the website mapping relation by the DNS proxy server.
In this embodiment, a caching mechanism of the DNS proxy server is utilized, and when a domain name corresponding to a domain name resolution request sent by the client performs domain name resolution before, a domain name resolution result is cached by the DNS proxy server (that is, a website mapping relationship between a domain name corresponding to the domain name resolution request and an IP address is cached), so that the domain name resolution result can be quickly obtained when the domain name resolution of the corresponding domain name is performed again. Therefore, when a domain name resolution request sent by a client is received, local cache inquiry is firstly carried out through the DNS proxy server, and if the corresponding website mapping relation exists in the cache, domain name resolution is carried out by the DNS proxy server according to the website mapping relation, so that the domain name resolution speed can be increased. Otherwise, randomly selecting a DNS resolution server from the DNS resolution server group as a target DNS resolution server to perform domain name resolution.
As an alternative embodiment, the method further comprises:
establishing a server mapping relation list;
acquiring a secondary domain name of a corresponding domain name in a domain name resolution request;
and establishing a server mapping relation between the second-level domain name and the target DNS resolution server, and storing the server mapping relation into a server mapping relation list.
Specifically, before randomly selecting one DNS resolution server from the DNS resolution server set as the target DNS resolution server, the method includes:
inquiring whether a server mapping relation of a corresponding second-level domain name in the domain name resolution request is stored in a server mapping relation list, if so, acquiring a target DNS resolution server according to the server mapping relation, and carrying out domain name resolution by the target DNS resolution server according to the domain name resolution request.
In this embodiment, when a domain name resolution request of a corresponding domain name is issued for the first time, the target DNS resolution server is randomly selected to perform domain name resolution, and at this time, each domain name has been distributed to each DNS resolution server to perform domain name resolution. Because the DNS resolution server has a caching mechanism, when the corresponding domain name issues a domain name resolution request again, in order to speed up domain name resolution, the DNS resolution server that performs domain name resolution on the domain name last time may be used to perform domain name resolution again. Therefore, by establishing the server mapping relationship list, in order to make the sub domain names of the secondary domain names (Second Level Domain, SLD) perform domain name resolution again by using the DNS resolution server, a server mapping relationship between the secondary domain names and the target DNS resolution server is established, so that when the sub domain names (e.g., a.xxx.com, b.xxx.com, c.xxx.com) with the same secondary domain names send out a domain name resolution request, if the server mapping relationship of the corresponding secondary domain names in the domain name resolution request is stored in the query server mapping relationship list, the target DNS resolution server is obtained by using the server mapping relationship, and the domain name resolution speed is improved.
As an alternative embodiment, the method further comprises:
and presetting a time period, and if the time period is reached, emptying the server mapping relation list and then reestablishing.
In this embodiment, in order to improve the reliability of domain name resolution and avoid the influence of the increase or decrease of DNS resolution servers in the DNS resolution server group, after reaching a preset time period, the mapping relationship list of the servers is emptied and then re-established. Since the server mapping list is emptied, there is no server mapping, and thus the corresponding domain name randomly selects the target DNS resolution server again.
As an alternative embodiment, the method further comprises:
calculating a first total number of all server mapping relations in a server mapping relation list;
calculating the second total number of each target DNS resolution server in the mapping relation of all the servers;
calculating the ratio of each second total to the first total;
if at least one ratio is larger than a preset threshold, the mapping relation list of the server is emptied and then reestablished.
In this embodiment, to avoid overload of at least one DNS resolution server, the list of server mappings may be emptied and then re-established. Assuming that 100 server mappings (i.e., the first total number is 100) are stored in the server mapping list, there are 40 target DNS resolution servers a (i.e., the second total number of target DNS resolution servers a is 40) in the server mapping list, 20 target DNS resolution servers B (i.e., the second total number of target DNS resolution servers B is 20) in the server mapping list, 20 target DNS resolution servers C (i.e., the second total number of target DNS resolution servers C is 20) in the server mapping list, 20 target DNS resolution servers D (i.e., the second total number of target DNS resolution servers D is 20) in the server mapping list, and the preset threshold is 0.25, since the ratio of the second total number 40 of target DNS resolution servers a to the first total number 100 is 0.4, which is greater than the preset threshold of 0.25, it is necessary to reestablish the server mapping list.
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:
acquiring an Internet service provider and/or an autonomous system to which a corresponding domain name belongs in a domain name resolution request;
the target DNS resolution server is randomly selected from all DNS resolution servers of which the affiliated Internet service provider and/or affiliated autonomous system are the same as the affiliated Internet service provider and/or affiliated autonomous system of the domain name.
In this embodiment, when the internet service provider to which the domain name belongs and/or the autonomous system to which the DNS resolution server belongs are the same as the internet service provider to which the DNS resolution server belongs and/or the autonomous system to which the domain name belongs, domain name resolution can be completed more quickly.
Referring to fig. 2 to 3, fig. 2 to 3 show schematic block diagrams of a domain name resolution device 100 according to a second embodiment of the present invention, where the device 100 includes:
a construction module 10, configured to construct a DNS resolution server group, where the DNS resolution server group includes a plurality of DNS resolution servers;
a receiving module 20, configured to receive a domain name resolution request;
a selecting module 30, configured to randomly select one DNS resolution server from the DNS resolution server set as a target DNS resolution server;
and the resolution module 40 is configured to resolve the domain name by the target DNS resolution server according to the domain name resolution request.
As an alternative embodiment, the apparatus 100 further includes a first query module 50 configured to, before randomly selecting one DNS resolution server from the DNS resolution server set as the target DNS resolution server:
sending a domain name resolution request to a DNS proxy server;
inquiring whether the DNS proxy server caches the corresponding website mapping relation between the domain name and the IP address in the domain name resolution request according to the domain name resolution request, and if so, carrying out domain name resolution according to the website mapping relation by the DNS proxy server.
As an alternative embodiment, the apparatus 100 further comprises a list creation module 60 for:
establishing a server mapping relation list;
acquiring a secondary domain name of a corresponding domain name in a domain name resolution request;
and establishing a server mapping relation between the second-level domain name and the target DNS resolution server, and storing the server mapping relation into a server mapping relation list.
As an alternative embodiment, the apparatus 100 further includes a second query module 70 configured to randomly select one DNS resolution server from the DNS resolution server set as the target DNS resolution server before:
inquiring whether a server mapping relation of a corresponding second-level domain name in the domain name resolution request is stored in a server mapping relation list, if so, acquiring a target DNS resolution server according to the server mapping relation, and carrying out domain name resolution by the target DNS resolution server according to the domain name resolution request.
As an alternative embodiment, the apparatus 100 further comprises a first list reconstruction module 80 for:
and presetting a time period, and when the time period is reached, emptying the server mapping relation list and then reestablishing.
As an alternative embodiment, the apparatus 100 further comprises a second list reconstruction module 90 for:
calculating a first total number of server mapping relations in a server mapping relation list;
calculating the second total number of each target DNS resolution server in the mapping relation of all the servers;
calculating the ratio of each second total to the first total;
if at least one ratio is larger than a preset threshold, the mapping relation list of the server is emptied and then reestablished.
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 selecting module 30 is specifically configured to:
acquiring an Internet service provider and/or an autonomous system to which a corresponding domain name belongs in a domain name resolution request;
the target DNS resolution server is randomly selected from all DNS resolution servers of which the affiliated Internet service provider and/or affiliated autonomous system are the same as the affiliated Internet service provider and/or affiliated autonomous system of the domain name.
It should be noted that, the specific implementation and the technical effects of the domain name resolution device 100 provided in the embodiment of the present invention are the same as those of the foregoing method embodiment, and for the sake of brevity, reference may be made to the corresponding content in the foregoing method embodiment for the part of the embodiment of the device 100 that is not mentioned.
The present invention also provides a storage medium storing a computer program for executing any one of the domain name resolution methods described above. Such as computer program instructions, which, when executed by a computer, may invoke or provide methods and/or techniques in accordance with the present application. Program instructions for invoking the methods of the present application may be stored in fixed or removable storage media and/or transmitted via a data stream in a broadcast or other signal bearing medium and/or stored within a storage medium of a computer device operating according to the program instructions. Here, according to an embodiment of the present application, comprising a computer device 400 as shown in fig. 4, the computer device 400 preferably comprises a storage medium 200 for storing a computer program and a processor 300 for executing the computer program, wherein the computer program, when executed by the processor 300, triggers the computer device 400 to perform the method and/or the technical solution based on the previous embodiments.
It should be noted that the present application may be implemented in software and/or a combination of software and hardware, for example, using Application Specific Integrated Circuits (ASIC), a general purpose computer or any other similar hardware device. In one embodiment, the software program of the present application may be executed by a processor to implement the above steps or functions. Likewise, the software programs of the present application (including associated data structures) may be stored on a computer readable recording medium, such as RAM memory, magnetic or optical drive or diskette and the like. In addition, some steps or functions of the present application may be implemented in hardware, for example, as circuitry that cooperates with the processor to perform various steps or functions.
The method according to the invention may be implemented as a computer implemented method on a computer, or in dedicated hardware, or in a combination of both. Executable code or parts thereof for the method according to the invention may be stored on a computer program product. Examples of computer program products include memory devices, optical storage devices, integrated circuits, servers, online software, and the like. Preferably, the computer program product comprises non-transitory program code means stored on a computer readable medium for performing the method according to the invention when said program product is executed on a computer.
In a preferred embodiment the computer program comprises computer program code means adapted to perform all the steps of the method according to the invention when the computer program is run on a computer. Preferably, the computer program is embodied on a computer readable medium.
In summary, the present invention constructs a DNS resolution server group, where the DNS resolution server group includes 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 carrying out domain name resolution on the target DNS resolution server according to the domain name resolution request, so that centralized processing of DNS traffic by the resolution server can be avoided, customer privacy can be protected, and reliability of DNS traffic processing can be improved.
Of course, the present invention is capable of other various embodiments and its several details are capable of modification and variation in light of the present invention, as will be apparent to those skilled in the art, without departing from the spirit and scope of the invention as defined in the appended claims.
The invention also discloses: a1, a domain name resolution method is characterized by comprising 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 carrying out domain name resolution on the target DNS resolution server according to the domain name resolution request.
A2, the domain name resolution method according to A1 is characterized in that before randomly selecting one DNS resolution server from the DNS resolution server group as a target DNS resolution server, the method comprises the following steps:
sending the domain name resolution request to a DNS proxy server;
and inquiring whether the DNS proxy server caches the website mapping relation between the corresponding domain name and the IP address in the domain name resolution request according to the domain name resolution request, and if so, carrying out domain name resolution according to the website mapping relation by the DNS proxy server.
A3, the domain name resolution method according to A1, further comprising:
establishing a server mapping relation list;
acquiring a secondary domain name of a corresponding domain name in the domain name resolution request;
and establishing a server mapping relation between the secondary domain name and the target DNS resolution server, and storing the server mapping relation into the server mapping relation list.
A4, the domain name resolution method according to A3 is characterized in that before randomly selecting one DNS resolution server from the DNS resolution server group as a target DNS resolution server, the method comprises the following steps:
inquiring whether the server mapping relation list stores the server mapping relation of the corresponding secondary domain name in the domain name resolution request, if so, acquiring the target DNS resolution server according to the server mapping relation, and performing domain name resolution by the target DNS resolution server according to the domain name resolution request.
A5, the domain name resolution method according to A3, further comprising:
and presetting a time period, and if the time period is reached, clearing the server mapping relation list and then reestablishing.
A6, the domain name resolution method according to A3 is characterized by further comprising:
calculating a first total number of all the server mapping relations in the server mapping relation list;
calculating a second total number of each target DNS resolution server in all the server mapping relations;
calculating the ratio of each second total to the first total;
and if at least one ratio is larger than a preset threshold, clearing the server mapping relation list and then reestablishing.
A7, the domain name resolution method according to A1 is characterized in that 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 randomly selecting one DNS resolution server from the DNS resolution server group as a target DNS resolution server comprises:
acquiring an Internet service provider and/or an autonomous system to which a corresponding domain name belongs in the domain name resolution request;
and randomly selecting the target DNS resolution server from all DNS resolution servers of which the internet service provider and/or the autonomous system belongs to are the same as the internet service provider and/or the autonomous system of which the domain name belongs to.
B8, a domain name resolution device, comprising:
the construction module is used for constructing a DNS resolution server group, wherein the DNS resolution server group comprises a plurality of DNS resolution servers;
the receiving module is used for receiving the domain name resolution request;
the selection module is used for randomly selecting one DNS resolution server from the DNS resolution server group to serve as a target DNS resolution server;
and the resolution module is used for carrying out domain name resolution on the target DNS resolution server according to the domain name resolution request.
B9, the domain name resolution device according to B8, wherein the device further includes a first query module, configured to, before randomly selecting one DNS resolution server from the DNS resolution server group as the target DNS resolution server:
sending the domain name resolution request to a DNS proxy server;
and inquiring whether the DNS proxy server caches the website mapping relation between the corresponding domain name and the IP address in the domain name resolution request according to the domain name resolution request, and if so, carrying out domain name resolution according to the website mapping relation by the DNS proxy server.
B10, the domain name resolution device according to B8, wherein the device further includes a list building module configured to:
establishing a server mapping relation list;
acquiring a secondary domain name of a corresponding domain name in the domain name resolution request;
and establishing a server mapping relation between the secondary domain name and the target DNS resolution server, and storing the server mapping relation into the server mapping relation list.
B11, the domain name resolution device according to B10, wherein the device further includes a second query module, configured to, before randomly selecting one DNS resolution server from the DNS resolution server set as the target DNS resolution server:
inquiring whether the server mapping relation list stores the server mapping relation of the corresponding secondary domain name in the domain name resolution request, if so, acquiring the target DNS resolution server according to the server mapping relation, and performing domain name resolution by the target DNS resolution server according to the domain name resolution request.
B12, the domain name resolution device according to B10, wherein the device further includes a first list reconstruction module configured to:
and presetting a time period, and emptying the server mapping relation list and reestablishing the server mapping relation list when the time period is reached.
B13, the domain name resolution device according to B10, wherein the device further includes a second list reconstruction module configured to:
calculating a first total number of the server mapping relations in the server mapping relation list;
calculating a second total number of each target DNS resolution server in all the server mapping relations;
calculating the ratio of each second total to the first total;
and if at least one ratio is larger than a preset threshold, clearing the server mapping relation list and then reestablishing.
B14, the domain name resolution device according to B8, wherein 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 is specifically configured to:
acquiring an Internet service provider and/or an autonomous system to which a corresponding domain name belongs in the domain name resolution request;
and randomly selecting the target DNS resolution server from all DNS resolution servers of which the internet service provider and/or the autonomous system belongs to are the same as the internet service provider and/or the autonomous system of which the domain name belongs to.
C15, a storage medium, storing a computer program for executing any one of the domain name resolution methods A1 to A7.
D16. a computer device comprising a storage medium, a processor and a computer program stored on the storage medium and executable on the processor, wherein the processor implements the domain name resolution method according to any one of A1 to A7 when executing the computer program.
Claims (10)
1. A method for domain name resolution, comprising:
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 carrying out domain name resolution on the target DNS resolution server according to the domain name resolution request.
2. The domain name resolution method according to claim 1, wherein before randomly selecting one DNS resolution server from the DNS resolution server set as the target DNS resolution server, the method comprises:
sending the domain name resolution request to a DNS proxy server;
and inquiring whether the DNS proxy server caches the website mapping relation between the corresponding domain name and the IP address in the domain name resolution request according to the domain name resolution request, and if so, carrying out domain name resolution according to the website mapping relation by the DNS proxy server.
3. The domain name resolution method according to claim 1, further comprising:
establishing a server mapping relation list;
acquiring a secondary domain name of a corresponding domain name in the domain name resolution request;
and establishing a server mapping relation between the secondary domain name and the target DNS resolution server, and storing the server mapping relation into the server mapping relation list.
4. A domain name resolution method according to claim 3, wherein before randomly selecting one DNS resolution server from the DNS resolution server set as the target DNS resolution server comprises:
inquiring whether the server mapping relation list stores the server mapping relation of the corresponding secondary domain name in the domain name resolution request, if so, acquiring the target DNS resolution server according to the server mapping relation, and performing domain name resolution by the target DNS resolution server according to the domain name resolution request.
5. A domain name resolution method as claimed in claim 3, further comprising:
and presetting a time period, and if the time period is reached, clearing the server mapping relation list and then reestablishing.
6. A domain name resolution method as claimed in claim 3, further comprising:
calculating a first total number of all the server mapping relations in the server mapping relation list;
calculating a second total number of each target DNS resolution server in all the server mapping relations;
calculating the ratio of each second total to the first total;
and if at least one ratio is larger than a preset threshold, clearing the server mapping relation list and then reestablishing.
7. The domain name resolution method according to claim 1, wherein 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 randomly selecting one DNS resolution server from the DNS resolution server group as the target DNS resolution server includes:
acquiring an Internet service provider and/or an autonomous system to which a corresponding domain name belongs in the domain name resolution request;
and randomly selecting the target DNS resolution server from all DNS resolution servers of which the internet service provider and/or the autonomous system belongs to are the same as the internet service provider and/or the autonomous system of which the domain name belongs to.
8. A domain name resolution device, comprising:
the construction module is used for constructing a DNS resolution server group, wherein the DNS resolution server group comprises a plurality of DNS resolution servers;
the receiving module is used for receiving the domain name resolution request;
the selection module is used for randomly selecting one DNS resolution server from the DNS resolution server group to serve as a target DNS resolution server;
and the resolution module is used for carrying out domain name resolution on the target DNS resolution server according to the domain name resolution request.
9. A storage medium storing a computer program for performing the domain name resolution method of any one of claims 1 to 7.
10. 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 implements the domain name resolution method according to any one of claims 1-7 when executing the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111549813.2A CN116266832A (en) | 2021-12-17 | 2021-12-17 | Domain name resolution method, device, storage medium and computer equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111549813.2A CN116266832A (en) | 2021-12-17 | 2021-12-17 | Domain name resolution method, device, storage medium and computer equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116266832A true CN116266832A (en) | 2023-06-20 |
Family
ID=86743546
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111549813.2A Pending CN116266832A (en) | 2021-12-17 | 2021-12-17 | Domain name resolution method, device, storage medium and computer equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116266832A (en) |
-
2021
- 2021-12-17 CN CN202111549813.2A patent/CN116266832A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9590946B2 (en) | Managing content delivery network service providers | |
| US10284516B2 (en) | System and method of determining geographic locations using DNS services | |
| US9800539B2 (en) | Request routing management based on network components | |
| US8156243B2 (en) | Request routing | |
| US9160703B2 (en) | Request routing management based on network components | |
| US9608957B2 (en) | Request routing using network computing components | |
| US9712422B2 (en) | Selection of service nodes for provision of services | |
| US11153264B2 (en) | Methods, apparatuses, and computer programs for data processing, and hierarchical domain name system zone files | |
| KR20190053170A (en) | System and method for suppressing DNS requests | |
| CN116566945A (en) | Access method and device for decentralised application, electronic equipment and storage medium | |
| CN116266832A (en) | Domain name resolution method, device, storage medium and computer equipment | |
| CN114866508B (en) | Domain name resolution method, and domain name-based data processing method and device | |
| GB2553243A (en) | Methods, apparatuses, and computer programs for data processing, and hierarchical domain name system zone files |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication |