CN109842566B - DNS (Domain name Server) analysis method and device - Google Patents
DNS (Domain name Server) analysis method and device Download PDFInfo
- Publication number
- CN109842566B CN109842566B CN201910022098.3A CN201910022098A CN109842566B CN 109842566 B CN109842566 B CN 109842566B CN 201910022098 A CN201910022098 A CN 201910022098A CN 109842566 B CN109842566 B CN 109842566B
- Authority
- CN
- China
- Prior art keywords
- dns
- resolution
- link
- record
- condition
- 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.)
- Active
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
A DNS analysis method and device are disclosed. A DNS resolution method is applied to load balancing equipment, and the method comprises the following steps: receiving a DNS request message, and acquiring a target domain name requested to be analyzed by the message; determining whether the number of times of resolution requests corresponding to the target domain name in a prestored DNS resolution table entry reaches a preset resolution frequency threshold; if yes, returning a DNS response message to the client side sending the DNS request message according to a domain name resolution result recorded in the DNS resolution table entry; if not, acquiring the bandwidth utilization rate of each alternative link, and determining the priority sequence of each alternative link; determining a target link for the DNS analysis according to the priority sequence; sending the received DNS request message to a DNS server through the target link; and sending a DNS response message returned by the DNS server to the client side sending the DNS request message through the target link, and updating the DNS analysis table entry.
Description
Technical Field
The embodiment of the specification relates to the technical field of network communication, in particular to a DNS (domain name system) resolution method and device.
Background
When the user equipment accesses the network through links of different operators, domain name resolution needs to be performed by a DNS server of the corresponding operator, for example, a telecommunication user needs to send a domain name resolution request message to the telecommunication DNS server through a telecommunication link, and accesses the network according to a returned response message.
Because the operators in south and north China are distributed unevenly, in order to avoid congestion of cross-operator access, in the prior art, load balancing equipment generally receives DNS request messages of each user equipment, distributes the DNS request messages to DNS servers of different links for analysis, and forwards response messages responded by the received DNS servers to the user equipment.
However, when the DNS request messages received by the load balancing device exceed the number that can be processed by each server, the server response messages will be delayed, and even normal responses may not be made, which affects the user experience of surfing the internet.
Disclosure of Invention
In view of this, embodiments of the present specification provide a DNS resolution method and apparatus, which are applied to a load balancing device, and the technical solution is as follows:
a DNS resolution method is applied to load balancing equipment, and the method comprises the following steps:
receiving a DNS request message, and acquiring a target domain name requested to be analyzed by the message;
determining whether the number of resolution requests corresponding to the target domain name in a prestored DNS resolution table entry reaches a preset resolution frequency threshold value;
if the DNS request message reaches the threshold value, returning a DNS response message to the client side which sends the DNS request message according to a domain name resolution result recorded in the DNS resolution table entry;
if the bandwidth utilization rate does not reach the threshold value, the bandwidth utilization rate of each alternative link is obtained, and the priority ranking of each alternative link is determined according to the bandwidth utilization rate; determining a target link for the DNS analysis according to the priority sequence; the link with low bandwidth utilization rate has high priority;
sending the received DNS request message to a DNS server through the target link, and receiving a DNS response message returned by the DNS server;
and sending a DNS response message returned by the DNS server to the client side sending the DNS request message through the target link, and updating the DNS analysis table entry according to the DNS request message and the DNS response message so as to perform DNS analysis according to the updated DNS analysis table entry.
A DNS resolution device is applied to load balancing equipment, and the DNS resolution device comprises:
the message receiving module is used for receiving a DNS request message and acquiring a target domain name requested to be analyzed by the message;
the table item query module is used for determining whether the number of times of resolution requests corresponding to the target domain name in the prestored DNS resolution table items reaches a preset resolution frequency threshold value;
the link selection module is used for obtaining the bandwidth utilization rate of each alternative link under the condition that the bandwidth utilization rate does not reach a threshold value, and determining the priority sequence of each alternative link according to the bandwidth utilization rate; determining a target link for the DNS analysis according to the priority sequence; the link with low bandwidth utilization rate has high priority;
the response obtaining module is used for returning a DNS response message to the client side which sends the DNS request message according to the domain name resolution result recorded in the DNS resolution table entry under the condition that the threshold value is reached; and under the condition that the threshold value is not reached, sending the received DNS request message to a DNS server through the target link, and receiving a DNS response message returned by the DNS server;
and the table item updating module is used for sending a DNS response message returned by the DNS server to the client side sending the DNS request message through the target link, and updating the DNS analysis table item according to the DNS request message and the DNS response message so as to carry out DNS analysis according to the updated DNS analysis table item.
According to the technical scheme provided by the embodiment of the specification, firstly, the load balancing device can select the optimal link to process the DNS request message according to the bandwidth utilization rate of each link, secondly, the load balancing device can record and update the resolution result of each link for the same domain name, and directly returns the DNS response message through the recorded resolution result under the condition that the resolution result of the corresponding domain name reaches the preset resolution frequency threshold, without further repeatedly obtaining the resolution result from the DNS server, so that the pressure of the load balancing device, the link and the DNS server is reduced.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of embodiments of the invention.
In addition, any one of the embodiments in the present specification is not required to achieve all of the effects described above.
Drawings
In order to more clearly illustrate the embodiments of the present specification or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the embodiments of the present specification, and other drawings can be obtained by those skilled in the art according to the drawings.
Fig. 1 is a schematic flow chart of a DNS resolution method according to an embodiment of the present disclosure;
fig. 2 is a schematic structural diagram of a DNS resolution apparatus according to an embodiment of the present disclosure;
FIG. 3 is a block diagram of a table entry update module according to an embodiment of the present disclosure;
fig. 4 is another schematic structural diagram of a DNS resolution apparatus according to an embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of a condition monitoring submodule in an embodiment of the present disclosure.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in the embodiments of the present specification, the technical solutions in the embodiments of the present specification will be described in detail below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of the present specification, and not all the embodiments. All other embodiments that can be derived by one of ordinary skill in the art from the embodiments given herein are intended to be within the scope of protection.
To solve the problems in the prior art, the present specification provides a DNS resolution method applied to a load balancing device, and referring to fig. 1, the method may include the following steps:
s101, receiving a DNS request message, and acquiring a target domain name requested to be analyzed by the message;
s102, determining whether the number of times of resolution requests corresponding to the target domain name in a prestored DNS resolution table entry reaches a preset resolution frequency threshold value;
in this description, the load balancing device may pre-store a DNS resolution table entry, where the table entry records, through each record, a plurality of pieces of information corresponding to a plurality of DNS request messages received by the load balancing device, and the description does not limit the specific parameter types and the number of parameters recorded in the description, and a person skilled in the art may flexibly select the DNS resolution table entry according to actual needs.
In a specific implementation manner of the embodiment of this specification, the load balancing device prestores DNS resolution table entries, and the resolution parameters may include one or more of the following parameters: sending a source address of the DNS request message, a domain name requested to be analyzed by the DNS request message, recording aging time, a DNS server for performing DNS analysis, a target link for processing the DNS request message, DNS analysis request times and a DNS analysis result. The source address may be represented in various ways, for example, the source address may be a source IP address of a client that sends a DNS request message, or an MAC address of the client; for another example, different masks may be used for multidimensional representation, or may be directly represented as a mask of 0 to match all source addresses; and the like, which are not limited in this specification.
For example, the load balancing device may pre-store the DNS resolution table entry as shown in table 1 below, where each row in the table is a record:
| source address | Domain name | Aging time | DNS server | Target link | Number of analyses | Analysis result |
TABLE 1
Assuming that the load balancing device receives a certain DNS request packet, the source address is 10.18.68.69, and the domain name requested to be resolved is www.abc.com, after receiving the DNS request packet, the load balancing device may select a target link as link 1, thereby determining that the corresponding DNS server is server 1, the aging time may be in the form of current time, countdown for a preset duration, and the like, and may be recorded in the form of a TTL value, which is not limited in this description of embodiments.
The load balancing device may specifically determine whether the domain name resolution result corresponding to the determined target link reaches the preset resolution frequency threshold in a variety of ways, and a person skilled in the art may flexibly set the domain name resolution result according to actual needs, which is not limited in the embodiments of the present specification.
In another specific implementation manner of the embodiments of the present specification, as shown in table 1, the number of times of domain name resolution is recorded, and when the number of times of domain name resolution reaches a preset threshold (for example, 3 times), it is determined that a domain name resolution result corresponding to a target link reaches a preset resolution frequency threshold.
S103a, if the threshold is reached, returning a DNS response message to the client side sending the DNS request message according to a domain name resolution result recorded in a DNS resolution table entry;
if the domain name resolution result corresponding to the target link reaches the preset resolution frequency threshold, if the number of times recorded in the DNS resolution table entry reaches 3 times, the DNS response message may be returned to the client that sent the DNS request message directly through the resolution result recorded in the DNS resolution table entry without requesting domain name resolution from the DNS server.
S103b, if the bandwidth utilization rate of each alternative link is not reached, obtaining the bandwidth utilization rate of each alternative link, and determining the priority sequence of each alternative link according to the bandwidth utilization rate; determining a target link for the DNS analysis according to the priority sequence; the link with low bandwidth utilization rate has high priority;
because the south and north China operators are unevenly distributed, in order to avoid the congestion situation of cross-operator access, a service provider usually provides links of different operators, when the flow passes through the load balancing equipment, the load balancing equipment can distribute the links of the corresponding operators for users of different operators by selecting the links, for example, a telecommunication user accesses through the telecommunication link, a communication user accesses through the communication link, a mobile user accesses through the mobile link, and the like, so that the access speed of the user is improved.
In this embodiment, the load balancing device may be connected to multiple links (e.g., links of multiple operators), and after receiving the DNS request packet, select an optimal or better link to process the DNS request packet.
Therefore, after receiving the DNS request message, the load balancing device may first obtain the bandwidth utilization rate of each alternative link, and determine the priority ranking of each alternative link according to the bandwidth utilization rate. In the embodiment of the present specification, the load balancing device may specifically determine the priority ranking of each alternative link and select the target link according to the bandwidth utilization in multiple ways, and a person skilled in the art may flexibly set the priority ranking according to actual needs, which is not limited in the embodiment of the present specification.
In a specific implementation manner of the embodiments of the present specification, the load balancing device may determine the priority ranking of each alternative link by using a minimum bandwidth utilization algorithm, so as to select a target link with a higher priority, that is, with a lower bandwidth utilization.
Furthermore, although the load balancing device can alleviate the problem of cross-operator access, it may cause a waste of bandwidth resources. For example, assuming that the egress has a plurality of links belonging to different operators, one telecommunication link and one communication link are deployed at the network egress. The intranet user PC network configuration is all configured with telecommunication DNS addresses, the users all carry out domain name resolution to a telecommunication DNS server, the corresponding domain name resolution result is replied to be generally the telecommunication IP address, and the users access resources through IP subsequently and all use telecommunication link outlets, so that the situation that the telecommunication link is congested and bandwidth resources of the communication link are idle and wasted can occur.
Thus, this problem can be solved by a DNS transparent proxy. In a multilink scene, the DNS transparent proxy equipment is started, after receiving a DNS request message, the DNS transparent proxy equipment is distributed to DNS servers of different links for analysis, and a DNS response message responded by the DNS server is forwarded to a client side sending the request message.
Specifically, in another specific implementation manner of the embodiments of the present specification, there may also be one or more DNS transparent proxy servers in each link, and after selecting a target link, the load balancing device may further search for an available DNS transparent proxy server on the link, and if there are multiple DNS transparent proxy servers in the target link selected by the load balancing device, one of the DNS transparent proxy servers may be selected to process the received DNS request message. Similarly, the load balancing device may specifically select the DNS transparent proxy server in multiple ways, and those skilled in the art may flexibly set the DNS transparent proxy server according to actual needs, which is not limited in this description embodiment.
As an example, the load balancing device may use a round robin algorithm to select an available DNS transparent proxy server.
S104, sending the received DNS request message to a DNS server through the target link, and receiving a DNS response message returned by the DNS server;
and S105, sending a DNS response message returned by the DNS server to the client side sending the DNS request message through the target link, and updating the DNS analysis table entry according to the DNS request message and the DNS response message so as to perform DNS analysis according to the updated DNS analysis table entry.
The load balancing device may specifically update the DNS resolution entry according to the DNS request packet and the DNS response packet in various ways, and a person skilled in the art may flexibly set the DNS resolution entry according to actual needs, which is not limited in this description embodiment.
In a specific implementation manner of the embodiments of this specification, the load balancing device may first determine a number of resolution parameters recorded in the DNS resolution table entry, for example, a source address, a DNS server, a destination link, and the like, then obtain parameter values of the resolution parameters in the DNS request message and the DNS reply message, and update and/or increase the parameter values recorded in the DNS resolution table entry according to the obtained number of parameter values.
Assuming that the load balancing device receives a certain DNS request message, the source address is 10.18.68.69, the domain name requested to be resolved is www.abc.com, and after receiving the DNS request message, the load balancing device may select the target link as link 1, thereby determining that the corresponding DNS server is server 1, the aging time may be in the form of current time, countdown of preset time duration, and the like, and may be recorded in the form of a TTL value, which is not limited in this description embodiment.
Assuming that it is determined through searching that no record with the above-mentioned parameter value exists in the current DNS resolution table entry, that is, the number of times of resolution is 0, a response message may be requested to the server 1 through the link 1, and a resolution result is determined according to the response message, so as to be recorded in the DNS resolution table entry, where the recording result may be as shown in table 2:
| source address | Domain name | Aging time | DNS server | Target link | Number of analyses | Analysis result |
| 10.18.68.69 | www.abc.com | 1min | Server 1 | Link 1 | 1 | 1.1.1.1 |
TABLE 2
In order to avoid that the domain name resolution result recorded in the DNS resolution table entry is wrong, or the recorded data consumes resources of the DNS resolution device excessively redundantly, an aging condition may be preset, and whether each record of the DNS resolution table entry reaches the preset aging condition is monitored, and if so, the record is deleted from the DNS resolution table entry.
Various aging conditions can be set for each record of the DNS resolution table entry in advance, and the DNS resolution device can specifically monitor whether each record of the DNS resolution table entry reaches the preset aging conditions in various ways, and those skilled in the art can flexibly set the aging conditions according to actual needs, which is not limited in this specification.
In one specific implementation of the embodiments of the present description, the aging condition may be: the aging time exceeds a preset threshold (such as 1 minute), a wrong domain name resolution result is detected, a target link is detected to be disconnected, and the like.
Correspondingly, when monitoring whether the record reaches the preset aging condition, the DNS resolution device may first obtain the aging time in the record, and then judge whether the obtained aging time reaches the preset threshold; if so, determining that the record reaches a preset aging condition;
or, the address of the domain name resolution result and/or the DNS server address in the record may be obtained first, and the obtained address is used as the target address; and sending a detection message to the target address through a target link in the record, and determining whether the record reaches a preset aging condition according to the data condition of the target link and/or the response condition of the target address.
Determining whether the record reaches a preset aging condition according to the data condition of the target link and/or the response condition of the target address, specifically, counting the packet loss rate, the delay and/or the number of passes of the target link within a preset time period, and determining that the record reaches the preset aging condition when the counted value meets the preset condition; and/or determining whether a response message sent by the target address is received, wherein the response message is used for responding to the detection message; if not, determining that the record reaches the preset aging condition.
For example, the link packet loss rate (detection failure times/total detection times × 100%) may be calculated in real time according to the link health monitoring quality detection result, and if the packet loss rate exceeds the value, the link is considered to be faulty.
As another example, the average delay (sum of delay for successful probing/number of successful probing) of the link may be calculated in real time according to the link health monitoring quality detection result, and if the average delay exceeds the value, the link is considered to be faulty.
For another example, in the health monitoring configuration, whether each target probe passes or not can be determined in real time according to the retry number (if the latest continuous detection failure number is greater than the retry number, it is determined that the monitored target does not pass). And counting the total number of the passing targets checked in the link health monitoring group, and if the actual total number of the passing targets is less than at least the number of the passing targets, determining that the link is faulty, otherwise, determining that the link is normal.
When whether the record reaches the preset aging condition is determined according to the data condition of the target link and/or the response condition of the target address, if the preset aging condition is determined to be reached, the target link or the target address is considered to be abnormal, the record can be deleted from the DNS analysis table entry, and a DNS request message is not sent to the corresponding DNS server any more, so that the DNS analysis error caused by the abnormal link or server is avoided.
Corresponding to the foregoing method embodiment, an embodiment of the present specification further provides a DNS resolution device, which is applied to a load balancing device, and as shown in fig. 2, the DNS resolution device may include:
a message receiving module 110, configured to receive a DNS request message and obtain a target domain name to be analyzed by the message request;
the table entry query module 120 is configured to determine whether, in a prestored DNS resolution table entry, the resolution request frequency corresponding to the target domain name reaches a preset resolution frequency threshold;
a link selection module 130, configured to obtain a bandwidth utilization rate of each alternative link when a threshold is reached, and determine a priority ranking of each alternative link according to the bandwidth utilization rate; determining a target link for the DNS analysis according to the priority sequence; the link with low bandwidth utilization rate has high priority;
a response obtaining module 140, configured to, when a threshold is reached, return a DNS response packet to the client that sends the DNS request packet according to a domain name resolution result recorded in the DNS resolution entry; and under the condition that the threshold value is not reached, sending the received DNS request message to a DNS server through the target link, and receiving a DNS response message returned by the DNS server;
and the table entry updating module 150 is configured to send a DNS response message returned by the DNS server to the client sending the DNS request message through the target link, and update the DNS resolution table entry according to the DNS request message and the DNS response message, so as to perform DNS resolution according to the updated DNS resolution table entry in the subsequent process.
In a specific implementation manner of the embodiment of the present specification, referring to fig. 3, the entry updating module 150 may include:
a parameter determining submodule 151, configured to determine a plurality of resolution parameters recorded in the DNS resolution table entry;
a parameter value obtaining sub-module 152, configured to obtain parameter values of the resolution parameters in the DNS request message and the DNS reply message;
and the representation updating sub-module 153 is configured to update and/or add the parameter values recorded in the DNS resolution table entry according to the obtained parameter values.
In a specific implementation manner of the embodiments of the present specification, the resolution parameters may include one or more of the following parameters:
sending a source address of the DNS request message, a domain name requested to be analyzed by the DNS request message, recording aging time, a DNS server for performing DNS analysis, a target link for processing the DNS request message, DNS analysis request times and a DNS analysis result.
In a specific implementation manner of the embodiment of the present specification, referring to fig. 4, the apparatus may further include an entry monitoring module 160, which specifically includes:
a condition monitoring submodule 161, configured to, for any record of the DNS resolution table entry: monitoring whether the record reaches a preset aging condition;
the record deleting submodule 162 is configured to delete any record of the DNS resolution table entry when the record reaches a preset aging condition.
In a specific implementation manner of the embodiment of the present disclosure, referring to fig. 5, the condition monitoring sub-module 161 may include:
a time monitoring unit 161a, configured to obtain the aging time in the record, and determine whether the obtained aging time reaches a preset threshold; if so, determining that the record reaches a preset aging condition; and/or
A status monitoring unit 161b, configured to obtain an address of a domain name resolution result in the record and/or a DNS server address, and use the obtained address as a target address; and sending a detection message to the target address through a target link in the record, and determining whether the record reaches a preset aging condition according to the data condition of the target link and/or the response condition of the target address.
In a specific implementation manner of the embodiment of the present specification, the state monitoring unit may be specifically configured to:
counting the packet loss rate, the delay and/or the passing number of the target link in a preset time period, and determining that the record reaches a preset aging condition under the condition that the counted value meets a preset condition;
and/or
Determining whether a response message sent by the target address is received, wherein the response message is used for responding to the detection message; if not, determining that the record reaches the preset aging condition.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiments of the present specification. One of ordinary skill in the art can understand and implement it without inventive effort.
While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any invention or of what may be claimed, but rather as descriptions of features specific to particular embodiments of particular inventions. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. In other instances, features described in connection with one embodiment may be implemented as discrete components or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In some cases, multitasking and parallel processing may be advantageous. Moreover, the separation of various system modules and components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.
Thus, particular embodiments of the subject matter have been described. Other embodiments are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. Further, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some implementations, multitasking and parallel processing may be advantageous.
The above description is only a preferred embodiment of the present disclosure, and should not be taken as limiting the present disclosure, and any modifications, equivalents, improvements, etc. made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.
Claims (10)
1. A DNS resolution method is applied to load balancing equipment in a multilink scene, and the method comprises the following steps:
receiving a DNS request message, and acquiring a target domain name requested to be analyzed by the message;
determining whether the number of resolution requests corresponding to the target domain name in a prestored DNS resolution table entry reaches a preset resolution frequency threshold value;
if the DNS request message reaches the threshold value, returning a DNS response message to the client side which sends the DNS request message according to a domain name resolution result recorded in the DNS resolution table entry;
if the bandwidth utilization rate does not reach the threshold value, obtaining the bandwidth utilization rate of each alternative link, and determining the priority sequence of each alternative link according to the bandwidth utilization rate; determining a target link for the DNS analysis according to the priority sequence; the link with low bandwidth utilization rate has high priority;
sending the received DNS request message to a DNS server through the target link, and receiving a DNS response message returned by the DNS server;
and sending a DNS response message returned by the DNS server to the client side sending the DNS request message through the target link, and updating the DNS analysis table entry according to the DNS request message and the DNS response message so as to perform DNS analysis according to the updated DNS analysis table entry.
2. The method according to claim 1, wherein the updating the DNS resolution entry according to the DNS request message and the DNS reply message comprises:
determining a plurality of resolution parameters recorded in the DNS resolution table entry;
obtaining parameter values of the analysis parameters in the DNS request message and the DNS response message;
and updating and/or increasing the parameter values recorded in the DNS resolution table entry according to the obtained parameter values.
3. The method of claim 2, wherein the resolution parameters comprise one or more of the following parameters:
sending a source address of the DNS request message, a domain name requested to be analyzed by the DNS request message, recording aging time, a DNS server for performing DNS analysis, a target link for processing the DNS request message, DNS analysis request times and a DNS analysis result.
4. The method of claim 1, further comprising:
for any record of the DNS resolution table entry:
monitoring whether the record reaches a preset aging condition;
if yes, deleting the record from the DNS resolution table entry.
5. The method of claim 4, wherein monitoring whether the record meets a predetermined aging condition comprises:
acquiring the aging time in the record, and judging whether the acquired aging time reaches a preset threshold value; if so, determining that the record reaches a preset aging condition; and/or
Obtaining the address of the domain name resolution result and/or the DNS server address in the record, and taking the obtained address as a target address; and sending a detection message to the target address through a target link in the record, and determining whether the record reaches a preset aging condition according to the data condition of the target link and/or the response condition of the target address.
6. The method according to claim 5, wherein the determining whether the record reaches a preset aging condition according to the data condition of the target link and/or the response condition of the target address comprises:
counting the packet loss rate, the time delay and/or the number of data packets passing through the target link of the target link within a preset time period, and determining that the record reaches a preset aging condition under the condition that the counted number meets a preset condition;
and/or
Determining whether a response message sent by the target address is received, wherein the response message is used for responding to the detection message; if not, determining that the record reaches the preset aging condition.
7. The DNS resolution device is applied to load balancing equipment in a multilink scene, and comprises the following components:
the message receiving module is used for receiving a DNS request message and acquiring a target domain name requested to be analyzed by the message;
the table item query module is used for determining whether the number of times of resolution requests corresponding to the target domain name in the prestored DNS resolution table items reaches a preset resolution frequency threshold value;
the link selection module is used for obtaining the bandwidth utilization rate of each alternative link under the condition that the bandwidth utilization rate does not reach a threshold value, and determining the priority sequence of each alternative link according to the bandwidth utilization rate; determining a target link for the DNS analysis according to the priority sequence; the link with low bandwidth utilization rate has high priority;
the response obtaining module is used for returning a DNS response message to the client side which sends the DNS request message according to the domain name resolution result recorded in the DNS resolution table entry under the condition that the threshold value is reached; and under the condition that the threshold value is not reached, sending the received DNS request message to a DNS server through the target link, and receiving a DNS response message returned by the DNS server;
and the table item updating module is used for sending a DNS response message returned by the DNS server to the client side sending the DNS request message through the target link, and updating the DNS analysis table item according to the DNS request message and the DNS response message so as to carry out DNS analysis according to the updated DNS analysis table item.
8. The apparatus of claim 7, wherein the entry update module comprises:
the parameter determination submodule is used for determining a plurality of resolution parameters recorded in the DNS resolution table entry;
a parameter value obtaining submodule for obtaining parameter values of the analysis parameters in the DNS request message and the DNS response message;
and the expression updating submodule is used for updating and/or increasing the parameter values recorded in the DNS resolution table entry according to the obtained parameter values.
9. The apparatus according to claim 7, wherein the apparatus further includes an entry monitoring module, which specifically includes:
a condition monitoring submodule, configured to, for any record of the DNS resolution table entry: monitoring whether the record reaches a preset aging condition;
and the record deleting submodule is used for deleting any record from the DNS analysis table entry under the condition that the record reaches a preset aging condition.
10. The apparatus of claim 9, wherein the condition monitoring submodule comprises:
the time monitoring unit is used for obtaining the aging time in the record and judging whether the obtained aging time reaches a preset threshold value; if so, determining that the record reaches a preset aging condition; and/or
The state monitoring unit is used for obtaining the address of the domain name resolution result and/or the DNS server address in the record and taking the obtained address as a target address; and sending a detection message to the target address through a target link in the record, and determining whether the record reaches a preset aging condition according to the data condition of the target link and/or the response condition of the target address.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910022098.3A CN109842566B (en) | 2019-01-10 | 2019-01-10 | DNS (Domain name Server) analysis method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910022098.3A CN109842566B (en) | 2019-01-10 | 2019-01-10 | DNS (Domain name Server) analysis method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109842566A CN109842566A (en) | 2019-06-04 |
| CN109842566B true CN109842566B (en) | 2023-01-24 |
Family
ID=66883742
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910022098.3A Active CN109842566B (en) | 2019-01-10 | 2019-01-10 | DNS (Domain name Server) analysis method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109842566B (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111953681B (en) * | 2020-08-11 | 2022-06-07 | 福州职业技术学院 | DNS identity authentication method and terminal |
| CN112711480B (en) * | 2020-12-24 | 2024-04-26 | 北京志翔信息技术有限公司 | Data link analysis method and system |
| CN113076212A (en) * | 2021-03-29 | 2021-07-06 | 青岛特来电新能源科技有限公司 | Cluster management method, device and equipment and computer readable storage medium |
| CN114363288B (en) * | 2021-12-16 | 2024-08-06 | 北京华耀科技有限公司 | Message processing method, device, link load balancing equipment and storage medium |
| CN114629822B (en) * | 2022-04-18 | 2024-06-11 | 北京小米移动软件有限公司 | Link detection method, device, electronic equipment and storage medium |
| CN115118700B (en) * | 2022-06-27 | 2024-03-15 | 北京天融信网络安全技术有限公司 | Communication method and communication system |
| CN116248631B (en) * | 2022-12-02 | 2024-05-14 | 中国互联网络信息中心 | DoQ priority setting method and system |
| CN116066293B (en) * | 2023-04-06 | 2023-06-09 | 深圳市拓普泰克技术股份有限公司 | Wind energy PLC control system |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103780714B (en) * | 2012-10-25 | 2016-12-21 | 中国移动通信集团北京有限公司 | The detection method of a kind of dns server and device |
| CN106161667A (en) * | 2015-04-27 | 2016-11-23 | 中国移动通信集团公司 | A kind of domain name analytic method and device |
| CN105991347A (en) * | 2015-04-30 | 2016-10-05 | 杭州迪普科技有限公司 | Redirection method of DNS request message and device |
| CN104935683A (en) * | 2015-06-29 | 2015-09-23 | 北京经天科技有限公司 | Buffer processing method and device for domain name resolution |
| CN108270881B (en) * | 2018-01-23 | 2021-03-23 | 杭州迪普科技股份有限公司 | Domain name resolution method and device |
-
2019
- 2019-01-10 CN CN201910022098.3A patent/CN109842566B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN109842566A (en) | 2019-06-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109842566B (en) | DNS (Domain name Server) analysis method and device | |
| CN111262938B (en) | DNS server selection method and proxy server | |
| CN110855633B (en) | DDOS attack protection method, device, system, communication equipment and storage medium | |
| EP3876607A1 (en) | Intelligent scheduling method, terminal device, edge node cluster and intelligent scheduling system | |
| CN108173976B (en) | Domain name resolution method and device | |
| US7698561B2 (en) | Method and system for detection of aliases in a network | |
| CN109787827B (en) | CDN network monitoring method and device | |
| CN108234207B (en) | Fault positioning method and device based on Content Delivery Network (CDN) | |
| CN105847381A (en) | Scheduling method and device for content server | |
| CN105871975A (en) | Method and device for selecting source server | |
| CN104270291A (en) | Content delivery network (CDN) quality monitoring method | |
| CN109474718B (en) | Domain name resolution method and device | |
| US11811638B2 (en) | Adaptable software defined wide area network application-specific probing | |
| CN104144223B (en) | A kind of data capture method and device | |
| CN111769997A (en) | Method, server, device and computer readable medium for network monitoring | |
| CN112261133A (en) | CDN node control method, device, server and storage medium | |
| CN115103008B (en) | Service request forwarding system | |
| CN114363288A (en) | Message processing method and device, link load balancing equipment and storage medium | |
| CN108683561B (en) | Site state detection method and device | |
| US20190037044A1 (en) | Content distribution and delivery optimization in a content delivery network (cdn) | |
| CN110380981B (en) | Flow distribution method and equipment | |
| CN109347766B (en) | Resource scheduling method and device | |
| CN113259492B (en) | Service request forwarding method and system | |
| CN104158735A (en) | Network data package distribution method and device | |
| CN114338794A (en) | Service message pushing method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |