CN104079668B - A kind of DNS load balancing adjusting method and system - Google Patents
A kind of DNS load balancing adjusting method and system Download PDFInfo
- Publication number
- CN104079668B CN104079668B CN201410348004.9A CN201410348004A CN104079668B CN 104079668 B CN104079668 B CN 104079668B CN 201410348004 A CN201410348004 A CN 201410348004A CN 104079668 B CN104079668 B CN 104079668B
- Authority
- CN
- China
- Prior art keywords
- load balancing
- subsystem
- server
- request
- group policy
- 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
Abstract
A kind of DNS load balancing adjusting method, comprising: step S1000, load balancing subsystem receive request, and response server is determined in server zone subsystem；Step S2000, the response server of the server zone subsystem parse request；The response server of step S3000, the server zone subsystem send parsing result.The present invention can promote the ability that DNS system is responsible for balance dispatching.
Description
Technical field
The present invention relates to a kind of DNS load balancing adjusting method and systems.
Background technique
In IP (Internet Protocol, Internet protocol) network, domain name system (Domain Name System,
DNS) be internet most critical one of infrastructure service, for numerous network applications provide essence support, major function be by
The domain name (Domain Name) for being easy to people's memory is converted with the identifiable IP address of network.Between domain name and IP address
Conversion is known as domain name mapping, and the network host for executing domain name mapping is properly termed as dns server.Pass through domain name system DNS service
The query service of device can find the entrance of required website or resource, and then access to website or resource.
The domain name for facilitating user to remember that DNS can input user is converted into the IP address for the server to be accessed,
Since the performance that the quantity difference DNS system of user needs is different, in the extra high DNS system of performance requirement, need to make
It uses for DNS equipment load balance technology, i.e., more dns servers is formed into a DNS collection by certain technological means
Group promotes the performance of DNS system with this.
The DNS centralization of state power means of mainstream mainly have following 2 kinds at present.
ANYCAST cluster: ANYCAST carries out cluster using the means of network layer, by installing routing on a dns
Software, more dns server publication sames are routed to router, are formed a plurality of equivalent route on the router with this, given way
By the equal shunt volume of device, achieve the purpose that load balancing.Usually only 2 kinds of the load balancing algorithm of ANYCAST.One be by
Chartered steamer instruction is referred to by chartered steamer instruction and carries out load balancing according to the sequencing of packet.Two be by stream training in rotation, by stream training in rotation refer to by
Load balancing is carried out according to the sequencing of stream, is taken its main feature is that the same data flow can distribute to same dns server
Business.
LVS cluster: LVS cluster carries out load balancing using the means of transport layer, and basic load balance policy algorithm has:
Training in rotation scheduling, is a kind of homogeneous dispatch of standard；Weighted round robin scheduling: weighted round robin dispatching algorithm is exactly basis, cluster service
The different processing capacities of device come dispatch access request, different scheduling weights its each Cluster Server can be arranged；
To the cluster server scheduling that the cluster server processing for making those performances good is more, user accesses, those performances are poor
Weight can be set it is lower, in this way can be from the resource for making good use of server of part, scheduler may also listen for cluster simultaneously
The loading condition of server simultaneously dynamically adjusts device weight.
Min-link scheduling: referring to if dns server link number in which platform cluster is minimum, so dispatching algorithm will
Automatically connect that cluster dns server.
There are also minimum connection that other 4 algorithms are based on locality respectively, tape copies at least to be connected based on locality for it
It connects, destination address hash and source address hash.
The content that both schemes all do not go deep into application layer carries out load balancing.Do not suit DNS using itself into
The more targeted load-balancing algorithm of row.Such as following 2 kinds of scenes they be unable to satisfy.
Scene one has many platform caching DNS servers in caching DNS cluster, and the operating mode of cache server is
If existing domain name is there is no need to recurrence in caching, recurrence is needed if the domain name that caching the inside is not present, which we
It may need the same domain name requesting assignment to the same dns server, the recurrence number of entire cluster is reduced with this,
The Buffer Utilization for promoting dns server promotes resolution speed.Common DNS load balancing, can not be by same domain name
It requests to specify a server in cluster.
Scene two, when encountering the attack of DNS recurrence, it may be necessary to be effectively isolated attack, this is just needed to attack
Domain name feature carries out targeted load balancing, and 2 kinds of schemes described above do not have such algorithm yet.
Summary of the invention
The object of the present invention is to provide a kind of DNS load balancing adjusting method and systems.
The solution to the problem
To achieve the goals above, the invention provides a kind of DNS load balancing adjusting method, comprising:
Step S1000, load balancing subsystem receive request, and response server is determined in server zone subsystem；
Step S2000, the response server of the server zone subsystem parse request；
The response server of step S3000, the server zone subsystem send parsing result.
Preferably, the load balancing subsystem receives request, determines the response server in server zone subsystem,
Include:
Step S1110, the load balancing subsystem receive dns resolution request, carry out processing of unpacking to request packet；
Step S1120, the load balancing subsystem extract domain-name information；
Step S1130, the load balancing subsystem determine the response in server zone subsystem by hashing algorithm
Server；
Dns resolution request is forwarded the response server by step S1140, the load balancing subsystem.
Preferably, the load balancing subsystem receives request, determines the response server in server zone subsystem,
Include:
Step S1110, the load balancing subsystem receive dns resolution request, carry out processing of unpacking to request packet；
Step S1120, the load balancing subsystem extract domain-name information；
Step S1230, the load balancing subsystem match domain name information with default domain name list；
The dns resolution then is requested to match by step S1240 if domain name information is in the default domain name list
To the first group policy of the load balancing subsystem；
Step S1250, the load balancing subsystem, by hashing algorithm, determine clothes according to the first group policy information
The response server being engaged in device cluster subsystem；
Dns resolution request is forwarded the response server by step S1260, the load balancing subsystem.
Preferably, the load balancing subsystem receives request, determines the response server in server zone subsystem,
Include:
Step S1110, the load balancing subsystem receive dns resolution request, carry out processing of unpacking to request packet；
Step S1120, the load balancing subsystem extract domain-name information；
Step S1230, the load balancing subsystem match domain name information with default domain name list；
Step S1270, if domain name information is not in the default domain name list, then by dns resolution request
It is assigned to the second group policy of the load balancing subsystem；
Step S1280, the load balancing subsystem, by hashing algorithm, determine clothes according to the second group policy information
The response server being engaged in device cluster subsystem；
Dns resolution request is forwarded the response server by step S1290, the load balancing subsystem.
Preferably, the load balancing subsystem receives request, determines the response server in server zone subsystem,
Include:
Step S1110, the load balancing subsystem receive dns resolution request, carry out processing of unpacking to request packet；
Step S1320, the load balancing subsystem extract the source address information in the dns resolution request；
Step S1330, the load balancing subsystem match the source address information with default source address list；
Step S1340, such as source address information then request the dns resolution in the default source address list
It is matched to the first group policy of the load balancing subsystem；
Step S1350, the load balancing subsystem, by hashing algorithm, determine clothes according to the first group policy information
The response server being engaged in device cluster subsystem；
Dns resolution request is forwarded the response server by step S1360, the load balancing subsystem.
Preferably, the load balancing subsystem receives request, determines the response server in server zone subsystem,
Include:
Step S1110, the load balancing subsystem receive dns resolution request, carry out processing of unpacking to request packet；
Step S1320, the load balancing subsystem extract the source address information in the dns resolution request；
Step S1330, the load balancing subsystem match the source address information with default source address list；
Step S1370, such as source address information then ask the dns resolution not in the default source address list
Seek the second group policy for being matched to the load balancing subsystem；
Step S1380, the load balancing subsystem, by hashing algorithm, determine server according to second group policy
Response server in cluster subsystem；
Dns resolution request is forwarded the response server by step S1390, the load balancing subsystem.
The present invention also provides a kind of DNS load balancing regulating systems, comprising:
Load balancing subsystem determines response server for receiving request in following server zone subsystems；
The response server of server zone subsystem for parsing to request, and sends parsing result.
Preferably, DNS load balancing regulating system, the load balancing subsystem are also used to:
Dns resolution request is received, processing of unpacking is carried out to request packet；Extract domain-name information；By hashing algorithm, clothes are determined
The response server being engaged in device cluster subsystem；Dns resolution request is forwarded into the response server.
Preferably, DNS load balancing regulating system,
The load balancing subsystem is used for: being received dns resolution request, is carried out processing of unpacking to request packet；Extract domain name
Information；Domain name information is matched with default domain name list；By the domain name letter in the default domain name list
The dns resolution request of breath is matched to first group policy；
The load balancing subsystem is also used to: determining the service by hashing algorithm according to first group policy
Response server in device cluster subsystem；Dns resolution request is forwarded into the response server；
The load balancing subsystem is also used to: being received dns resolution request, is carried out processing of unpacking to request packet；Extract domain
Name information；Domain name information is matched with default domain name list；By the domain not in the default domain name list
The dns resolution request of name information is matched to second group policy；
The load balancing subsystem is also used to: determining the service by hashing algorithm according to second group policy
Response server in device cluster subsystem；Dns resolution request is forwarded into the response server.
Preferably, DNS load balancing regulating system,
The load balancing subsystem is used for: being received dns resolution request, is carried out processing of unpacking to request packet；Described in extraction
Source address information in dns resolution request；The source address information is matched with default source address list；It will be in default source
The dns resolution request of the source address information in address list is matched to first group policy；
The load balancing subsystem is also used to: according to first group policy, for determining service by hashing algorithm
Response server in device cluster subsystem；Dns resolution request is forwarded into the response server；
The load balancing subsystem is used for: being received dns resolution request, is carried out processing of unpacking to request packet；Described in extraction
Source address information in dns resolution request；The source address information is matched with default source address list；It will be not default
The dns resolution request of the source address information in source address list is matched to second group policy；
The load balancing subsystem is also used to: according to second group policy, for determining service by hashing algorithm
Response server in device cluster subsystem；Dns resolution request is forwarded into the response server.
Beneficial effect
1, the recurrence number for reducing entire cluster, the Buffer Utilization for promoting dns server promote resolution speed.
2, the compressive property that server faces recurrence attack is enhanced.
3, effective distribution server cluster, provides dns resolution efficiency.
Detailed description of the invention
Fig. 1 is DNS load balancing adjusting method flow diagram；
Fig. 2 is the flow diagram of one embodiment of the invention；
Fig. 3 is the flow diagram of one embodiment of the invention；
Fig. 4 is the example schematic diagram of one embodiment of the invention；
Fig. 5 is the flow diagram of another embodiment of the present invention；
Fig. 6 is the flow diagram of another embodiment of the present invention；
Fig. 7 is the flow diagram of another embodiment of the present invention；
Fig. 8 is the example schematic diagram of another embodiment of the present invention；
Fig. 9 is the flow diagram of further embodiment of this invention；
Figure 10 is the flow diagram of further embodiment of this invention；
Figure 11 is the flow diagram of further embodiment of this invention；
Figure 12 is the flow diagram of further embodiment of this invention.
Specific embodiment
The technical solution in the invention embodiment is clearly and completely described below, it is clear that described reality
Applying example only is the invention section Example, instead of all the embodiments.Based on the embodiment in the invention, ability
Domain those of ordinary skill every other embodiment obtained without creative efforts, belongs to wound of the present invention
Make the range of protection.
As shown in Figure 1, a kind of DNS load balancing adjusting method, comprising:
Step S1000, load balancing subsystem receive request, and response server is determined in server zone subsystem；
Step S2000, the response server of the server zone subsystem parse request；
The response server of step S3000, the server zone subsystem send parsing result.
Preferably, as shown in Fig. 2, the step S1000, load balancing subsystem receive request, determine cluster of servers
Response server in subsystem, comprising:
Step S1110, the load balancing subsystem receive dns resolution request, carry out processing of unpacking to request packet；
Step S1120, the load balancing subsystem extract domain-name information；
Step S1130, the load balancing subsystem determine the response in server zone subsystem by hashing algorithm
Server；
Dns resolution request is forwarded the response server by step S1140, the load balancing subsystem.
The above method, mainly uses domain name hash dispatching algorithm (Domain Hashing Scheduling), and domain name dissipates
Column scheduling (Domain Hashing Scheduling) algorithm is the load balancing for domain name, is a kind of static mappings algorithm,
All analysis requests of certain domain name are mapped to a server by a hash function.
As shown in figure 3, domain name hashes dispatching algorithm by the domain name in application layer extraction analysis request, which is done scattered
Column operations is found out corresponding server for operation values as hashed key from the hash table of static allocation, and will next be owned
The analysis request of the domain name is all sent to the server.Assuming that the TTL=3600 second (1 hour) of certain domain name on the server,
Dispatching algorithm is hashed using domain name, the server for parsing the domain name only needs upward recurrence 24 times daily, greatly enhances clothes
Business device faces the compressive property of recurrence attack.
It proposes or issues request (for example, DNC analysis request), can be considered client, user, client layer；Load balancing
Subsystem may be load balancing layer, load balancing；Server zone subsystem may be server cluster layer, Ke Yiyou
Server group A, server group B to server group N form, can also by dns server 1, dns server 2, dns server 3 to
Dns server N composition.One server group, can be by dns server 1, dns server 2, dns server 3 to dns server
N composition.
Wherein typical process are as follows:
1, client layer issues DNS request；
2, load balancing layer unpacks processing to request packet；
3, the domain name for needing to parse is extracted after unpacking；
4, operation values are shown as hash operations to the domain name；
5, specified server is found according to operation values；
6, DNS request is given to the server；
7, server process analysis request；
8, parsing result is returned to user；
9, client obtains parsing result.
As shown in figure 4, an example of the above method are as follows:
(1) dns resolution that user issues that domain name is www.abc.com is requested.
(2) load balancer does packet processing to the DNS request, and module of unpacking extracts domain name from the DNS request packet
Www.abc.com does hash operations to www.abc.com and obtains operation values 2, finds out corresponding DNS in static hash table
The DNS request is handed to dns server 2 and handled by server 2, load balancer.
(3) dns server 2 receives and result is returned to user terminal after the completion of the dns resolution request is handled.
Preferably, as shown in figure 5, the step S1000, load balancing subsystem receive request, determine cluster of servers
Response server in subsystem, comprising:
Step S1110, the load balancing subsystem receive dns resolution request, carry out processing of unpacking to request packet；
Step S1120, the load balancing subsystem extract domain-name information；
Step S1230, the load balancing subsystem match domain name information with default domain name list；
The dns resolution then is requested to match by step S1240 if domain name information is in the default domain name list
To the first group policy of the load balancing subsystem；
Step S1250, the load balancing subsystem are determined according to the first group policy information by hashing algorithm
Response server in server zone subsystem；
Dns resolution request is forwarded the response server by step S1260, the load balancing subsystem.
Preferably, as shown in fig. 6, the step S1000, load balancing subsystem receive request, determine cluster of servers
Response server in subsystem, comprising:
Step S1110, the load balancing subsystem receive dns resolution request, carry out processing of unpacking to request packet；
Step S1120, the load balancing subsystem extract domain-name information；
Step S1230, the load balancing subsystem match domain name information with default domain name list；
Step S1270, if domain name information is not in the default domain name list, then by dns resolution request
It is assigned to the second group policy of the load balancing subsystem；
Step S1280, the load balancing subsystem are determined according to the second group policy information by hashing algorithm
Response server in server zone subsystem；
Dns resolution request is forwarded the response server by step S1290, the load balancing subsystem.
Above-mentioned the first group policy, the second group policy, specifically: the first group policy and the second group policy provide different dissipate
Column algorithm, the first group policy can only will request assignment to several respective servers defined in the first group policy, and second group
Strategy can only will request assignment to several respective servers defined in the second group policy.So every group policy includes one
Specific hashing algorithm and a specific response server group.
The above method mainly uses domain name isolation hash dispatching algorithm (Domain Isolation Hashing
Scheduling).As shown in fig. 7, domain name isolation hash scheduling (Domain Isolation Hashing Scheduling) is calculated
Method is on the basis of the preset domain name list of application layer, and the domain name of list match does hash scheduling in server group A, and list is not
The domain name matched does hash scheduling in server group B.Administrator can in real time make an amendment domain name list, will according to DNS log
The big domain name of parsing amount is not added to domain name list in lists, reduces the load of server group B.
Typical operation flow are as follows:
1, client layer issues DNS request；
2, load balancing layer unpacks processing to request packet；
3, the domain name for needing to parse is extracted after unpacking；
4, by the domain name and domain name list match；
If 5, the domain name is in domain name list, the DNS request of the domain name is matched and gives server group A, which is made
Hash operations obtain operation values；
If 6, the domain name is not in domain name list, the DNS request of the domain name is matched and gives server group B, to the domain name
Operation values are obtained as hash operations.
7, the server in specified server group is found according to operation values；
8, DNS request is given to the server；
9, server process analysis request；
10, parsing result is returned to client layer；
11, client obtains parsing result.
As shown in figure 8, an example of the above method are as follows:
(1) dns resolution that user issues that domain name is www.abc.com is requested.
(2) load balancer does packet processing to the DNS request, and module of unpacking extracts domain name from the DNS request packet
Www.abc.com, and the domain name is matched not in domain name list and gives server group B, done to www.abc.com scattered by the domain name
Column operations obtains operation values 2, the dns server 2 being matched in server group B in the corresponding static hash table of server group B,
The DNS request is handed to the dns server 2 in server group B and handled by load balancer.
(3) dns server 2 in server group B receives and result is returned to user after the completion of the dns resolution request is handled
Terminal.
Preferably, as shown in figure 9, the step S1000, load balancing subsystem receive request, determine cluster of servers
Response server in subsystem, comprising:
Step S1110, the load balancing subsystem receive dns resolution request, carry out processing of unpacking to request packet；
Step S1320, the load balancing subsystem extract the source address information in the dns resolution request；
Step S1330, the load balancing subsystem match the source address information with default source address list；
Step S1340, such as source address information then request the dns resolution in the default source address list
It is matched to the first group policy of the load balancing subsystem；
Step S1350, the load balancing subsystem are determined according to the first group policy information by hashing algorithm
Response server in server zone subsystem；
Dns resolution request is forwarded the response server by step S1360, the load balancing subsystem.
Preferably, as shown in Figure 10, the step S1000, load balancing subsystem receive request, determine cluster of servers
Response server in subsystem, comprising:
Step S1110, the load balancing subsystem receive dns resolution request, carry out processing of unpacking to request packet；
Step S1320, the load balancing subsystem extract the source address information in the dns resolution request；
Step S1330, the load balancing subsystem match the source address information with default source address list；
Step S1370, such as source address information then ask the dns resolution not in the default source address list
Seek the second group policy for being matched to the load balancing subsystem；
Step S1380, the load balancing subsystem are determined according to the second group policy information by hashing algorithm
Response server in server zone subsystem；
Dns resolution request is forwarded the response server by step S1390, the load balancing subsystem.
Above-mentioned the first group policy, the second group policy, specifically: the first group policy and the second group policy provide different dissipate
Column algorithm, the first group policy can only will request assignment to several respective servers defined in the first group policy, and second group
Strategy can only will request assignment to several respective servers defined in the second group policy.So every group policy includes one
Specific hashing algorithm and a specific response server group.
The above method mainly uses source address isolation hash dispatching algorithm (Source Isolation Hashing
Scheduling).As shown in figure 11, source address isolation hash scheduling (Source Isolation Hashing
Scheduling) algorithm is the load balancing for source IP address, it is also a kind of static mappings algorithm, but it is one kind to answer
On the basis of the preset source destination address list of layer, the request of the source IP address of list match is done hash in server group A and is adjusted
Hash scheduling is done in degree, the request of the unmatched source IP address of list in server group B.
Typical operation flow are as follows:
1, client layer issues DNS request；
2, load balancing layer extracts the source IP address of request；
3, by the source IP address and source IP list match；
If 4, the IP address is in source IP list, the DNS request of the source IP address is matched and gives server group A, to this
Source IP address obtains operation values as hash operations；
If 5, the IP address is not in source IP list, the DNS request of the source IP address is matched and gives server group B, it is right
The source IP address obtains operation values as hash operations.
6, the server in specified server group is found according to operation values；
7, DNS request is given to the server；
8, server process analysis request；
9, parsing result is returned to client layer；
10, client obtains parsing result.
As shown in figure 12, an example of the above method are as follows:
(1) user that source IP is 211.142.142.142 issues the dns resolution request that domain name is www.abc.com.
(2) load balancer extraction source IP is 211.142.142.142, and discovery 211.142.142.142 is not arranged in source IP
The domain name is matched and gives server group B by table, is done hash operations to the source IP and is obtained operation values 2, corresponding static in server group B
Hash table in be matched to dns server 2 in server group B, which is handed to server group B by load balancer
In dns server 2 handle.
(3) dns server 2 in server group B receives and result is returned to user after the completion of the dns resolution request is handled
Terminal.
The present invention also provides a kind of DNS load balancing regulating systems, comprising:
Load balancing subsystem determines response server for receiving request in following server zone subsystems；
The response server of server zone subsystem for parsing to request, and sends parsing result.
Preferably, DNS load balancing regulating system, the load balancing subsystem are also used to:
Dns resolution request is received, processing of unpacking is carried out to request packet；Extract domain-name information；By hashing algorithm, clothes are determined
The response server being engaged in device cluster subsystem；Dns resolution request is forwarded into the response server.
Preferably, DNS load balancing regulating system,
The load balancing subsystem is used for: being received dns resolution request, is carried out processing of unpacking to request packet；Extract domain name
Information；Domain name information is matched with default domain name list；By the domain name letter in the default domain name list
The dns resolution request of breath is matched to first group policy；
The load balancing subsystem is used for: determining the server by hashing algorithm according to first group policy
Response server in cluster subsystem；Dns resolution request is forwarded into the response server；
The load balancing subsystem is also used to: being received dns resolution request, is carried out processing of unpacking to request packet；Extract domain
Name information；Domain name information is matched with default domain name list；By the domain not in the default domain name list
The dns resolution request of name information is matched to second group policy；
The load balancing subsystem is used for: determining the server by hashing algorithm according to second group policy
Response server in cluster subsystem；Dns resolution request is forwarded into the response server.
Preferably, DNS load balancing regulating system,
The load balancing subsystem is used for: being received dns resolution request, is carried out processing of unpacking to request packet；Described in extraction
Source address information in dns resolution request；The source address information is matched with default source address list；It will be in default source
The dns resolution request of the source address information in address list is matched to first group policy；
The load balancing subsystem is used for: according to first group policy, for determining server by hashing algorithm
Response server in cluster subsystem；Dns resolution request is forwarded into the response server；
The load balancing subsystem is used for: being received dns resolution request, is carried out processing of unpacking to request packet；Described in extraction
Source address information in dns resolution request；The source address information is matched with default source address list；It will be not default
The dns resolution request of the source address information in source address list is matched to second group policy；
The load balancing subsystem is used for: according to second group policy, for determining server by hashing algorithm
Response server in cluster subsystem；Dns resolution request is forwarded into the response server.
The above, the only specific embodiment of the invention, but the protection scope of the invention does not limit to
In this, anyone skilled in the art can readily occur in variation in the technical scope that the invention discloses
Or replacement, it should all cover within the protection scope of the invention.Therefore, the protection scope of the invention is answered described with power
Subject to the protection scope that benefit requires.
Claims (2)
1. a kind of DNS load balancing adjusting method characterized by comprising
Step S1000, load balancing subsystem receive request, and response server is determined in server zone subsystem；
Step S2000, the response server of the server zone subsystem parse request；
The response server of step S3000, the server zone subsystem send parsing result；
The load balancing subsystem receives request, determines the response server in server zone subsystem, comprising:
Step S1110, the load balancing subsystem receive dns resolution request, carry out processing of unpacking to request packet；
Step S1120, the load balancing subsystem extract domain-name information or extract the source address letter in the dns resolution request
Breath；
Step S1130, the load balancing subsystem determine cluster of servers by the hashing algorithm for domain name information
Response server in subsystem；
Step S1230, the load balancing subsystem match domain name information with default domain name list；
Dns resolution request is then matched to institute if domain name information is in the default domain name list by step S1240
State the first group policy of load balancing subsystem；
Step S1250, the load balancing subsystem is according to the first group policy information, by for domain name information
Hashing algorithm determines the response server in server zone subsystem；
Dns resolution request is then matched to by step S1270 if domain name information is not in the default domain name list
Second group policy of the load balancing subsystem；
Step S1280, the load balancing subsystem is according to the second group policy information, by for domain name information
Hashing algorithm determines the response server in server zone subsystem；Then step S1400 is gone to；
Step S1330, the load balancing subsystem match the source address information with default source address list；
The dns resolution then is requested to match by step S1340, such as source address information in the default source address list
To the first group policy of the load balancing subsystem；
Step S1350, the load balancing subsystem are calculated according to the first group policy information by the hash for source address
Method determines the response server in server zone subsystem；Then step S1400 is gone to；
Step S1370, such as source address information is not in the default source address list, then by dns resolution request
It is assigned to the second group policy of the load balancing subsystem；
Step S1380, the load balancing subsystem are calculated according to the second group policy information by the hash for source address
Method determines the response server in server zone subsystem；Then step S1400 is gone to；
Dns resolution request is forwarded to the response server by step S1400, the load balancing subsystem；
Wherein, first group policy and the second group policy specifically: first group policy and second group policy mention
For different hashing algorithms, first group policy can only will request assignment to several defined in first group policy
Response server, second group policy can only will request assignment to several responses defined in second group policy and take
Business device, every group policy include a specific hashing algorithm and a specific response server group.
2. a kind of DNS load balancing regulating system characterized by comprising
Load balancing subsystem determines response server for receiving request in following server zone subsystems；
The response server of server zone subsystem for parsing to request, and sends parsing result；
The load balancing subsystem is used for: being received dns resolution request, is carried out processing of unpacking to request packet；Extract the DNS solution
Source address information in analysis request；The source address information is matched with default source address list；It will be in default source address
The dns resolution request of the source address information in list is matched to the first group policy；
The load balancing subsystem is also used to: according to first group policy, for determining server zone by hashing algorithm
Response server in subsystem；Dns resolution request is forwarded into the response server；
The load balancing subsystem is used for: being received dns resolution request, is carried out processing of unpacking to request packet；Extract the DNS solution
Source address information in analysis request；The source address information is matched with default source address list；It will not in default source
The dns resolution request of the source address information in the list of location is matched to the second group policy；
The load balancing subsystem is also used to: according to second group policy, for determining server zone by hashing algorithm
Response server in subsystem；Dns resolution request is forwarded into the response server；
Wherein, first group policy and the second group policy specifically: first group policy and second group policy mention
For different hashing algorithms, first group policy can only will request assignment to several defined in first group policy
Response server, second group policy can only will request assignment to several responses defined in second group policy and take
Business device, every group policy include a specific hashing algorithm and a specific response server group.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410348004.9A CN104079668B (en) | 2014-07-21 | 2014-07-21 | A kind of DNS load balancing adjusting method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410348004.9A CN104079668B (en) | 2014-07-21 | 2014-07-21 | A kind of DNS load balancing adjusting method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104079668A CN104079668A (en) | 2014-10-01 |
| CN104079668B true CN104079668B (en) | 2018-12-28 |
Family
ID=51600708
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410348004.9A Active CN104079668B (en) | 2014-07-21 | 2014-07-21 | A kind of DNS load balancing adjusting method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104079668B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104283804B (en) * | 2014-10-27 | 2018-05-11 | 新华三技术有限公司 | A kind of balancing link load method and apparatus |
| CN105991347A (en) * | 2015-04-30 | 2016-10-05 | 杭州迪普科技有限公司 | Redirection method of DNS request message and device |
| US10122647B2 (en) * | 2016-06-20 | 2018-11-06 | Microsoft Technology Licensing, Llc | Low-redistribution load balancing |
| CN107070983A (en) * | 2017-01-23 | 2017-08-18 | 天地融科技股份有限公司 | A kind of load-balancing method, equipment and system forwarded based on address |
| CN107967650A (en) * | 2017-11-08 | 2018-04-27 | 中国银行股份有限公司 | A kind of batch accounting data processing method and processing device of core banking system |
| CN110933145A (en) * | 2019-11-14 | 2020-03-27 | 光通天下网络科技股份有限公司 | Remote scheduling method, device, equipment and medium |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102231766B (en) * | 2011-07-28 | 2013-10-09 | 北京蓝汛通信技术有限责任公司 | Method and system for analyzing and verifying domain name |
| CN103685583B (en) * | 2012-09-05 | 2018-02-23 | 阿里巴巴集团控股有限公司 | A kind of method and system of domain name mapping |
| CN103051740B (en) * | 2012-12-13 | 2016-04-20 | 上海牙木通讯技术有限公司 | Domain name analytic method, dns server and domain name analysis system |
| CN103685056A (en) * | 2014-01-14 | 2014-03-26 | 互联网域名系统北京市工程研究中心有限公司 | Load balancing method and load balancing system |
-
2014
- 2014-07-21 CN CN201410348004.9A patent/CN104079668B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN104079668A (en) | 2014-10-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104079668B (en) | A kind of DNS load balancing adjusting method and system | |
| KR102138619B1 (en) | Message clustering method and load balancer based on server cluster | |
| US9209990B1 (en) | Method and system for scaling network traffic managers | |
| EP3404878B1 (en) | Virtual network apparatus, and related method | |
| KR102146476B1 (en) | Method and system for load balancing anycast data traffic | |
| US8898331B2 (en) | Method, network and computer program for processing a content request | |
| US9979656B2 (en) | Methods, systems, and computer readable media for implementing load balancer traffic policies | |
| JP2003281109A (en) | Load distribution method | |
| US20100125656A1 (en) | System and Method for Request Routing Optimization | |
| US20160261505A1 (en) | Localized service chaining in nfv clouds | |
| CN110086886B (en) | Dynamic session holding method and device | |
| JP2005182641A (en) | Dynamic load distribution system and dynamic load distribution method | |
| Xu et al. | A modified round-robin load-balancing algorithm for cluster-based web servers | |
| CN112839081A (en) | Load balancing method of cloud cluster | |
| EP3166262B1 (en) | Control device, control system, control method, and control program | |
| WO2017097092A1 (en) | Method and system for processing cache cluster service | |
| Vaidya et al. | A single system image server cluster using duplicated MAC and IP addresses | |
| CN113014611A (en) | Load balancing method and related equipment | |
| US20160323371A1 (en) | Methods and apparatus for load balancing in a network | |
| Ke et al. | Load balancing using P4 in software-defined networks | |
| CN107508760B (en) | Method for load distribution based on line source IP | |
| Mangayarkarasi et al. | Highly scalable and load balanced web server on AWS cloud | |
| CN113271260A (en) | Load balancing processing method, device, equipment and storage medium | |
| TW201832519A (en) | Flow entry management system applied to SDN network based upon user grouping and method thereof prevent virtual machine from generating network delay and packet loss due to overloading through grouping distributed mechanism having load balancing | |
| JP2011239082A (en) | Communication apparatus and address conversion method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20181102 Address after: No. 159 Tian'an Zhigu Exhibition Service Center, No. 18 Chuangxing Avenue, Science and Technology Innovation Park, Qingcheng High-tech Industrial Development Zone, Qingyuan City, Guangdong Province Applicant after: Qingyuan starter Intelligent Technology Co., Ltd. Address before: 100080 Beijing Haidian District Suzhou Street 55, 3 tier 01-A340 Applicant before: Beijing Kuai Yibo Science and Technology Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |