CN108173979B - Message processing method, device, equipment and storage medium - Google Patents

Message processing method, device, equipment and storage medium Download PDF

Info

Publication number
CN108173979B
CN108173979B CN201711421621.7A CN201711421621A CN108173979B CN 108173979 B CN108173979 B CN 108173979B CN 201711421621 A CN201711421621 A CN 201711421621A CN 108173979 B CN108173979 B CN 108173979B
Authority
CN
China
Prior art keywords
domain name
dns
target
target domain
dns server
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
Application number
CN201711421621.7A
Other languages
Chinese (zh)
Other versions
CN108173979A (en
Inventor
董瑶
廖杨
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
New H3C Security Technologies Co Ltd
Original Assignee
New H3C Security Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by New H3C Security Technologies Co Ltd filed Critical New H3C Security Technologies Co Ltd
Priority to CN201711421621.7A priority Critical patent/CN108173979B/en
Publication of CN108173979A publication Critical patent/CN108173979A/en
Application granted granted Critical
Publication of CN108173979B publication Critical patent/CN108173979B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1036—Load balancing of requests to servers for services different from user content provisioning, e.g. load balancing across domain name servers

Abstract

The embodiment of the application provides a message processing method, a message processing device, message processing equipment and a storage medium, which are applied to LB equipment, wherein the method comprises the following steps: receiving a DNS request message sent by user equipment; the DNS request message comprises a target domain name and a target domain name type; searching target DNS server information corresponding to a target domain name and a target domain name type from a pre-stored corresponding relation among the domain name, the domain name type and the DNS server information; sending the DNS request message to a target DNS server corresponding to the information of the target DNS server; and the target DNS server analyzes the DNS request message and feeds a DNS response message back to the user equipment. By applying the technical scheme provided by the embodiment of the application, the success rate of the user equipment for acquiring the domain name is improved, and the user experience is improved.

Description

Message processing method, device, equipment and storage medium
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method, an apparatus, a device, and a storage medium for processing a packet.
Background
Currently, when a user equipment in a private network acquires a certain network Service, the user equipment can access an extranet server with the network Service through links of different ISPs (Internet Service providers).
When acquiring network services, a user equipment sends a Domain Name System (DNS) request message carrying a Domain Name and a Domain Name type to an optical fiber (LB) device, and the LB device sends the DNS request message to an ISP DNS server according to a scheduling algorithm and a Load balancing principle. The DNS server of the ISP resolves the domain name carried in the DNS request message to obtain IP (Internet Protocol, network Protocol) address information conforming to the domain name type carried in the DNS request message, carries the obtained IP address information in the DNS response message, and sends the DNS response message to the user equipment through the LB device. Thus, the user equipment can access the external network server through the obtained IP address information to obtain the corresponding network service.
When the user equipment acquires the network service, after the LB device sends the DNS request packet to an ISP DNS server, if the DNS server of the ISP does not record the domain name carried in the DNS request packet and the IP address information corresponding to the domain name type, the ISP DNS server will fail to resolve the domain name, and the user equipment cannot normally access the external network to acquire the network service.
Disclosure of Invention
An object of the embodiments of the present application is to provide a method, an apparatus, a device, and a storage medium for processing a packet, so as to improve the probability that user equipment obtains a successful result of domain name resolution, and improve user experience. The specific technical scheme is as follows:
in a first aspect, an embodiment of the present application discloses a packet processing method, which is applied to an LB device, and the method includes:
receiving a DNS request message sent by user equipment; the DNS request message comprises a target domain name and a target domain name type;
searching target DNS server information corresponding to the target domain name and the target domain name type from a pre-stored corresponding relation among the domain name, the domain name type and the DNS server information;
and sending the DNS request message to a target DNS server corresponding to the information of the target DNS server so that the target DNS server can analyze the DNS request message and feed back a DNS response message.
In a second aspect, an embodiment of the present application discloses a packet processing apparatus, which is applied to an LB device, and the apparatus includes:
the receiving unit is used for receiving a DNS request message sent by user equipment; the DNS request message comprises a target domain name and a target domain name type;
the searching unit is used for searching target DNS server information corresponding to the target domain name and the target domain name type from the corresponding relation among the domain name, the domain name type and the DNS server information which are stored in advance;
and the sending unit is used for sending the DNS request message to a target DNS server corresponding to the information of the target DNS server so that the target DNS server can analyze the DNS request message and feed back a DNS response message.
In a third aspect, an embodiment of the present application discloses an LB device, including a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor, the processor being caused by the machine-executable instructions to: the method for processing any message is realized.
In a fourth aspect, embodiments of the present application disclose a machine-readable storage medium storing machine-executable instructions that, when invoked and executed by a processor, cause the processor to: the method for processing any message is realized.
In the embodiment of the application, the corresponding relation among the domain name, the domain name type and the DNS server information is stored in advance. The LB device determines target DNS server information corresponding to a target domain name and a target domain name type according to a pre-stored corresponding relation among the domain name, the domain name type and the DNS server information, and sends a DNS request message to a target DNS server corresponding to the target DNS server information. The target DNS server stores address information corresponding to a target domain name and a target domain name type. Therefore, the target DNS server analyzes the target domain name carried by the DNS request message, the address information corresponding to the target domain name type can be successfully obtained, the problems that the DNS server of the ISP fails to analyze the domain name and the user equipment cannot normally access the external network due to the fact that the address information corresponding to the domain name and the domain name type carried by the DNS request message is not recorded in the DNS server of some ISP are solved, the probability that the user equipment obtains the successful result of domain name analysis is improved, and user experience is improved. Of course, it is not necessary for any product or method of the present application to achieve all of the above-described advantages at the same time.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings 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 of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a first flowchart illustrating a message processing method according to an embodiment of the present application;
fig. 2 is a schematic diagram of a network provided in the embodiment of the present application;
fig. 3 is a second flowchart of a message processing method according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a message processing apparatus according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of an LB apparatus according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In order to improve the success rate of obtaining a domain name by user equipment and improve user experience, the embodiment of the application provides a message processing method and device.
Referring to fig. 1, fig. 1 is a first flowchart illustrating a message processing method provided in an embodiment of the present application, and is applied to an LB device.
Step 101: the LB equipment receives a DNS request message sent by the user equipment. The DNS request message comprises a target domain name and a target domain name type.
The domain name type may include multiple types, and one domain name type corresponds to one type of address information. For example, the domain name type a corresponds to an IPv4(IP version 4, fourth version of internet protocol) address, and the domain name type aaaa corresponds to an IPv6(IP version 6, sixth version of internet protocol) address.
When the user equipment needs to access the network resource, the user equipment sends a DNS request message to the LB equipment. The LB equipment receives a DNS request message sent by the user equipment.
Step 102: the LB device searches target DNS server information corresponding to a target domain name and a target domain name type from the corresponding relation among the domain name, the domain name type and the DNS server information which are stored in advance.
The target DNS server information may include: IP address of the target DNS server, MAC (Media Access Control) address, and the like.
In an embodiment of the present application, if the LB device finds a plurality of pieces of DNS server information corresponding to the target domain name and the target domain name type from the correspondence among the domain name, the domain name type, and the DNS server information stored in advance, the LB device may select one piece of DNS server information from the plurality of pieces of DNS server information as the target DNS server information.
When the LB device selects one piece of target DNS server information from the plurality of pieces of DNS server information, the LB device may randomly select one piece of DNS server information from the plurality of pieces of DNS server information as the target DNS server information, or may select one piece of DNS server information from the plurality of pieces of DNS server information as the target DNS server information according to a principle of load balancing, which is not limited in this embodiment of the present application.
Step 103: and the LB equipment sends the DNS request message to a target DNS server corresponding to the information of the target DNS server.
The target DNS server records the corresponding relation of the target domain name, the target domain name type and the target address information, and after receiving the DNS request message, the target DNS server can successfully analyze the DNS request message to obtain the target address information, and carries the target address information in a DNS response message to send the DNS response message to the LB equipment. The LB equipment sends the DNS response message to the user equipment, so that the user equipment is ensured to normally access the external network and obtain network resources.
In the embodiment of the application, the corresponding relation among the domain name, the domain name type and the DNS server information is stored in advance. The LB device determines target DNS server information corresponding to a target domain name and a target domain name type according to a pre-stored corresponding relation among the domain name, the domain name type and the DNS server information, and sends a DNS request message to a target DNS server corresponding to the target DNS server information. The target DNS server stores address information corresponding to a target domain name and a target domain name type. Therefore, the target DNS server analyzes the target domain name carried by the DNS request message, the address information corresponding to the target domain name type can be successfully obtained, the problems that the DNS server of the ISP fails to analyze the domain name and the user equipment cannot normally access the external network due to the fact that the address information corresponding to the domain name and the domain name type carried by the DNS request message is not recorded in the DNS server of some ISP are solved, the probability that the user equipment obtains the successful result of domain name analysis is improved, and user experience is improved.
In an embodiment of the present application, in order to facilitate flexible control of the lookup of the target DNS server information, a load balancing policy may be set in the LB device. The load balancing strategy comprises the following steps: the corresponding relation among the domain name, the domain name type and the DNS server information. The DNS server corresponding to the DNS server information in the load balancing policy stores: and address information corresponding to the domain name and the domain name type in the load balancing strategy. The address information is address information of an external network server to be accessed by the user equipment.
When the LB device starts the function of generating the load balancing strategy, the LB device searches the target DNS server information corresponding to the target domain name and the target domain name type from the corresponding relation among the domain name, the domain name type and the DNS server information included in the load balancing strategy. Alternatively, the function may be turned on by a turn-on command.
In an embodiment of the application, if the LB device does not find the target DNS server information corresponding to the target domain name and the target domain name type from the load balancing policy, that is, from the correspondence among the domain name, the domain name type, and the DNS server information stored in advance, the LB device may determine a target DNS server from the DNS servers associated with the LB device according to a preset scheduling algorithm, in order to ensure that the user equipment accesses the network resource.
The DNS server associated with the LB device is the DNS server corresponding to the DNS server information recorded in the LB device. The DNS server information in the load balancing policy is a part or all of the DNS server information recorded in the LB device.
The scheduling algorithm includes, but is not limited to, a random algorithm, a source IP hash algorithm, a source IP source port hash algorithm, a reinforced polling algorithm, and the like.
For example, if the preset scheduling algorithm is a random algorithm, the LB device randomly selects one DNS server from DNS servers associated with the LB device as the target DNS server.
If the preset scheduling algorithm is a source IP hash algorithm, the LB device calculates a hash value of a source IP address of the DNS request message, determines a DNS server corresponding to the calculated hash value from a pre-stored corresponding relation between the hash value and a DNS server associated with the LB device, and takes the DNS server as a target DNS server.
If the preset scheduling algorithm is a source IP source port hash algorithm, the LB device calculates a hash value which is common to a source IP address and a source port of the DNS request message, determines a DNS server corresponding to the calculated hash value from a pre-stored corresponding relation between the hash value and a DNS server associated with the LB device, and takes the DNS server as a target DNS server.
If the preset scheduling algorithm is a reinforced polling algorithm, the LB device allocates a weight proportion to the DNS server associated with each LB device in advance, and determines one DNS server from the DNS servers associated with the LB device as a target DNS server according to the weight proportion. For example, the LB device is associated with a DNS server 1 and a DNS server 2, where the weight ratio of the DNS server 1 is 1 and the weight ratio of the DNS server 2 is 2. When the LB device receives 1 DNS request message, the DNS server 1 is used as a target DNS server, and the 1 DNS request message is sent to the DNS server 1. Then, the 2 DNS request messages received by the LB device all send the DNS server 2 to the DNS server 2, with the DNS server 2 being the target DNS server.
And the LB equipment determines a target DNS server according to a preset scheduling algorithm and then sends the DNS request message to the target DNS server. The target DNS server analyzes the target domain name carried in the DNS request message and sends an analysis result carried in a DNS response message to the LB device. And the LB equipment feeds the DNS response message back to the user equipment.
When the LB device starts a function of generating a load balancing policy, but the LB device does not find target DNS server information corresponding to a target domain name and a target domain name type from the load balancing policy, the target DNS server may resolve the domain name successfully, and obtain target address information, or may fail to resolve, and obtain no target address information.
If the resolution fails, the DNS reply message fed back by the DNS request message does not carry the destination address information, the user equipment cannot obtain the destination address information and cannot access the network resource, and in order to ensure that the user equipment can successfully access the network resource again, the LB device detects each DNS server associated therewith according to a predetermined period according to a correspondence between the destination domain name and the destination domain name type, as follows.
The LB device carries the target domain name and the target domain name type carried in the DNS response message in the DNS detection request message, and sends the DNS detection request message to each DNS server associated with the LB device.
In an embodiment of the present application, in order to facilitate detection of each DNS server associated with the LB device, after receiving a DNS reply packet carrying analysis failure information, the LB device records a correspondence between a target domain name and a target domain name type. Then, the LB device detects each associated DNS server according to the corresponding relation between the recorded target domain name and the target domain name type according to a preset period.
In an embodiment of the present application, in order to save resources and network resources of the LB device, when the LB device starts a function of generating a load balancing policy, but the LB device does not find target DNS server information corresponding to a target domain name and a target domain name type from the load balancing policy, if a DNS reply message received by the LB device carries analysis success information, a corresponding relationship between the target domain name and the target domain name type is not recorded. That is, when the DNS reply message carries the information of successful resolution, the LB device does not need to detect each DNS server associated therewith according to the predetermined period according to the correspondence between the target domain name and the target domain name type.
After receiving the detection DNS request message, each DNS server associated with the LB device respectively analyzes the target domain name carried in the detection DNS request message, and feeds back the analysis result carried in the detection DNS response message to the LB device. Here, if the DNS server obtains target address information corresponding to the type of the target domain name when analyzing the target domain name, the domain name is successfully analyzed, and detecting the analysis result in the DNS reply message includes: and resolving success information, a target domain name type and target address information. If the DNS server does not obtain the address information corresponding to the type of the target domain name when analyzing the target domain name, the domain name analysis fails, and the detection of the analysis result in the DNS response message comprises the following steps: analyzing failure information, a target domain name and a target domain name type.
In the embodiment of the present application, the difference between the detection DNS request packet and the DNS request packet is that the detection DNS request packet carries a DNS request packet with a detection identifier, and the detection identifier may be determined by user definition and added to a reserved field of a packet header of the DNS request packet. Therefore, new messages do not need to be added, and network resources are saved. In addition, after the LB device receives the response message of the probe DNS request message, that is, after the probe DNS response message is received, the LB device may obtain the probe identifier from the reserved field of the header of the probe DNS response message, and then determine that the message is the probe response message according to the probe identifier, without sending the probe DNS response message to the user equipment. At this time, the LB device realizes health detection of the DNS server by periodically sending the detection DNS request message, determines whether the DNS server stores the address information corresponding to the target domain name and the target domain name type, and improves the success rate of the user equipment obtaining the successful result of domain name resolution.
If the detection DNS response message carrying the analysis success information exists in the detection DNS response message received by the LB device, the LB device stores the corresponding relation among the target domain name, the type of the target domain name and the DNS server information of the DNS server sending the detection DNS response message carrying the analysis success information. For example, the LB device stores a correspondence between the target domain name, the type of the target domain name, and DNS server information of the DNS server that sends the probe DNS reply packet carrying the successfully resolved information, in the load balancing policy. In addition, the LB device stops detecting each associated DNS server according to the corresponding relation between the target domain name and the target domain name type and according to a preset period.
If the detection DNS response message carrying the analysis success information does not exist in the detection DNS response message received by the LB device, the LB device continues to detect each associated DNS server according to the corresponding relation between the target domain name and the target domain name type and according to a preset period.
For example, the preset sounding flag is TTT. The LB device constructs a DNS request message 1 carrying a domain name 1 and a domain name type 1, and adds TTT in a reserved field of a message header of the DNS request message 1 to obtain a detection DNS request message 1.
The LB device sends a probe DNS request message 1 to its associated DNS servers.
Then, the LB device receives 2 DNS servers as response messages to the DNS request message 1, that is, receives DNS response messages with TTTs in the reserved fields of the headers of the 2 DNS servers, which are respectively the DNS response message 11 fed back by the DNS server 1 and the DNS response message 12 fed back by the DNS server 2.
If the detection DNS reply message 11 carries an analysis success message: detecting that Reply code (Reply code) in DNS Reply message 11 is No error (0), indicating that domain name resolution is error-free, detecting that DNS Reply message 12 resolves failure message: detecting that the Reply code in the DNS Reply message 12 is No Such name (3), indicating that the domain name does not exist, the LB device stores the correspondence between the domain name 1, the domain name type 1, and the DNS server information of the DNS server 1.
If the detection DNS reply message 11 carries an analysis failure message: detecting that the Reply code in the DNS Reply message 11 is No Such name (3), and detecting that the DNS Reply message 12 resolves the failure message: if the Reply code in the DNS Reply message 12 is No Such name (3), the LB device sends a DNS request message 1 according to a predetermined cycle.
In an embodiment of the present application, the LB device may accumulate and record the number of cycles of sending the probe DNS request message. If the number of the accumulated records reaches the number threshold, the LB device can determine that the DNS server recorded with the address information corresponding to the target domain name and the target domain name type does not exist in the network, and stop detecting each associated DNS server according to the corresponding relation between the target domain name and the target domain name type and the preset period, so as to save LB device resources.
For example, the number threshold is 3, the predetermined period is 10 minutes, and the LB device records the correspondence between domain name 1 and domain name type 1.
If the ratio is 10:00, the LB device sends the domain name 1 and the domain name type 1 carried in the detection DNS request message 1 to each DNS server associated with the LB device, and detects each DNS server associated with the LB device. If the detection DNS response message carrying the analysis success information is not received after the detection DNS request message is sent at 10:00, the number of the accumulated and recorded cycles of sending the detection DNS request message 1 is 1.
When the ratio is 10:10, the LB device sends the domain name 1 and the domain name type 1 carried in the detection DNS request message 1 to each DNS server associated with the LB device again, and detects each DNS server associated with the LB device. And if the detection DNS response message carrying the analysis success information is not received after the detection DNS request message is sent by the ratio of 10:10, the number of the accumulated and recorded cycles of sending the detection DNS request message 1 is 2.
When the ratio is 10:20, the LB device sends the domain name 1 and the domain name type 1 carried in the detection DNS request message 1 to each DNS server associated with the LB device again, and detects each DNS server associated with the LB device. If the detection DNS response message carrying the analysis success information is not received after the detection DNS request message is sent by 10:20, the number of the accumulated cycles of sending the detection DNS request message 1 is 3.
At this time, the number of cycles of sending the detection DNS request message 1 recorded cumulatively by the LB device is 3, the number of cycles of sending the detection DNS request message 1 recorded cumulatively reaches the number threshold, and the domain name 1 and the domain name type 1 carried in the detection DNS request message 1 are stopped from being sent again to each DNS server associated with the LB device, so as to detect each DNS server associated with the LB device.
In an embodiment of the present application, if the corresponding relationship between the target domain name and the target domain name type is recorded in the LB device, when it is detected that a detection DNS reply packet carrying information on which resolution is successful exists or the number of cycles of sending a detection DNS request packet reaches a number threshold, the recorded corresponding relationship between the target domain name and the target domain name type is deleted, so as to save a storage space of the LB device.
In an embodiment of the present application, if the LB device does not start the function of generating the load balancing policy, the LB device determines, according to a preset scheduling algorithm, a target DNS server from DNS servers associated with the LB device, and sends a DNS request packet to the target DNS server. The target DNS server analyzes the target domain name carried in the DNS request message and sends an analysis result carried in a DNS response message to the LB device. And the LB equipment feeds the DNS response message back to the user equipment.
The following describes an embodiment of the present application in detail with reference to the networking shown in fig. 2 and a second flowchart of the message processing method shown in fig. 3. The networking includes user equipment 100, LB equipment 200, DNS server 300, DNS server 301, and DNS server 302. The DNS server 301 and the DNS server 302 are DNS servers with which the LB appliance 200 is associated. The LB device 200 turns on the DNS transparent proxy function. Here, the DNS transparent proxy is: the user equipment does not need to know the DNS server, only needs to send the DNS request message to the LB equipment, and the LB equipment determines the DNS server for analyzing the domain name to realize domain name analysis.
The message processing method is applied to the LB device 200, the LB device 200 is provided with a load balancing policy and a function of generating the load balancing policy, and when the function of generating the load balancing policy is started, the LB device 200 can dynamically generate the load balancing policy according to a DNS response message or a detection DNS response message. And starting the function of generating the load balancing strategy when the LB device receives a starting instruction.
When the user equipment 100 needs to access a network resource, the user equipment 100 sends a DNS request message to the LB device 200.
Step 01, the LB device 200 receives the DNS request message sent by the user equipment 100. The DNS request message comprises a target domain name and a target domain name type.
Step 02, the LB device 200 detects whether to start the function of generating the load balancing policy.
If not, go to step 03.
If yes, go to step 06.
In an embodiment of the present application, if the LB device 200 receives an activation instruction of the function that generates the load balancing policy, the function that generates the load balancing policy is activated. The LB device 200, if receiving a shutdown instruction for the function of generating the load balancing policy issued by the user, shuts down the function of generating the load balancing policy.
Step 03, the LB device 200 selects a DNS server from the DNS servers 300 and 302 as a target DNS server according to a preset scheduling algorithm, for example, selects the DNS server 300, and sends the DNS request message to the DNS server 300.
Step 04, the LB device 200 receives a DNS reply message fed back by the DNS server 300 according to the DNS request message.
Step 05, the LB device 200 feeds back the DNS reply message to the user equipment 100.
Step 06, if it is detected in step 02 that the function of generating the load balancing policy is turned on, the LB device 200 searches for target DNS server information corresponding to the target domain name and the target domain name type from the correspondence among the domain name, the domain name type, and the DNS server information included in the load balancing policy.
If the target DNS server information is found, the LB device 200 determines the target DNS server according to the target DNS server information, for example, if the target DNS server information is the DNS server information of the DNS server 301, determines that the target DNS server is the DNS server 301, and executes step 07.
If the information of the target DNS server is not found, the LB device 200 determines the target DNS server according to a preset scheduling algorithm, for example, determines the target DNS server as the DNS server 301 according to the preset scheduling algorithm, and performs step 07.
The determination of the target DNS server according to the target DNS server information and the determination of the target DNS server according to the preset scheduling algorithm may be the same or different. For ease of understanding, the description is given only by taking the DNS server 301 as the target DNS server.
Step 07, the LB device 200 sends the DNS request message to the DNS server 301.
Step 08, the LB device 200 receives a DNS reply message fed back by the DNS server 301 according to the DNS request message.
Step 09, if the DNS reply message carries the successful analysis information: the Reply code is No error (0), and the LB device 200 feeds back the DNS Reply message to the user equipment 100.
At this time, since the DNS server successfully resolves the target domain name, the address information corresponding to the type of the target domain name is obtained, and in order to save resources of the LB device, when receiving the DNS response packet carrying the successfully resolved information, the LB device does not need to generate a load balancing policy according to the target domain name and the type of the target domain name in the DNS response packet.
Step 10, if the DNS reply message carries an analysis failure message: the Reply code is No Suchname (3), and the LB device 200 feeds back the DNS Reply packet to the user device 100, records the correspondence between the target domain name and the target domain name type, and executes step 11.
In an embodiment of the present application, to save the storage space of the LB device, before recording the correspondence between the target domain name and the target domain name type, the LB device 200 determines whether the correspondence between the target domain name and the target domain name type is currently locally recorded.
If not, the LB device 200 records a correspondence between the target domain name and the target domain name type. If so, the LB device 200 does not record the correspondence between the target domain name and the target domain name type.
Step 11, the LB device 200 carries the target domain name and the target domain name type in the detection DNS request message according to the predetermined period, and sends the detection DNS request message to the DNS server 300 and 302.
In an embodiment of the present application, two tables, for example, table a and table B, may be preset, where both table a and table B are used to store a correspondence between a target domain name and a target domain name type. The table a is used to store the corresponding relationship between the domain name and the domain name type that is not carried in the detection DNS request message and is sent to each DNS server. After the LB device carries the target domain name and the target domain name type recorded in table a in the detection DNS request message and sends the detection DNS request message to the DNS server, if a detection DNS reply message that is successfully resolved is not obtained, the LB device transfers the correspondence between the target domain name and the target domain name type to table B. Then, the LB device 200 carries the target domain name and the target domain name type in the detection DNS request message according to the correspondence between the target domain name and the target domain name type stored in the table B and according to the predetermined period, and sends the detection DNS request message to the DNS server 300 and 302.
For example, in step 10, the LB appliance 200 records the correspondence between the target domain name and the target domain name type in table a. In step 11, after the LB device 200 carries the target domain name and the target domain name type in the detection DNS request message and sends the detection DNS request message to the DNS server 300 and 302, if the detection DNS reply message carrying the analysis success information is not obtained, the corresponding relationship between the target domain name and the target domain name type is transferred to the table B.
When probing each DNS server, the LB device may first probe based on the correspondence stored in table a. If the DNS server records target address information corresponding to a target domain name and a target domain name type, the LB device can obtain a detection DNS response message of successfully analyzed information when detecting for the first time, if the detection DNS response message of successfully analyzed information is not obtained when detecting for the first time, the possibility of later detection is much lower, the detection is performed on the basis of the corresponding relation stored in the table A, the LB device can be ensured to quickly obtain the corresponding relation among the domain name, the domain name type and the DNS server information, and LB device resources are saved.
Step 12, the LB device 200 receives the probe DNS reply message fed back by each DNS server 300 and 302 according to the probe DNS request message.
If the detection DNS response message carrying the analysis success information exists, executing step 16.
And if the detection DNS response message carrying the analysis success information does not exist, returning to execute the step 13.
Step 13, the LB device 200 accumulatively records the number of cycles of sending the DNS request message.
And step 14, the LB device detects whether the number of the accumulated record cycles reaches a number threshold value.
If the number threshold is reached, go to step 15.
If the number threshold is not reached, the step 11 is executed again.
Step 15, the LB device 200 deletes the correspondence between the target domain name and the target domain name type.
To illustrate by way of example in step 10, the deletion table B records the correspondence between the target domain name and the target domain name type.
Step 16, the LB device 200 stores the correspondence between the target domain name, the target domain name type, and the DNS server information of the DNS server that sends the detection DNS reply packet carrying the successfully resolved information, and deletes the recorded correspondence between the target domain name and the target domain name type.
Taking the example in step 10 for illustration, the LB device 200 may store the correspondence between the target domain name and the target domain name type carried in the probe DNS response packet and the DNS server information of the DNS server that sends the probe DNS response packet carrying the analysis success information into the load balancing policy, and delete the correspondence between the target domain name and the target domain name type recorded in table a or table B.
For example, if a detection DNS request packet constructed for a target domain name and a target domain name type stored in table B carries information that is successfully resolved in a feedback detection DNS response packet, the target domain name type, and the target DNS server information carried in the detection DNS response packet are stored in a load balancing policy, and a correspondence between the target domain name and the target domain name type in table B is deleted.
Corresponding to the embodiment of the message processing method, the embodiment of the application also provides a message processing device. Referring to fig. 4, fig. 4 is a schematic structural diagram of a message processing apparatus according to an embodiment of the present application, which is applied to an LB device, and the apparatus includes:
a receiving unit 401, configured to receive a DNS request packet sent by a user equipment; the DNS request message comprises a target domain name and a target domain name type;
a searching unit 402, configured to search, from a correspondence among a domain name, a domain name type, and DNS server information stored in advance, target DNS server information corresponding to a target domain name and a target domain name type;
a sending unit 403, configured to send the DNS request packet to a target DNS server corresponding to the target DNS server information, so that the target DNS server analyzes the DNS request packet and feeds back a DNS response packet.
In an embodiment of the present application, the message processing apparatus may further include: a determination unit;
the determining unit is used for determining a target DNS server according to a preset scheduling algorithm if the target DNS server information corresponding to the target domain name and the target domain name type is not found;
the sending unit 403 may also be configured to send the DNS request message to the target DNS server.
In an embodiment of the present application, the message processing apparatus may further include: a storage unit;
the sending unit 403 may also be configured to, if the DNS reply message fed back by the DNS request message carries analysis failure information, carry the target domain name and the type of the target domain name carried in the DNS reply message in the detection DNS request message according to a predetermined period, and send the detection DNS request message to each DNS server associated with the LB device;
the receiving unit 401 may also be configured to receive a detection DNS reply message fed back by each DNS server according to the detection DNS request message;
and the storage unit is used for storing the corresponding relation among the target domain name, the type of the target domain name and the DNS server information of the DNS server which sends the detection DNS response message carrying the analysis success information if the detection DNS response message carrying the analysis success information exists.
In an embodiment of the application, the sending unit 403 is specifically configured to, if there is no detection DNS reply message carrying information that is successful in resolution, repeatedly execute a process of carrying a target domain name and a target domain name type carried in the DNS reply message in the detection DNS request message and sending the detection DNS request message to each DNS server connected to the LB device according to a predetermined cycle until there is a detection DNS reply message carrying information that is successful in resolution, or the number of cycles of sending the detection DNS request message reaches a number threshold.
In an embodiment of the present application, the message processing apparatus may further include: recording unit and deleting unit
The recording unit is used for recording the corresponding relation between the target domain name and the target domain name type carried in the DNS response message;
and the deleting unit is used for deleting the corresponding relation between the recorded target domain name and the target domain name type when detecting that the detection DNS response message carrying the analysis success information exists or the number of the periods for sending the detection DNS request message reaches the number threshold.
By applying the embodiment of the application, the corresponding relation among the domain name, the domain name type and the DNS server information is stored in advance. The LB device determines target DNS server information corresponding to a target domain name and a target domain name type according to a pre-stored corresponding relation among the domain name, the domain name type and the DNS server information, and sends a DNS request message to a target DNS server corresponding to the target DNS server information. The target DNS server stores address information corresponding to a target domain name and a target domain name type. Therefore, the target DNS server analyzes the target domain name carried by the DNS request message, the address information corresponding to the target domain name type can be successfully obtained, the problems that the DNS server of the ISP fails to analyze the domain name and the user equipment cannot normally access the external network due to the fact that the address information corresponding to the domain name and the domain name type carried by the DNS request message is not recorded in the DNS server of some ISP are solved, the probability that the user equipment obtains the successful result of domain name analysis is improved, and user experience is improved.
Corresponding to the message processing method embodiment, an embodiment of the present application further provides an LB device, including a processor and a machine-readable storage medium, where the machine-readable storage medium stores machine-executable instructions capable of being executed by the processor, and the processor is enabled by the machine-executable instructions to perform the message processing method described above.
One configuration of the LB device shown in fig. 5 includes a processor 501 and a machine-readable storage medium 502, where the machine-readable storage medium 502 stores machine-executable instructions capable of being executed by the processor 501.
In addition, as shown in fig. 5, the LB apparatus may further include: a communication interface 503 and a communication bus 504; the processor 501, the machine-readable storage medium 502, and the communication interface 503 are configured to complete communication with each other through the communication bus 504, and the communication interface 503 is configured to communicate with other devices through the LB device.
In an embodiment of the application, the machine executable instructions include: receive instructions 512, look-up instructions 522, and send instructions 532;
the processor 501, being received with instructions 512, causes implementation of: receiving a DNS request message sent by user equipment; the DNS request message comprises a target domain name and a target domain name type;
the processor 501 is caused by the lookup instructions 522 to implement: searching target DNS server information corresponding to a target domain name and a target domain name type from a pre-stored corresponding relation among the domain name, the domain name type and the DNS server information;
the processor 501 is caused by the send instructions 532 to implement: and sending the DNS request message to a target DNS server corresponding to the information of the target DNS server so that the target DNS server can analyze the DNS request message and feed back a DNS response message.
In one embodiment of the present application, the machine-executable instructions may further comprise: determining an instruction;
the processor 501 is caused by the determined instructions to implement: if the target DNS server information corresponding to the target domain name and the target domain name type is not found, determining a target DNS server according to a preset scheduling algorithm;
the processor 501 being caused by the send instructions 532 may also implement: and sending the DNS request message to a target DNS server.
In one embodiment of the present application, the machine-executable instructions may further comprise: storing the instruction;
the processor 501 being caused by the send instructions 532 may also implement: if the DNS response message fed back by aiming at the DNS request message carries analysis failure information, carrying the target domain name and the target domain name type in the detection DNS request message according to a preset period, and sending the detection DNS request message to each DNS server associated with the LB equipment;
the processor 501, being received with the instructions 512, is further caused to: receiving a detection DNS response message fed back by each DNS according to the detection DNS request message;
the processor 501 is stored with instructions to cause the implementation of: and if the detection DNS response message carrying the analysis success information exists, storing the corresponding relation among the target domain name, the type of the target domain name and DNS server information of a DNS server sending the detection DNS response message carrying the analysis success information.
In one embodiment of the present application, the processor 501 being sent instructions 532 causes the implementation of: if the detection DNS response message carrying the analysis success information does not exist, the process of carrying the target domain name and the target domain name type carried in the DNS response message in the detection DNS request message and sending the detection DNS request message to each DNS server connected with the LB equipment according to a preset period is repeatedly executed until the detection DNS response message carrying the analysis success information exists or the number of the periods for sending the detection DNS request message reaches a number threshold.
In one embodiment of the present application, the machine-executable instructions may further comprise: recording an instruction and deleting the instruction;
the processor 501 is recorded with instructions to cause the implementation of: recording the corresponding relation between a target domain name and a target domain name type carried in a DNS response message;
the processor 501 is caused by the delete instruction to implement: and when detecting that the number of the periods of the detection DNS response messages carrying the analysis success information or the detection DNS request message sending reaches a number threshold, deleting the corresponding relation between the recorded target domain name and the target domain name type.
By applying the embodiment of the application, the corresponding relation among the domain name, the domain name type and the DNS server information is stored in advance. The LB device determines target DNS server information corresponding to a target domain name and a target domain name type according to a pre-stored corresponding relation among the domain name, the domain name type and the DNS server information, and sends a DNS request message to a target DNS server corresponding to the target DNS server information. The target DNS server stores address information corresponding to a target domain name and a target domain name type. Therefore, the target DNS server analyzes the target domain name carried by the DNS request message, the address information corresponding to the target domain name type can be successfully obtained, the problems that the DNS server of the ISP fails to analyze the domain name and the user equipment cannot normally access the external network due to the fact that the address information corresponding to the domain name and the domain name type carried by the DNS request message is not recorded in the DNS server of some ISP are solved, the probability that the user equipment obtains the successful result of domain name analysis is improved, and user experience is improved.
The communication bus 504 may be a PCI (Peripheral Component Interconnect) bus, an EISA (Extended Industry Standard Architecture) bus, or the like. The communication bus 504 may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 5, but this is not intended to represent only one bus or type of bus.
The machine-readable storage medium 502 may include a RAM (Random Access Memory) and may also include a NVM (Non-Volatile Memory), such as at least one disk Memory. Additionally, the machine-readable storage medium 502 may also be at least one memory device located remotely from the aforementioned processor.
The Processor 501 may be a general-purpose Processor including a CPU (Central Processing Unit), an NP (Network Processor), and the like; but also DSPs (Digital Signal Processing), ASICs (Application Specific Integrated circuits), FPGAs (Field Programmable Gate arrays) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.
Corresponding to the message processing method embodiment, the embodiment of the present application further provides a machine-readable storage medium, in which machine-executable instructions are stored, and the machine-executable instructions cause a processor to implement the message processing method.
Wherein the machine-executable instructions comprise: receiving an instruction, searching the instruction and sending the instruction;
when invoked and executed by a processor, receiving instructions cause the processor to: receiving a DNS request message sent by user equipment; the DNS request message comprises a target domain name and a target domain name type;
when invoked and executed by a processor, the lookup instructions cause the processor to: searching target DNS server information corresponding to a target domain name and a target domain name type from a pre-stored corresponding relation among the domain name, the domain name type and the DNS server information;
when invoked and executed by a processor, the send instructions cause the processor to: and sending the DNS request message to a target DNS server corresponding to the information of the target DNS server so that the target DNS server can analyze the DNS request message and feed back a DNS response message.
In one embodiment of the present application, the machine-executable instructions may further comprise: determining an instruction;
when invoked and executed by a processor, the determining instructions cause the processor to: if the target DNS server information corresponding to the target domain name and the target domain name type is not found, determining a target DNS server according to a preset scheduling algorithm;
when invoked and executed by a processor, the send instructions cause the processor to further implement: and sending the DNS request message to a target DNS server.
In one embodiment of the present application, the machine-executable instructions may further comprise: storing the instruction;
when invoked and executed by a processor, the send instructions cause the processor to further implement: if the DNS response message fed back by aiming at the DNS request message carries analysis failure information, carrying the target domain name and the target domain name type in the detection DNS request message according to a preset period, and sending the detection DNS request message to each DNS server associated with the LB equipment;
when invoked and executed by a processor, receiving instructions cause the processor to further implement: receiving a detection DNS response message fed back by each DNS according to the detection DNS request message;
when invoked and executed by a processor, storing instructions causes the processor to: and if the detection DNS response message carrying the analysis success information exists, storing the corresponding relation among the target domain name, the type of the target domain name and DNS server information of a DNS server sending the detection DNS response message carrying the analysis success information.
In one embodiment of the application, the instructions, when invoked and executed by a processor, cause the processor to implement: if the detection DNS response message carrying the analysis success information does not exist, the process of carrying the target domain name and the target domain name type carried in the DNS response message in the detection DNS request message and sending the detection DNS request message to each DNS server connected with the LB equipment according to a preset period is repeatedly executed until the detection DNS response message carrying the analysis success information exists or the number of the periods for sending the detection DNS request message reaches a number threshold.
In one embodiment of the present application, the machine-executable instructions may further comprise: recording an instruction and deleting the instruction;
when invoked and executed by a processor, the recording instructions cause the processor to: recording the corresponding relation between a target domain name and a target domain name type carried in a DNS response message;
when invoked and executed by a processor, the delete instruction causes the processor to: and when detecting that the number of the periods of the detection DNS response messages carrying the analysis success information or the detection DNS request message sending reaches a number threshold, deleting the corresponding relation between the recorded target domain name and the target domain name type.
By applying the embodiment of the application, the corresponding relation among the domain name, the domain name type and the DNS server information is stored in advance. The LB device determines target DNS server information corresponding to a target domain name and a target domain name type according to a pre-stored corresponding relation among the domain name, the domain name type and the DNS server information, and sends a DNS request message to a target DNS server corresponding to the target DNS server information. The target DNS server stores address information corresponding to a target domain name and a target domain name type. Therefore, the target DNS server analyzes the target domain name carried by the DNS request message, the address information corresponding to the target domain name type can be successfully obtained, the problems that the DNS server of the ISP fails to analyze the domain name and the user equipment cannot normally access the external network due to the fact that the address information corresponding to the domain name and the domain name type carried by the DNS request message is not recorded in the DNS server of some ISP are solved, the probability that the user equipment obtains the successful result of domain name analysis is improved, and user experience is improved.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. Especially, for the embodiments of the message processing apparatus, the LB device, and the machine-readable storage medium, since they are substantially similar to the embodiments of the message processing method, the description is relatively simple, and for the relevant points, reference may be made to the partial description of the embodiments of the message processing method.
The above description is only for the preferred embodiment of the present application, and is not intended to limit the scope of the present application. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application are included in the protection scope of the present application.

Claims (10)

1. A message processing method is applied to a load balancing LB device, and comprises the following steps:
receiving a Domain Name System (DNS) request message sent by user equipment; the DNS request message comprises a target domain name and a target domain name type;
searching target DNS server information corresponding to the target domain name and the target domain name type from a pre-stored corresponding relation among the domain name, the domain name type and the DNS server information;
if the target DNS server information corresponding to the target domain name and the target domain name type is found, sending the DNS request message to a target DNS server corresponding to the target DNS server information, so that the target DNS server analyzes the DNS request message and feeds back a DNS response message;
if the target DNS server information corresponding to the target domain name and the target domain name type is not found, determining a target DNS server according to a preset scheduling algorithm; and sending the DNS request message to the target DNS server.
2. The method of claim 1, further comprising:
if a DNS response message fed back by aiming at the DNS request message carries analysis failure information, carrying the target domain name and the target domain name type carried in the DNS response message in a detection DNS request message according to a preset period, and sending the detection DNS request message to each DNS server associated with the LB equipment;
receiving a detection DNS response message fed back by each DNS according to the detection DNS request message;
and if the detection DNS response message carrying the analysis success information exists, storing the corresponding relation among the target domain name, the type of the target domain name and DNS server information of a DNS server sending the detection DNS response message carrying the analysis success information.
3. The method of claim 2, further comprising:
if the detection DNS response message carrying the analysis success information does not exist, the process of carrying the target domain name and the target domain name type carried in the DNS response message in the detection DNS request message and sending the detection DNS request message to each DNS server connected with the LB equipment according to a preset period is repeatedly executed until the detection DNS response message carrying the analysis success information exists or the number of the periods for sending the detection DNS request message reaches a number threshold value.
4. A method according to claim 2 or 3, characterized in that:
recording the corresponding relation between the target domain name and the target domain name type carried in the DNS response message;
and deleting the recorded corresponding relation between the target domain name and the target domain name type when detecting that a detection DNS response message carrying analysis success information exists or the number of the periods for sending the detection DNS request message reaches a number threshold.
5. A message processing apparatus, applied to a load balancing LB device, the apparatus comprising:
the receiving unit is used for receiving a domain name system DNS request message sent by user equipment; the DNS request message comprises a target domain name and a target domain name type;
the searching unit is used for searching target DNS server information corresponding to the target domain name and the target domain name type from the corresponding relation among the domain name, the domain name type and the DNS server information which are stored in advance;
a sending unit, configured to send the DNS request packet to a target DNS server corresponding to the target DNS server information if the target DNS server information corresponding to the target domain name and the target domain name type is found, so that the target DNS server analyzes the DNS request packet and feeds back a DNS response packet;
a determining unit, configured to determine a target DNS server according to a preset scheduling algorithm if target DNS server information corresponding to the target domain name and the target domain name type is not found;
the sending unit is further configured to send the DNS request packet to the target DNS server.
6. The apparatus of claim 5, further comprising: a storage unit;
the sending unit is further configured to, if a DNS reply message fed back in response to the DNS request message carries analysis failure information, carry the target domain name and the target domain name type carried in the DNS reply message in a detection DNS request message according to a predetermined period, and send the detection DNS request message to each DNS server associated with the LB device;
the receiving unit is further configured to receive a detection DNS reply message fed back by each DNS server according to the detection DNS request message;
and the storage unit is used for storing the corresponding relation among the target domain name, the type of the target domain name and DNS server information of a DNS server which sends the detection DNS response message carrying the analysis success information if the detection DNS response message carrying the analysis success information exists.
7. The apparatus of claim 6, further comprising:
the sending unit is specifically configured to, if there is no detection DNS reply message carrying information that is successful in resolution, repeatedly execute a process of sending the target domain name and the target domain name type carried in the DNS reply message to each DNS server connected to the LB device in a detection DNS request message according to a predetermined cycle until there is a detection DNS reply message carrying information that is successful in resolution, or the number of cycles of sending the detection DNS request message reaches a number threshold.
8. The apparatus of claim 6 or 7, further comprising:
a recording unit, configured to record a correspondence between the target domain name and the target domain name type carried in the DNS reply message;
and the deleting unit is used for deleting the recorded corresponding relation between the target domain name and the target domain name type when detecting that a detection DNS response message carrying analysis success information exists or the number of the periods for sending the detection DNS request message reaches a number threshold.
9. A load balancing LB device comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor, the processor being caused by the machine-executable instructions to: carrying out the method steps of any one of claims 1 to 4.
10. A machine-readable storage medium having stored thereon machine-executable instructions that, when invoked and executed by a processor, cause the processor to: carrying out the method steps of any one of claims 1 to 4.
CN201711421621.7A 2017-12-25 2017-12-25 Message processing method, device, equipment and storage medium Active CN108173979B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201711421621.7A CN108173979B (en) 2017-12-25 2017-12-25 Message processing method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201711421621.7A CN108173979B (en) 2017-12-25 2017-12-25 Message processing method, device, equipment and storage medium

Publications (2)

Publication Number Publication Date
CN108173979A CN108173979A (en) 2018-06-15
CN108173979B true CN108173979B (en) 2021-03-12

Family

ID=62520371

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201711421621.7A Active CN108173979B (en) 2017-12-25 2017-12-25 Message processing method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN108173979B (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111262938B (en) * 2020-01-17 2021-06-22 厦门网宿有限公司 DNS server selection method and proxy server
CN111953681B (en) * 2020-08-11 2022-06-07 福州职业技术学院 DNS identity authentication method and terminal
CN112165517B (en) * 2020-09-22 2022-09-20 成都知道创宇信息技术有限公司 Return source detection method and device, storage medium and electronic equipment
CN115801731B (en) * 2023-02-08 2023-06-23 天翼云科技有限公司 Processing method and device of network message, electronic equipment and storage medium

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102771083A (en) * 2009-12-23 2012-11-07 思杰系统有限公司 Systems and methods for mixed mode of IPv6 and IPv4 DNS of global server load balancing
CN103401800A (en) * 2013-07-31 2013-11-20 杭州华三通信技术有限公司 Link load balancing method and link load balancing device
EP2747387A1 (en) * 2012-12-21 2014-06-25 Comcast Cable Communications, LLC Implementation of domain name services
CN104767690A (en) * 2014-01-08 2015-07-08 杭州迪普科技有限公司 Flow scheduling device and method
CN106790340A (en) * 2016-04-25 2017-05-31 新华三技术有限公司 A kind of link scheduling method and device
CN106878193A (en) * 2017-02-10 2017-06-20 新华三技术有限公司 A kind of load sharing method and device
CN106953945A (en) * 2017-05-26 2017-07-14 北京奇虎科技有限公司 Domain name intelligently parsing method and device, server based on SDN realizations

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102771083A (en) * 2009-12-23 2012-11-07 思杰系统有限公司 Systems and methods for mixed mode of IPv6 and IPv4 DNS of global server load balancing
EP2747387A1 (en) * 2012-12-21 2014-06-25 Comcast Cable Communications, LLC Implementation of domain name services
CN103401800A (en) * 2013-07-31 2013-11-20 杭州华三通信技术有限公司 Link load balancing method and link load balancing device
CN104767690A (en) * 2014-01-08 2015-07-08 杭州迪普科技有限公司 Flow scheduling device and method
CN106790340A (en) * 2016-04-25 2017-05-31 新华三技术有限公司 A kind of link scheduling method and device
CN106878193A (en) * 2017-02-10 2017-06-20 新华三技术有限公司 A kind of load sharing method and device
CN106953945A (en) * 2017-05-26 2017-07-14 北京奇虎科技有限公司 Domain name intelligently parsing method and device, server based on SDN realizations

Also Published As

Publication number Publication date
CN108173979A (en) 2018-06-15

Similar Documents

Publication Publication Date Title
US11632420B2 (en) Point of presence management in request routing
US10931738B2 (en) Point of presence management in request routing
CN108173979B (en) Message processing method, device, equipment and storage medium
US20190044787A1 (en) Point of presence management in request routing
US8156243B2 (en) Request routing
US9053320B2 (en) Method of and apparatus for identifying requestors of machine-generated requests to resolve a textual identifier
CN108667946B (en) Multi-domain name mutual backup analysis management method, device and system
WO2017166524A1 (en) Domain name parsing method and apparatus
CN112583952B (en) Redirection scheduling processing method, device and system, related equipment and storage medium
CN113315848A (en) Access control method, device and equipment
CN105262858B (en) Method and device for detecting safety of Domain Name System (DNS) server
US9497083B1 (en) Discovering network nodes
CN108718280B (en) Message forwarding method and device
CN107547295B (en) Aging method and device for domain name cache table entries
CN107517248B (en) Network connection method and device based on SDK
CN114363288A (en) Message processing method and device, link load balancing equipment and storage medium
CN110035134B (en) Network address translation method, device and access equipment
CN108306999B (en) Domain name resolution method and device
CN115442329A (en) Domain name information query method, system, device, equipment and storage medium
CN107592374B (en) Correction method and system for domain name error resolution
CN112738271A (en) CDN quality detection method, system and domain name server
US20080301229A1 (en) Client device, communication method and computer readable medium
CN113839938B (en) Method and device for detecting domain name takeover vulnerability
CN115665086A (en) Domain name resolution method and device based on network management equipment and electronic equipment
CN114374669A (en) VPN client proxy DNS analysis method and system

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