CN110380969A - A kind of traffic scheduling method and system based on domain name - Google Patents
A kind of traffic scheduling method and system based on domain name Download PDFInfo
- Publication number
- CN110380969A CN110380969A CN201910632026.0A CN201910632026A CN110380969A CN 110380969 A CN110380969 A CN 110380969A CN 201910632026 A CN201910632026 A CN 201910632026A CN 110380969 A CN110380969 A CN 110380969A
- Authority
- CN
- China
- Prior art keywords
- domain name
- request message
- parsing
- distal end
- flow table
- 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.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
- H04L45/745—Address table lookup; Address filtering
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/12—Avoiding congestion; Recovering from congestion
- H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
-
- 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/50—Network services
- H04L67/56—Provisioning of proxy services
-
- 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/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The present invention provides a kind of application traffic dispatching method based on domain name, is related to data communication technology field, comprising: the network equipment kidnaps the domain name mapping request message that client issues, and forwards it in domain name resolution agent server;Domain name resolution agent server carries out the parsing of domain name according to domain name mapping request message, generates corresponding specific message according to parsing result and is forwarded to interchanger;The study flow table that interchanger is pre-generated and issued according to controller learns specific message to obtain corresponding forwarding flow table, and is accordingly forwarded the corresponding IP address of domain name according to forwarding flow table.The present invention avoids controller from becoming name server, while frequent domain name mapping being avoided to request the influence to controller, keeps the load pressure that controller is effectively reduced while the control flexibility of controller.
Description
Technical field
The present invention relates to data communication technology field more particularly to a kind of traffic scheduling methods and system based on domain name.
Background technique
With the continuous development of internet, diversity is presented in business.Internet service proposes internet higher and higher
Transmission quality requirements, including big bandwidth, safety guarantee, flexible dispatching, intelligent management etc..
Software defined network (Software Defined Network, SDN) is used as a kind of new network of Emulex network innovation framework, is
A kind of implementation of network virtualization, core concept are the couplings that the network equipment is released by OpenFlow, realize control
The separation in preparative layer face and data plane becomes network more as communication pipe to realize the flexible control of network flow
Intelligence.Core of the SDN controller as software defined network is responsible for the maintenance of whole network, the collection of switch status, routing
Calculating and flow entry management, instruct interchanger to forward data packet by flow entry, realize transmission to data flow in network
It is controlled.
Domain name system (Domain Name System, DNS) is a kind of skill that host name and domain name are converted to IP address
Art.Domain name mapping is exactly conversion process of the domain name to IP address, and domain name client-side sends to name server end a first
Query message includes the fields such as the host name to be accessed in the query message;Domain name client-side subsequently receives name server
The reply message sent is held, includes the corresponding IP address of the host name to be accessed in the reply message.
Due to OpenFlow interchanger can not Direct Recognition domain name so that based on domain name application traffic scheduling can not use domain
Name directly describes, and needs to parse domain name before to application flow scheduling.In the prior art, it is handed over to solve OpenFlow
The matching changed planes to domain name, it usually needs the DNS message of OpenFlow interchanger is reported into SDN controller, by SDN controller
It is interacted with dns server, and actual operation flow table is formed according to parsing result and is updated onto OpenFlow interchanger, realize base
It is dispatched in the service traffics of domain name.But in the technical solution, SDN controller has essentially become a dns server, simultaneously also
The various processing for the flow table to be undertaken and TCP connection etc. is initiated to the IP address, so that the load of SDN controller is very big.
Summary of the invention
Aiming at the problems existing in the prior art, the present invention provides a kind of traffic scheduling method based on domain name, is applied to
In software defined network, the software defined network includes a controller and the network equipment that connect with the controller,
The network equipment includes an interchanger and the domain name resolution agent server that connect with the interchanger;
The external client of software defined network, the client connect the network equipment;
The traffic scheduling method specifically includes the following steps:
Step S1, the network equipment kidnap the domain name mapping request message that the client issues, and by domain name
Analysis request message is forwarded in domain name parsing proxy server;
Step S2, domain name parse the parsing that proxy server carries out domain name according to domain name analysis request message,
Then output parsing result;
Step S3, domain name parse proxy server and generate corresponding specific message according to the parsing result, and will
The specific message is forwarded to the interchanger;
It include domain name and the institute corresponding with domain name in domain name analysis request message in the specific message
State the IP address in parsing result;
Step S4, the study flow table that the interchanger is pre-generated and issued according to the controller, to the special report
Text is learnt to obtain corresponding forwarding flow table;
Step S5, the interchanger are accordingly turned the corresponding IP address of domain name according to the forwarding flow table
Hair.
Preferably, the step S1 is specifically included:
Step S11, it includes preset in the initial forwarding flow table that the controller pre-generated one is initial, which to forward flow table,
The port numbers of domain name mapping;
Step S12, the network equipment hit corresponding in advance for the client sending according to the initial forwarding flow table
If domain name parsing port numbers domain name mapping request message;
Step S13, the network equipment kidnap domain name analysis request message.
Preferably, the port numbers of preset domain name parsing are UDP transport protocol in the initial forwarding flow table
53 ports of middle agreement.
Preferably, the process for presetting local cache database including one, described in local cache database connection
Domain name resolution agent server;
The process for presetting local cache database specifically includes:
Step A1, the network equipment are issued according to the domain name analysis request message of abduction in the controller in advance
Domain name concern list in inquired, with judge the domain name in domain name analysis request message whether there is in domain name
It pays close attention in list:
If so, domain name request message to be remotely sent to one first distal end connecting with the network apparatus remote
It is parsed in domain name resolution server, is subsequently diverted to step A2;
If it is not, domain name request message to be then remotely sent to one second distal end connecting with the network apparatus remote
It is parsed in domain name resolution server, is subsequently diverted to step A3;
Step A2, domain name parsing proxy server obtain the first of first distal end domain name resolution server feedback
Domain name mapping data, and it is pre-generated described according to domain name parsing data and corresponding domain name analysis request message
The first standardized domain name in local cache database parses information;
It include the first parsing result of domain name and corresponding domain name in the first standardized domain name parsing information;
Step A3, domain name parsing proxy server obtain the second of second distal end domain name resolution server feedback
Domain name mapping data, and it is pre-generated described according to domain name parsing data and corresponding domain name analysis request message
The second standardized domain name in local cache database parses information;
It include the second parsing result of domain name and corresponding domain name in the second standardized domain name parsing information;
Then the step S2 is specifically included:
Step S21 is slow in the local after domain name parses proxy server reception domain name analysis request message
Deposit data is inquired in library, to judge that the domain name in domain name analysis request message whether there is in the local cache number
According in library:
If so, exporting corresponding parsing result, it is subsequently diverted to the step S3;
If it is not, then turning to step S22;
Step S22, domain name parses proxy server and is inquired in domain name concern list, described in judgement
Domain name in domain name mapping request message whether there is in domain name concern list:
If so, turning to step S23;
If it is not, then turning to step S24;
It includes several concern domain names in list that domain name, which is paid close attention to,;
Step S23, domain name parses proxy server and accesses first distal end domain name resolution server, to request
It states the first distal end domain name resolution server to parse the domain name in domain name analysis request message, and exports described first
First parsing result of distal end domain name resolution server feedback, is subsequently diverted to step S3;
Step S24, domain name parses proxy server and accesses second distal end domain name resolution server, to request
It states the second distal end domain name resolution server to parse the domain name in domain name analysis request message, and exports described second
Second parsing result of distal end domain name resolution server feedback, is subsequently diverted to step S3;
Each domain name parsing proxy server obtains described the of first distal end domain name resolution server feedback
When one parsing result, domain name resolution server is according to first parsing result and corresponding domain name analysis request report
Domain name in text updates the local cache database;And
Each domain name parsing proxy server obtains described the of second distal end domain name resolution server feedback
When two parsing results, domain name parses proxy server and is asked according to second parsing result and the parsing of corresponding domain name
The domain name in message is asked to update the local cache database.
Preferably, further include the process being updated to domain name concern list, specifically include:
Step B1, the controller receive external modification information, and according to the modification information to domain name concern
List is updated;
Updated domain name is paid close attention to list real time down to the network equipment by step B2, the controller.
Preferably, in the step S4, the modification information includes the change to the concern domain name, and/or addition is closed
Domain name is infused, and/or deletes the concern domain name.
Preferably, the interchanger is Openflow interchanger.
A kind of flow scheduling system based on domain name, using the flow scheduling side based on domain name described in any of the above one
Method specifically includes:
The network equipment, the network equipment include:
Interchanger, the interchanger include:
Hijacking data module, for kidnapping the domain name mapping request message of the network interface sending of the client and exporting;
Domain name resolution agent server connects the interchanger, for carrying out domain according to domain name analysis request message
The parsing of name, and corresponding specific message is generated according to parsing result and is exported;
It include domain name and the institute corresponding with domain name in domain name analysis request message in the specific message
State the IP address in parsing result;
The interchanger further include:
Study module, for being learnt to obtain to the specific message corresponding according to pre-generated study flow table
Forward flow table;
Forwarding module connects the study module, for according to the forwarding flow table by the corresponding IP of domain name
Address is accordingly forwarded.
Controller establishes connection by Openflow agreement and the network equipment, for generating the study flow table, first
The forwarding flow table that begins and domain name pay close attention to list, and are issued to the network equipment.
Preferably, the hijacking data module specifically includes:
Data storage cell, for saving the initial forwarding flow table of the controller pre-generated one, the initial forwarding flow
It include the port numbers of preset domain name mapping in table;
Data hit unit connects the data storage cell, for hitting the visitor according to the initial forwarding flow table
What family end issued corresponds to the domain name mapping request message of the port numbers of preset domain name parsing;
Hijacking data unit connects the data hit unit, for kidnapping domain name analysis request message.
Preferably, domain name parsing proxy server specifically includes:
First memory module, for saving pre-generated local cache database;
Second memory module, for saving, the controller is pre-generated and the domain name issued pays close attention to list;
First parsing module connects first memory module, is used for after receiving domain name analysis request message, in
It is inquired in the local cache database, and is generated accordingly when inquiring the domain name in domain name analysis request message
Parsing result and output;And
Corresponding first query result is generated when not inquiring the domain name in domain name analysis request message and is exported;
First enquiry module is separately connected first parsing module and second memory module, for according to
First query result is inquired in domain name concern list, and is inquiring the domain in domain name analysis request message
It generates corresponding second query result when name and exports;And
Corresponding third query result is generated when not inquiring the domain name in domain name analysis request message and is exported;
It includes several concern domain names in list that domain name, which is paid close attention to,;
Second parsing module connects first enquiry module, for according to second query result access with it is described
One first distal end domain name resolution server of network apparatus remote connection, to request first distal end domain name resolution server pair
Domain name in domain name analysis request message is parsed, and exports the of first distal end domain name resolution server feedback
One parsing result;
Third parsing module connects first enquiry module, for according to third query result access with it is described
One second distal end domain name resolution server of network apparatus remote connection, to request the distal end domain name resolution server to described
Domain name in domain name mapping request message is parsed, and exports the second solution of second distal end domain name resolution server feedback
Analyse result;
Each domain name parsing proxy server obtains described the of first distal end domain name resolution server feedback
When one parsing result, domain name parses proxy server and is asked according to first parsing result and the parsing of corresponding domain name
The domain name in message is asked to update the local cache database;And
Each domain name parsing proxy server obtains described the of second distal end domain name resolution server feedback
When two parsing results, domain name parses proxy server and is asked according to second parsing result and the parsing of corresponding domain name
The domain name in message is asked to update the local cache database.
Above-mentioned technical proposal have the following advantages that or the utility model has the advantages that
1) redirection function for utilizing flow table, translates domain names into request message and is directed to local domain name resolution agent service
In device, so that the resolving of domain name mapping request message carries out in local domain name resolution agent server, control is avoided
Device processed becomes name server, while avoiding frequent domain name mapping request influence caused by controller, maintains control
The load pressure of controller is effectively reduced while the control flexibility of device;
2) learning functionality for utilizing flow table, it is special according to being sent in the local domain name resolution agent server received
Message generates corresponding forwarding flow table, realizes OpenFlow interchanger to the high-efficiency learning of domain name mapping result.
Detailed description of the invention
Fig. 1 is a kind of flow diagram of the traffic scheduling method based on domain name in preferred embodiment of the invention;
Fig. 2 is the flow diagram of the processing method of domain name mapping request message in preferred embodiment of the invention;
Fig. 3 is to preset the process flow schematic diagram of local cache database in preferred embodiment of the invention;
Fig. 4 is the method flow signal that domain name resolution agent server is parsed in preferred embodiment of the invention
Figure;
Fig. 5 is in preferred embodiment of the invention, and domain name pays close attention to the update method flow diagram of list;
Fig. 6 is a kind of structural schematic diagram of the flow scheduling system based on domain name in preferred embodiment of the invention.
Specific embodiment
The present invention is described in detail with specific embodiment below in conjunction with the accompanying drawings.The present invention is not limited to the embodiment party
Formula, as long as meeting purport of the invention, other embodiments also may belong to scope of the invention.
In preferred embodiment of the invention, it is based on the above-mentioned problems in the prior art, is now provided a kind of based on domain
The traffic scheduling method of name is applied in software defined network, and software defined network includes a controller and connects with controller
The network equipment connect, the network equipment include an interchanger and the domain name resolution agent server connecting with interchanger;
The external client of software defined network, client connect the network equipment;
As shown in Figure 1, traffic scheduling method specifically includes the following steps:
Step S1, the network equipment kidnaps the domain name mapping request message that client issues, and translates domain names into request message
It is forwarded in domain name resolution agent server;
Step S2, domain name resolution agent server carry out the parsing of domain name according to domain name mapping request message, then export
Parsing result;
Step S3, domain name resolution agent server generate corresponding specific message according to parsing result, and by specific message
It is forwarded to interchanger;
It include the IP in the domain name and parsing result corresponding with domain name in domain name mapping request message in specific message
Address;
Step S4, the study flow table that interchanger is pre-generated and issued according to the controller, to the specific message into
Row study obtains corresponding forwarding flow table;
Step S5, interchanger are accordingly forwarded the corresponding IP address of domain name according to forwarding flow table.
Specifically, in the present embodiment, the above-mentioned network equipment is SDN equipment, and the SDN equipment is pre- according to above controller first
The port numbers of preset domain name mapping in the initial forwarding flow table first configured kidnap the domain name mapping request message that client issues,
Request message is translated domain names into be forwarded in local domain name resolution agent server.A preferred embodiment of the invention
In, the initial port numbers for forwarding preset domain name mapping in flow table are 53 ports arranged in UDP transport protocol, then the network equipment
All domain name mapping request reports for 53 ports arranged in UDP transport protocol are hit by the port numbers of preset domain name mapping
In other words text is configured with forward rule corresponding with 53 ports arranged in UDP transport protocol in initially forwarding flow table, only
Further forward process is carried out to the domain name mapping request message for 53 ports arranged in UDP transport protocol, other ports are not
It processes;Above-mentioned forward rule is all domain name mapping request reports for 53 ports that will arrange in the UDP transport protocol of hit
It is literary to be all forwarded to domain name resolution agent server.
The subsequent domain name resolution agent server is first by way of inquiring pre-generated local cache database pair
The domain name mapping request message is parsed;Successfully resolved then exports corresponding parsing result, and parsing is unsuccessful, i.e., in local
When inquiring in cache database less than domain name in domain name mapping request message, then by inquiring controller pre-generates and issue
Domain name concern list mode the domain name mapping request message received is parsed;If in the domain name mapping request message
Domain name in domain name concern list, then the domain name mapping request message is sent to the connect with the network apparatus remote
It is parsed in one distal end domain name resolution server, the first distal end domain name resolution server generates corresponding after successfully resolved
One parsing result is simultaneously fed back in domain name resolution agent server;If inquiry is requested less than domain name mapping in domain name concern list
When domain name in message, which is sent to the second distal end domain name connecting with the network apparatus remote
It is parsed in resolution server, the second distal end domain name resolution server generates corresponding second parsing result after successfully resolved
And it feeds back in domain name resolution agent server.Domain name mapping request message is after successfully resolved, domain name resolution agent server
Obtain the parsing result of the IP address comprising domain name and the corresponding domain name in domain name mapping request message, and by the parsing result
It is encapsulated in specific message and is forwarded to interchanger, wherein above-mentioned specific message is special UDP message, and above-mentioned interchanger is
Openflow interchanger, above controller are SDN controller.
The study flow table for pre-generating and issuing according to controller after interchanger receives above-mentioned specific message, to special
Message is learnt to obtain corresponding forwarding flow table, is then accordingly turned the corresponding IP address of domain name according to the forwarding flow table
Hair, more preferably, which is forwarded in corresponding service tunnel and establishes corresponding TCP connection, i.e., in the business tunnel
Road carries out corresponding webpage load and processing;
In other words, the invention belongs to SDN gateway side application, for certain domain names for needing specially treated, such as Google
And the access of external number of site domain name, when client opens express passway service, using application traffic of the invention
Client will carry out TCP connection in quick treatment channel when dispatching method to access these website domain names, so that its
Webpage load and processing speed are greater than normal treatment channel.
Specifically, domain name concern list and initial forwarding flow table are previously provided in the control layer where controller,
Wherein, new forward-path is arranged to all concern domain names in domain name concern list, i.e., domain name is paid close attention to the concern in list
The corresponding IP address of domain name carries out application traffic scheduling, enters client in quick treatment channel and carries out TCP connection;Wherein,
Initially the purpose of forwarding flow table setting is, can be according to initial when interchanger receives domain name mapping request message for the first time
The domain name mapping request message is forwarded in local domain name resolution agent server by the forward-path in forwarding flow table;Into one
Step ground generates the forward-path with non-Match IP Address and arranges using the learning functionality of initial forwarding flow table after being parsed
Table, i.e. study flow table.The learning functionality of study flow table is then recycled to generate the forward-path list for being matched with corresponding IP address,
Forward flow table.
Further, in the case where the multichannel first line of a couplet, Openflow interchanger needs the scheduling of application traffic
TCP is completed before shaking hands, and Openflow interchanger only just can be carried out corresponding application stream after learning domain name mapping result
The scheduling of amount.And by above-mentioned application traffic dispatching method, before client carries out TCP connection according to the IP address, hand over
It changes planes and the forwarding of the IP address is completed according to forwarding flow table, to realize Openflow interchanger for the tune of application traffic
Degree.
Controller only needs pre-generated initial forwarding flow table, study stream it can be seen from above-mentioned traffic scheduling method
Table and domain name concern list are simultaneously issued to SDN equipment, while carrying out real-time update to domain name concern list, and for domain name
The relevant treatment of parsing and parsing result, SDN equipment can learn flow table and domain name concern according to above-mentioned initial forwarding flow table
List executes automatically, and the load of controller is greatly reduced while the control flexibility for maintaining controller.
In preferred embodiment of the invention, as shown in Fig. 2, step S1 is specifically included:
Step S11, the initial forwarding flow table of controller pre-generated one, initial forward includes preset domain name mapping in flow table
Port numbers;
Step S12, the network equipment correspond to preset domain name according to what initial forwarding flow table hit client issued
The domain name mapping request message of the port numbers of parsing;
Step S13, the network equipment kidnap domain name mapping request message.
In preferred embodiment of the invention, the initial port numbers for forwarding preset domain name mapping in flow table are the 53 of UDP
Port.
In preferred embodiment of the invention, the process for presetting local cache database including one, local cache number
Domain name resolution agent server is connected according to library;
As shown in figure 3, the process for presetting local cache database specifically includes:
Step A1, the domain name concern column that the network equipment is issued according to the domain name mapping request message of abduction in controller in advance
It is inquired in table, to judge that the domain name in domain name mapping request message whether there is in domain name concern list:
If so, domain name request message to be remotely sent to one first distal end domain name mapping connecting with network apparatus remote
It is parsed in server, is subsequently diverted to step A2;
If it is not, domain name request message to be then remotely sent to one second distal end domain name mapping connecting with network apparatus remote
It is parsed in server, is subsequently diverted to step A3;
Step A2, domain name resolution agent server obtain the first domain name mapping of the first distal end domain name resolution server feedback
Data, and pre-generated according to domain name mapping data and corresponding domain name mapping request message in local cache database the
One standardized domain name parses information;
It includes domain name and the first parsing result for corresponding to domain name in information that first standardized domain name, which parses,;
Step A3, domain name resolution agent server obtain the second domain name mapping of the second distal end domain name resolution server feedback
Data, and pre-generated according to domain name mapping data and corresponding domain name mapping request message in local cache database the
Two standardized domain names parse information;
It includes domain name and the second parsing result for corresponding to domain name in information that second standardized domain name, which parses,;
As shown in figure 4, then step S2 is specifically included:
Step S21, domain name resolution agent server receive domain name mapping request message after, in local cache database into
Row inquiry, to judge that the domain name in domain name mapping request message whether there is in local cache database:
If so, exporting corresponding parsing result, it is subsequently diverted to step S3;
If it is not, then turning to step S22;
Step S22, domain name resolution agent server are inquired in domain name concern list, to judge that domain name mapping is requested
Domain name in message whether there is in domain name concern list:
If so, turning to step S23;
If it is not, then turning to step S24;
It includes several concern domain names in list that domain name, which is paid close attention to,;
Step S23, domain name resolution agent server accesses the first distal end domain name resolution server, to request the first remote domain
Name resolution server parses the domain name in domain name mapping request message, and it is anti-to export the first distal end domain name resolution server
First parsing result of feedback, is subsequently diverted to step S3;
Step S24, domain name resolution agent server accesses the second distal end domain name resolution server, to request the second remote domain
Name resolution server parses the domain name in domain name mapping request message, and it is anti-to export the second distal end domain name resolution server
Second parsing result of feedback, is subsequently diverted to step S3;
When each domain name resolution agent server obtains the first parsing result of the first distal end domain name resolution server feedback,
Domain name resolution server updates local cache number according to the domain name in the first parsing result and corresponding domain name mapping request message
According to library;And
When each domain name resolution agent server obtains the second parsing result of the second distal end domain name resolution server feedback,
Domain name resolution agent server updates local slow according to the domain name in the second parsing result and corresponding domain name mapping request message
Deposit data library.
Specifically, in the present embodiment, the first distal end domain name resolution server is preassigned domain name resolution server, the
Two distal end domain name resolution servers are general domain name resolution server, which can be
114.114.114.114 domain name resolution server, and the first distal end domain name resolution server and the second distal end domain name resolution service
The parsing result of device is different.When the domain name for needing to parse being not present in local cache database, i.e., local domain name mapping generation
When reason server can not be parsed and the domain name that needs to parse is not in domain name concern list, local domain name resolution agent clothes
Business device initiates domain name analysis request to the second distal end domain name resolution server of different business with source address 192.168.1.1, this
When local domain name resolution agent server be equivalent to client, and so on, the corresponding parsing for finally obtaining the domain name is tied
Fruit.
It further include the process being updated to domain name concern list in preferred embodiment of the invention, as shown in figure 5,
It specifically includes:
Step B1, controller receives external modification information, and pays close attention to list to domain name according to modification information and be updated;
Updated domain name is paid close attention to list real time down to the network equipment by step B2, controller.
In preferred embodiment of the invention, modification information includes the change to concern domain name, and/or addition focuses on domain
Name, and/or delete concern domain name.
In preferred embodiment of the invention, interchanger is Openflow interchanger.
A kind of flow scheduling system based on domain name, using any of the above one traffic scheduling method based on domain name,
As shown in fig. 6, specifically including:
The network equipment 1, the network equipment 1 include:
Interchanger 11, the interchanger include:
Hijacking data module 111, the domain name mapping request message and defeated that the network interface for kidnapping the client 2 issues
Out;
Domain name resolution agent server 12 connects interchanger 11, for carrying out domain name according to domain name mapping request message
Parsing, and parsing result generates corresponding specific message and exports;
It include the IP in the domain name and parsing result corresponding with domain name in domain name mapping request message in specific message
Address;
Interchanger 11 further include:
Study module 112, for being learnt to obtain corresponding turn to specific message according to pre-generated study flow table
Send out flow table;
Forwarding module 113, connectionist learning module 112, for the corresponding IP address of domain name to be carried out phase according to forwarding flow table
It should forward.
Controller 3 establishes connection by Openflow agreement and the network equipment 1, for generating study flow table, initial forwarding
Flow table and domain name pay close attention to list, and are issued to the network equipment 1.
In preferred embodiment of the invention, hijacking data module 111 is specifically included:
Data storage cell 1111, it is initial to forward in flow table for saving the initial forwarding flow table of controller pre-generated one
Port numbers including preset domain name mapping;
Data hit unit 1112 connects data storage cell 1111, for hitting client according to initial forwarding flow table
The domain name mapping request message of the port numbers corresponding to preset domain name mapping issued;
Hijacking data unit 1113 connects data hit unit 1112, for kidnapping domain name mapping request message.
In preferred embodiment of the invention, domain name resolution agent server 12 is specifically included:
First memory module 121, for saving pre-generated local cache database;
Second memory module 122, for saving the domain name concern list that controller 3 is pre-generated and issues;
First parsing module 123 connects the first memory module 121, is used for the Yu Ben after receiving domain name mapping request message
It is inquired in ground cache database, and generates corresponding parsing result when inquiring the domain name in domain name mapping request message
And it exports;And
Corresponding first query result is generated when not inquiring the domain name in domain name mapping request message and is exported;
Data inquiry module 124 is separately connected the first parsing module 123 and the second memory module 122, for according to first
Query result is inquired in domain name concern list, and is generated accordingly when inquiring the domain name in domain name mapping request message
The second query result and export;And
Corresponding third query result is generated when not inquiring the domain name in domain name mapping request message and is exported;
It includes several concern domain names in list that domain name, which is paid close attention to,;
Second parsing module 125 connects data inquiry module 124, sets for being accessed according to the second query result with network
The standby 1 one first distal end domain name resolution server 4 remotely connected, to request the first distal end domain name resolution server 4 to domain name solution
Domain name in analysis request message is parsed, and exports the first parsing result of the first distal end domain name resolution server 4 feedback;
Third parsing module 126 connects data inquiry module 124, sets for being accessed according to third query result with network
The standby 1 one second distal end domain name resolution server 5 remotely connected, to request distal end domain name resolution server 5 to ask domain name mapping
It asks the domain name in message to be parsed, and exports the second parsing result of the second distal end domain name resolution server 5 feedback;
Each domain name resolution agent server 12 obtains the first parsing result of the first distal end domain name resolution server 4 feedback
When, domain name resolution agent server 12 updates this according to the domain name in the first parsing result and corresponding domain name mapping request message
Ground cache database;And
Each domain name resolution agent server 12 obtains the second parsing result of the second distal end domain name resolution server 5 feedback
When, domain name resolution agent server 12 updates this according to the domain name in the second parsing result and corresponding domain name mapping request message
Ground cache database.
The foregoing is merely preferred embodiments of the present invention, are not intended to limit embodiments of the present invention and protection model
It encloses, to those skilled in the art, should can appreciate that and all be equal with made by this specification and diagramatic content
It replaces and obviously changes obtained scheme, should all be included within the scope of the present invention.
Claims (10)
1. a kind of traffic scheduling method based on domain name is applied in software defined network, which is characterized in that the software definition
Network includes a controller and the network equipment that connect with the controller, the network equipment include an interchanger and
The domain name resolution agent server being connect with the interchanger;
The external client of software defined network, the client connect the network equipment;
The traffic scheduling method specifically includes the following steps:
Step S1, the network equipment kidnaps the domain name mapping request message that the client issues, and domain name is parsed
Request message is forwarded in domain name parsing proxy server;
Step S2, domain name parse the parsing that proxy server carries out domain name according to domain name analysis request message, then
Export parsing result;
Step S3, domain name parse proxy server and generate corresponding specific message according to the parsing result, and will be described
Specific message is forwarded to the interchanger;
It include the domain name and the solution corresponding with domain name in domain name analysis request message in the specific message
Analyse the IP address in result;
Step S4, the study flow table that the interchanger is pre-generated and issued according to the controller, to the specific message into
Row study obtains corresponding forwarding flow table;
Step S5, the interchanger are accordingly forwarded the corresponding IP address of domain name according to the forwarding flow table.
2. traffic scheduling method according to claim 1, which is characterized in that the step S1 is specifically included:
Step S11, it includes preset domain name in the initial forwarding flow table that the controller pre-generated one is initial, which to forward flow table,
The port numbers of parsing;
Step S12, the network equipment are preset according to the initial forwarding flow table corresponding to of hitting that the client issues
The domain name mapping request message of the port numbers of domain name parsing;
Step S13, the network equipment kidnap domain name analysis request message.
3. traffic scheduling method according to claim 2, which is characterized in that preset described in the initial forwarding flow table
The port numbers of domain name mapping are 53 ports arranged in UDP transport protocol.
4. traffic scheduling method according to claim 1, which is characterized in that preset local cache database including one
Process, local cache database connection domain name parses proxy server;
The process for presetting local cache database specifically includes:
Step A1, the network equipment is according to the domain name analysis request message of abduction in the domain that the controller issues in advance
It is inquired in name concern list, is paid close attention to judging that the domain name in domain name analysis request message whether there is in domain name
In list:
If so, domain name request message to be sent to one first distal end domain name mapping connecting with the network apparatus remote
It is parsed in server, is subsequently diverted to step A2;
If it is not, domain name request message to be then sent to one second distal end domain name mapping connecting with the network apparatus remote
It is parsed in server, is subsequently diverted to step A3;
Step A2, domain name parsing proxy server obtain the first domain name of first distal end domain name resolution server feedback
Data are parsed, and pre-generate the local according to domain name parsing data and corresponding domain name analysis request message
The first standardized domain name in cache database parses information;
It include the first parsing result of domain name and corresponding domain name in the first standardized domain name parsing information;
Step A3, domain name parsing proxy server obtain the second domain name of second distal end domain name resolution server feedback
Data are parsed, and pre-generate the local according to domain name parsing data and corresponding domain name analysis request message
The second standardized domain name in cache database parses information;
It include the second parsing result of domain name and corresponding domain name in the second standardized domain name parsing information;
Then the step S2 is specifically included:
Step S21, after domain name parses proxy server reception domain name analysis request message, Yu Suoshu local cache number
According to being inquired in library, to judge that the domain name in domain name analysis request message whether there is in the local cache database
In:
If so, exporting corresponding parsing result, it is subsequently diverted to the step S3;
If it is not, then turning to step S22;
Step S22, domain name parses proxy server and is inquired in domain name concern list, to judge domain name
Domain name in analysis request message whether there is in domain name concern list:
If so, turning to step S23;
If it is not, then turning to step S24;
It includes several concern domain names in list that domain name, which is paid close attention to,;
Step S23, domain name parse proxy server and access first distal end domain name resolution server, to request described the
One distal end domain name resolution server parses the domain name in domain name analysis request message, and exports first distal end
First parsing result of domain name resolution server feedback, is subsequently diverted to step S3;
Step S24, domain name parse proxy server and access second distal end domain name resolution server, to request described the
Two distal end domain name resolution servers parse the domain name in domain name analysis request message, and export second distal end
Second parsing result of domain name resolution server feedback, is subsequently diverted to step S3;
Each domain name parsing proxy server obtains first solution of first distal end domain name resolution server feedback
When analysing result, domain name resolution server is according in first parsing result and corresponding domain name analysis request message
Domain name update the local cache database;And
Each domain name parsing proxy server obtains second solution of second distal end domain name resolution server feedback
When analysing result, domain name parses proxy server according to second parsing result and corresponding domain name analysis request report
Domain name in text updates the local cache database.
5. traffic scheduling method according to claim 4, which is characterized in that further include being carried out to domain name concern list
The process of update, specifically includes:
Step B1, the controller receive external modification information, and according to the modification information to domain name concern list
It is updated;
Updated domain name is paid close attention to list real time down to the network equipment by step B2, the controller.
6. traffic scheduling method according to claim 5, which is characterized in that the modification information includes to the focuses on domain
The change of name, and/or addition concern domain name, and/or delete the concern domain name.
7. traffic scheduling method according to claim 1, which is characterized in that the interchanger is Openflow interchanger.
8. a kind of flow scheduling system based on domain name, which is characterized in that application is as described in any one of claim 1-7
Traffic scheduling method based on domain name, specifically includes:
The network equipment, the network equipment include:
Interchanger, the interchanger include:
Hijacking data module, for kidnapping the domain name mapping request message of the network interface sending of the client and exporting;
Domain name resolution agent server connects the interchanger, for carrying out domain name according to domain name analysis request message
Parsing, and corresponding specific message is generated according to parsing result and is exported;
It include the domain name and the solution corresponding with domain name in domain name analysis request message in the specific message
Analyse the IP address in result;
The interchanger further include:
Study module, for being learnt to obtain corresponding forwarding to the specific message according to pre-generated study flow table
Flow table;
Forwarding module connects the study module, for according to the forwarding flow table by the corresponding IP address of domain name
Accordingly forwarded.
Controller establishes connection by Openflow agreement and the network equipment, for generating the study flow table, initial turn
It sends out flow table and domain name pays close attention to list, and be issued to the network equipment.
9. traffic scheduling method according to claim 8, which is characterized in that the hijacking data module specifically includes:
Data storage cell, for saving the initial forwarding flow table of the controller pre-generated one, in the initial forwarding flow table
Port numbers including preset domain name mapping;
Data hit unit connects the data storage cell, for hitting the client according to the initial forwarding flow table
What is issued corresponds to the domain name mapping request message of the port numbers of preset domain name parsing;
Hijacking data unit connects the data hit unit, for kidnapping domain name analysis request message.
10. traffic scheduling method according to claim 8, which is characterized in that domain name parses agency service implement body
Include:
First memory module, for saving pre-generated local cache database;
Second memory module, for saving, the controller is pre-generated and the domain name issued pays close attention to list;
First parsing module connects first memory module, is used for the Yu Suoshu after receiving domain name analysis request message
It is inquired in local cache database, and generates corresponding solution when inquiring the domain name in domain name analysis request message
Analysis result simultaneously exports;And
Corresponding first query result is generated when not inquiring the domain name in domain name analysis request message and is exported;
Data inquiry module is separately connected first parsing module and second memory module, for according to described first
Query result is inquired in domain name concern list, and when inquiring the domain name in domain name analysis request message
It generates corresponding second query result and exports;And
Corresponding third query result is generated when not inquiring the domain name in domain name analysis request message and is exported;
It includes several concern domain names in list that domain name, which is paid close attention to,;
Second parsing module connects the data inquiry module, for according to second query result access and the network
The one first distal end domain name resolution server that equipment remotely connects, to request first distal end domain name resolution server to described
Domain name in domain name mapping request message is parsed, and exports the first solution of first distal end domain name resolution server feedback
Analyse result;
Third parsing module connects the data inquiry module, for according to third query result access and the network
The one second distal end domain name resolution server that equipment remotely connects, to request the distal end domain name resolution server to domain name
Domain name in analysis request message is parsed, and exports the second parsing knot of second distal end domain name resolution server feedback
Fruit;
Each domain name parsing proxy server obtains first solution of first distal end domain name resolution server feedback
When analysing result, domain name parses proxy server according to first parsing result and corresponding domain name analysis request report
Domain name in text updates the local cache database;And
Each domain name parsing proxy server obtains second solution of second distal end domain name resolution server feedback
When analysing result, domain name parses proxy server according to second parsing result and corresponding domain name analysis request report
Domain name in text updates the local cache database.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910632026.0A CN110380969B (en) | 2019-07-12 | 2019-07-12 | Domain name based traffic scheduling method and system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910632026.0A CN110380969B (en) | 2019-07-12 | 2019-07-12 | Domain name based traffic scheduling method and system |
Publications (2)
Publication Number | Publication Date |
---|---|
CN110380969A true CN110380969A (en) | 2019-10-25 |
CN110380969B CN110380969B (en) | 2021-10-01 |
Family
ID=68253003
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201910632026.0A Active CN110380969B (en) | 2019-07-12 | 2019-07-12 | Domain name based traffic scheduling method and system |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN110380969B (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110855782A (en) * | 2019-11-14 | 2020-02-28 | 北京顺丰同城科技有限公司 | Service calling system, method, electronic equipment and readable storage medium |
CN113055287A (en) * | 2019-12-27 | 2021-06-29 | 中国电信股份有限公司 | Data packet processing method and device and computer readable storage medium |
CN113873048A (en) * | 2020-06-12 | 2021-12-31 | 腾讯科技(上海)有限公司 | Method and system for downloading application package in application downloading platform |
CN115442292A (en) * | 2022-08-29 | 2022-12-06 | 中国联合网络通信集团有限公司 | Method, device and equipment for adjusting data flow table and storage medium |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104378299A (en) * | 2014-11-20 | 2015-02-25 | 杭州华三通信技术有限公司 | Flow table entry processing method and device |
CN104734963A (en) * | 2015-03-24 | 2015-06-24 | 电子科技大学 | IPv4 and IPv6 network interconnection method based on SDN |
CN104853002A (en) * | 2015-04-29 | 2015-08-19 | 中国互联网络信息中心 | DNS resolution system and DNS resolution method based on SDN |
CN105338123A (en) * | 2014-05-28 | 2016-02-17 | 国际商业机器公司 | Method, apparatus and system for parsing domain name in network |
CN105959217A (en) * | 2016-06-06 | 2016-09-21 | 北京邮电大学 | Data processing method and apparatus for SDN Mobile Ad-Hoc Network |
US9736185B1 (en) * | 2015-04-21 | 2017-08-15 | Infoblox Inc. | DNS or network metadata policy for network control |
US20170339247A1 (en) * | 2016-05-23 | 2017-11-23 | Citrix Systems, Inc. | Systems and methods for provisioning network automation by logically separating l2-l3 entities from l4-l7 entities using a software defined network (sdn) controller |
-
2019
- 2019-07-12 CN CN201910632026.0A patent/CN110380969B/en active Active
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105338123A (en) * | 2014-05-28 | 2016-02-17 | 国际商业机器公司 | Method, apparatus and system for parsing domain name in network |
CN104378299A (en) * | 2014-11-20 | 2015-02-25 | 杭州华三通信技术有限公司 | Flow table entry processing method and device |
CN104734963A (en) * | 2015-03-24 | 2015-06-24 | 电子科技大学 | IPv4 and IPv6 network interconnection method based on SDN |
US9736185B1 (en) * | 2015-04-21 | 2017-08-15 | Infoblox Inc. | DNS or network metadata policy for network control |
CN104853002A (en) * | 2015-04-29 | 2015-08-19 | 中国互联网络信息中心 | DNS resolution system and DNS resolution method based on SDN |
US20170339247A1 (en) * | 2016-05-23 | 2017-11-23 | Citrix Systems, Inc. | Systems and methods for provisioning network automation by logically separating l2-l3 entities from l4-l7 entities using a software defined network (sdn) controller |
CN105959217A (en) * | 2016-06-06 | 2016-09-21 | 北京邮电大学 | Data processing method and apparatus for SDN Mobile Ad-Hoc Network |
Non-Patent Citations (3)
Title |
---|
VISHAL GUPTA,等: ""Secure domain name service in software defined network"", 《2017 20TH INTERNATIONAL CONFERENCE OF COMPUTER AND INFORMATION TECHNOLOGY (ICCIT)》 * |
孙子莹: ""基于SDN架构的网络接入控制功能的设计与实现"", 《中国优秀硕士学位论文全文数据库信息科技辑》 * |
曹维华,等: ""基于转发和控制分离的DNS新型架构研究"", 《广东通信技术》 * |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110855782A (en) * | 2019-11-14 | 2020-02-28 | 北京顺丰同城科技有限公司 | Service calling system, method, electronic equipment and readable storage medium |
CN110855782B (en) * | 2019-11-14 | 2022-12-02 | 北京顺丰同城科技有限公司 | Service calling system, method, electronic equipment and readable storage medium |
CN113055287A (en) * | 2019-12-27 | 2021-06-29 | 中国电信股份有限公司 | Data packet processing method and device and computer readable storage medium |
CN113873048A (en) * | 2020-06-12 | 2021-12-31 | 腾讯科技(上海)有限公司 | Method and system for downloading application package in application downloading platform |
CN113873048B (en) * | 2020-06-12 | 2023-05-12 | 腾讯科技(上海)有限公司 | Method and system for downloading application package in application downloading platform |
CN115442292A (en) * | 2022-08-29 | 2022-12-06 | 中国联合网络通信集团有限公司 | Method, device and equipment for adjusting data flow table and storage medium |
CN115442292B (en) * | 2022-08-29 | 2023-10-03 | 中国联合网络通信集团有限公司 | Data flow table adjusting method, device, equipment and storage medium |
Also Published As
Publication number | Publication date |
---|---|
CN110380969B (en) | 2021-10-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN110380969A (en) | A kind of traffic scheduling method and system based on domain name | |
CN105591819B (en) | The method and device of Configuration network equipment | |
CN104852845B (en) | A kind of intelligent networking gateway | |
CN105207853B (en) | A kind of LAN method for managing and monitoring | |
CN109687995A (en) | A kind of OPC UA message transmitting method based on CoAP suitable for resource-constrained type industrial field device | |
CN105159256B (en) | A kind of intelligent home control system based on Web service | |
CN104144080B (en) | The system and method being managed using remote equipment to terminal device | |
CN106817341B (en) | A kind of Session Initiation Protocol throttling Transmission system and method towards mobile Internet | |
CN101170687A (en) | Method for front recording order to penetrate NAT based on video monitoring | |
CN108965367A (en) | A kind of method and system of control view networked server | |
CN101262372A (en) | Method for video monitoring platform to operate and control front-end device based on SIP server cluster | |
CN101404630B (en) | Method and system for implementing internet service access gate | |
CN102811219A (en) | Method for remotely accessing desktop of computer in intranet across network segments in cluster system | |
CN108964962A (en) | A kind of method and system of control view networked terminals | |
CN106453541A (en) | Data synchronization method, server and data synchronization system | |
CN112637283B (en) | Chat robot-based Internet of things intelligent home management system and control method | |
CN106992906B (en) | A kind of method of adjustment and system of access rate | |
CN109981748A (en) | A kind of positive supply method realized based on Kong gateway | |
CN102263837B (en) | A kind of domain name system DNS analysis method and device | |
CN106911732A (en) | A kind of website visiting accelerating method and device | |
CN105991698A (en) | Method, system and device for mobile terminal remotely managing intelligent router file | |
CN107645543A (en) | Method and system applied to the non-80 caching miniport services of caching server HTTP | |
CN102882733B (en) | A kind of cross-over NAT equipment realizes WEB network management method | |
CN101510196A (en) | Web page push method, system and apparatus thereof | |
CN103516794A (en) | Distributed-server network architecture and achieving method thereof |
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 |