CN101969478B - Intelligent DNS message processing method and processing device - Google Patents
Intelligent DNS message processing method and processing device Download PDFInfo
- Publication number
- CN101969478B CN101969478B CN 201010508058 CN201010508058A CN101969478B CN 101969478 B CN101969478 B CN 101969478B CN 201010508058 CN201010508058 CN 201010508058 CN 201010508058 A CN201010508058 A CN 201010508058A CN 101969478 B CN101969478 B CN 101969478B
- Authority
- CN
- China
- Prior art keywords
- address
- http server
- dns
- response message
- message
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Abstract
The invention provides an intelligent domain name system (DNS) service processing method and an intelligent DNS service processing device. The method comprises the following steps of: judging whether the connection to which a DNS response message belongs undergoes network address translation (NAT) processing or not; matching an I address of a HTTP Server in a message with a private network E address in a static mapping list item; if the matching is successful, modifying an HTTP Server address in the message according to a mapping relation and then forwarding the modified HTTP Server address; if the matching fails, entering a message forwarding process, namely matching the connection which does not undergo the NAT processing with a public network IP address in the static mapping list item; if the matching is successful, modifying the HTTP Server address according to the mapping relation and then forwarding the modified HTTP Server address; and if the matching fails, entering the massage forwarding process. By the method and the device, the configuration work of users is greatly simplified.
Description
Technical field
The present invention relates to the intelligent gateway technology, relate in particular to a kind of technology of carrying out intelligent DNS message processing at gateway device.
Background technology
HTTP for enterprise uses; HTTP Server(hypertext transfer protocol server〉usually place have safety function gateway device after Intranet; the benefit of doing like this is to avoid HTTPServer to be directly exposed on the public network; can effectively resist diverse network by the security mechanism of intranet and extranet isolation and safety means attacks; such as based on the extensive aggression of Transmission Control Protocol or based on the various attack of http protocol, thereby arrive the purpose of protection HTTP Server.
Because HTTP Server is in Intranet, IP its configuration or that be assigned with address is private network IP address, and inner user (Client) can communicate with it, but it can't directly communicate with outside Client.Usually need to enable nat feature at gateway device for this reason, the HTTP service message is carried out private network IP address to the conversion of public network IP address.Yet because the http protocol regulation is by the Client initiating communication, before the NAT list item is not set up, Client from public network can't have access to HTTP Server, therefore need at the external interface configuration NAT of gateway device static mappings table, be that the private network IP address of HTTP Server distributes a fixing public network IP address in the static mappings list item also.Client can access the public network IP address in the gateway device static entry like this, and then gateway device carries out sending to HTTP Server after NAT processes at the message to Client, and so the HTTP service channel between Client and the Server has just been got through.
Client need to send the IP address that DNS asks to obtain this website before certain HTTP website of access.As previously mentioned because HTTP Server need to accept access from public network and private network Client simultaneously, and each http server only is provided with an IP address among the DNS Server.Therefore need to enable DNS ALG characteristic at gateway device, please refer to two kinds of typical application of Fig. 1 and Fig. 2, the IP address of the HTTP Server that DNS Server disposes in figure l is private network IP address, then for the DNS response message that sends to Intranet user, gateway device is not done special processing to the DNS response message; Then need to make amendment to the DNS response message in the DNSALG module for the DNS response message that sends to public network user, the private network IP address that message inside is carried HTTP Server is revised as the public network IP address that configures, and then transmits.Next just opposite at the network environment of Fig. 2, do not do special processing for the DNS response message that sends public network user, the public network IP address that then needs message inside to be carried HTTP Server for the DNS response message that sends to private user is revised as the private network IP address that configures.
Please further with reference to figure 3, under the network environment of Fig. 3, for gateway device, because DNS Server is positioned at public network, IP address of HTTP Server of configuration must be public network IP address in it.For from the DNS of public network request with reply without gateway device accordingly, but then can pass through gateway device for DNS request and the corresponding DNS response message from Intranet, the public network IP address that gateway device need to carry DNS response message inside HTTP Server is revised as the private network IP address that configures.
Use for above Fig. 1 and two kinds of typical actual networkings of Fig. 2, all need to carry out extra DNSALG configuration, also needing further to distinguish is Intranet or the situation of public network; In case and the IP address of HTTP Server changes, and then need to reconfigure at gateway device, increased the complexity of ordinary enterprises user's Management and application.For Fig. 3, although it does not need to carry out extra configuration, DNS Server is positioned on the public network; lack the protection of safety means; may become the object of being attacked, thereby bring larger potential safety hazard, and the higher saving that also is unfavorable for public network IP address of lower deployment cost.
Summary of the invention
In view of this, the present invention is intended to dispose a kind of more intelligent DNS method for processing business and processing unit for gateway device, comes the assisting users simplification to the configuration effort of network with more intelligent processing method.Technical scheme of the present invention is as follows:
The invention provides a kind of DNS message processing method of intelligence, it is applied in the gateway device, wherein this gateway device is between private network and public network, wherein said private network inside has at least one HTTP Server and DNS Server, described gateway device is used for that the message that transmits between private network and the public network is carried out network address translation (nat) to be processed, and dispose the static mappings list item at the interface towards public network, described static mappings list item comprises the private net address of described HTTP Server and the public network address that has with it mapping relations, and the method comprises:
A identifies the message by gateway device, therefrom identifies the DNS response message;
B judges whether the connection under the described DNS response message has carried out the NAT processing; If so, turn step C, otherwise turn step D
C, remove to mate private net address in the described static mappings list item with the network address of the HTTP Server that carries in the described DNS response message, if the match is successful, transmit again after then according to described mapping relations the network address of the HTTP Server that carries in the DNS response message being revised, otherwise enter the message repeating flow process;
D, remove to mate public network address in the described static mappings list item with the network address of the HTTP Server that carries in the described DNS response message, if the match is successful, transmit again after then according to described mapping relations the network address of the HTTP Server that carries in the DNS response message being revised, otherwise enter the message repeating flow process.
Preferably, comprised also before step C that step e is carried out Hash operation to the public network address in the static mappings list item and generated the public network address chained list, and the private net address Hash operation in the static mappings list item is generated the private net address chained list; Matching process among the wherein said step C is specially: the network address of extracting the HTTP Server that carries in the described DNS response message is carried out Hash operation and is then mated described private net address chained list; Matching process among the described step D is specially: the network address of extracting the HTTP Server that carries in the described DNS response message is carried out Hash operation and is then mated described public network address chained list.
Preferably, described steps A identifies the DNS response message by the corresponding message identification of DNS.
Preferably, the described HTTP Server address of carrying in the DNS response message modification according to mapping relations of step C or step D is specially: if the HTTP Server network address that DNS carries is public network address, then it is revised as the private net address that shines upon mutually with this public network address, if the HTTP Server address that DNS carries is private net address, then it is revised as the public network address with this private net address mapping.
The present invention also provides a kind of DNS message process device of intelligence, it is applied in the gateway device, wherein this gateway device is between private network and public network, wherein said private network inside has at least one HTTP Server and DNS Server, described gateway device is used for that the message that transmits between private network and the public network is carried out network address translation NAT to be processed, and dispose the static mappings list item at the interface towards public network, the public network E address that described static mappings list item comprises the private net address of described HTTP Server and has with it mapping relations, this processing unit comprises the message identification module, enquiry module and DNS application module, wherein
The message identification module is used for the message by gateway device is identified, and therefrom identifies DNS response message and submit Query module;
Enquiry module, the user judges whether the connection under the described DNS response message has carried out the NAT processing, and submits judged result to the DNS application module;
The DNS application module, be used in described judged result for when being, remove to mate private net address in the described static mappings list item with the network address of the HTTP Server that carries in the described DNS response message, if the match is successful, transmit again after then according to described mapping relations the address of the HTTP Server that carries in the DNS response message being revised, otherwise message is sent into normal forwarding process; Perhaps be used for described when the determination result is NO, remove to mate public network address in the described static mappings list item with the network address of the HTTP Server that carries in the described DNS response message, if the match is successful, transmit again after then according to described mapping relations the network address of the HTTP Server that carries in the DNS response message being revised, otherwise message is sent into normal forwarding process.
Preferably, described processing unit also comprises the chained list generation module, and it is used for the public network address of static mappings list item is carried out Hash operation generation public network address chained list, and the private net address Hash operation in the static mappings list item is generated the private net address chained list; Wherein the matching process of DNS application module is specially: the network address of extracting the HTTP Server that carries in the described DNS response message is carried out Hash operation and is then mated described public network/private net address chained list.
Preferably, described message identification module identifies the DNS response message by the corresponding message identification of DNS.
Preferably, described DNS application module is revised the HTTP Server network address of carrying in the DNS response message according to mapping relations and is specially: if the HTTP Server address that DNS carries is public network address, then it is revised as the private net address with this public network address mapping, if the HTTPServer address that DNS carries is private net address, then it is revised as the public network address with this private network IP address mapping.
Description of drawings
Fig. 1 is the networking diagram that a kind of typical HTTP of enterprise uses.
Fig. 2 is the networking diagrams of other the two kinds of typical HTTP of enterprise application.
Fig. 3 is the networking model that another typical HTTP of enterprise uses.
Fig. 4 is the building-block of logic of the present invention's intelligence DNS device.
Embodiment
The present invention focuses on the intelligent processing method of gateway device pair and DNS response message, and reduces by this user's configuration effort, and can not be subject to the impact of http server address configuration change.With better execution mode, recommend adoption computer software of the present invention is as realization mechanism, certainly the present invention do not get rid of soft or hard in conjunction with and the realization of firmware, below introduce first the general handling process of the present invention by preferred embodiments, and describe in conjunction with some examples.
Please refer to the building-block of logic of the present invention of Fig. 4, at first need some the normal configurations in the network environment are introduced, these configurations are the bases of finishing normal inside and outside business intercommunication.Be static mappings list item of HTTP Server configuration at gateway device first, the private network IP address that is HTTP Server distributes a corresponding public network IP address, guarantees that public network user can be to HTTP Server initiating communication.Because DNS Server also is positioned at Intranet, then need to carry out equally corresponding static mappings configuration.Need to prove that the combination that can use the IP address to add port in the at present popular NAT technology identifies unique intranet host in other words as the external network address, so that save public network IP address.Therefore for more succinct and convenient on describing, if not otherwise specified, when relating to the NAT process, it has comprised the situation of IP address the network address, the situation that has comprised equally IP address+port combination, this is that appearance is intelligible for those of ordinary skills, and also is to meet description convention commonly used.Next need correctly to dispose the network address of HTTP Server on the dns server, this address can be the private net address of HTTP Server self, also can be the public network address that has mapping relations with this private net address that disposes on the gateway device external interface, the public network address that the present invention is shone upon at gateway device the private net address of configuration HTTP Server self or its be without any restriction.
As shown in Figure 4, intelligent DNS business processing device comprises message identification module 20, enquiry module 30 and DNS application module 40 in the preferred embodiment of the present invention, and it is responsible for respectively processing the main flow process of the present invention.
Step 101 pair is identified by the message of gateway device, therefrom identifies the DNS response message; This step is processed by message identification module 20, and in general the message identification module both can be that software realizes it also can being that bottom hardware is realized, if the bottom chip support can adopt the mode of hardware identification can improve speed.For the DNS response message, can identify by the sign of message first, such as identifying all DNS messages by well-known port number first, then identify response message or request message by the QR flag bit in the DNS message.
Whether the connection under the described DNS response message that step 102, determining step 101 obtain has carried out the NAT processing: if, turn step 103, otherwise turn step 104, namely judged result is submitted to DNS application module 40.This step 102 is mainly carried out by enquiry module 30.Specifically, (such as the combination of the source and destination IP address of message) removes to mate NAT dynamically and static entry according to the link information of DNS response message; If the match is successful would illustrate the described connection of this message through NAT process.Need to prove that the link information here is comparison broad sense, the tlv triple of message and five-tuple all can use, as long as and match before the NAT conversion or the source and destination IP shifting combination after the conversion can.
Step 103, if determining step 102 judged results are yes, remove to mate private net address in the described static mappings list item with the network address of the HTTP Server that carries in the described DNS response message, if the match is successful, transmit again after then according to described mapping relations the network address of the HTTP Server that carries in the DNS response message being revised, otherwise enter the normal message forwarding process.Step 104, if the determination result is NO for determining step 102, remove to mate public network address in the described static mappings list item with the network address of the HTTP Server that carries in the described DNS response message, if the match is successful, transmit again after then according to described mapping relations the address of the HTTP Server that carries in the DNS response message being revised, otherwise enter the normal message forwarding process.What need supplementary notes is, it is for this special processing of address of aforementioned modifications HTTP Server that what is called enters the normal message forwarding process, be not two or three layers of forwarding that refer to merely message, but say and allow message walk original due handling process, might need in this process to be that safety filtering or NAT etc. process.
Step 103 and 104 is carried out by DNS application module 40, specifically, exists the mapping of a plurality of private net addresses and public network address right in the static mappings list item.In a kind of implementation of excellent limit, processing unit of the present invention also comprises a chained list generation module 50, be mainly used in that the private net address in the static mappings list item is carried out Hash operation and form a private network chained list 60, and public network address carries out putting into a public network chained list 70 after the Hash operation; The DNS application module is when carrying out coupling, and the address of extracting first the HTTP Server that carries in the described DNS response message is carried out Hash operation and then mated described public network/private net address chained list.Owing to the more than record of static mappings list item possibility, and when realizing, usually adopt software engineering, utilize the matching efficiency that the network address that can improve step 103 and 104 is set of Hash processing and chained list, avoid affecting the experience of User DN S business.
Modification for message, if the HTTP Server address that DNS carries is public network address, then it is revised as the private net address that shines upon with this public network address, if the HTTP Server address that DNS carries is private net address, then it is revised as the public network address with this private net address mapping.
Be illustrated below in conjunction with Fig. 1, Fig. 2 and Fig. 3.The network address of the HTTP Server that DNS Server disposes in Fig. 1 is private net address 192.168.2.253, a kind of with the network equipment FW(gateway device of the present invention of firewall functionality) upper HTTP Server has been disposed external static mappings list item, wherein HTTP Server ground private net address 192.168.2.253 and public network address 202.98.5.68 have mapping relations, the private net address 192.168.2.254 that supposes dns server is mapped to 202.98.5.68 equally, according to popular NAT technology, for the uniqueness that guarantees to shine upon, need the leading-in end slogan, supposing that port numbers is 80 for HTTP Server, is 53 for DNS Server.Access to DNS Server mainly contains two kinds of situations, namely Intranet user initiate and external user initiates.
For the situation that Intranet user is initiated, in general, the day mark of Intranet user is the private net address that will obtain HTTPServer, below this target is verified.If the SW(switch) the lower Intranet user 192.168.2.2 that hangs sends the DNS request to DNS Server, because the NAT conversion all at interior network interface, therefore can not carried out now in its network address.When FW has identified DNS Server and has returned to the DNS response message (inside carries the network address 192.168.2.253 of HTTP Server) of 192.168.2.2 from the message that interface is received, FW shows with source IP address and the current NAT stream of purpose IP matching addresses of message, obviously coupling can not hit, according to flow process of the present invention, should change step 104 over to processes, remove public network address in the matched static mapping item with the network address 192.168.2.253 of the HTTP Server that carries in the message, because this moment, the destination address of message was 192.168.2.254, it is a private net address, coupling obviously can not be hit, therefore FW does not do special processing, transmits this DNS response message according to normal flow.So 192.168.2.2 can be subject to the DNS response message of unmodified, and is resolved to its needed HTTP Server network address 192.168.2.53 from response message inside; Obviously the target checking is set up, and Intranet user has successfully obtained the private net address of its needed HTTP Server.
For for the User DN S request of public network direction, in general, it need to obtain the public network address (IP 202.98.5.68, port 80) that HTTP Server shines upon at FW; At first the user can be to (IP 202.98.5.68, port 53) initiates the DNS request, owing to there is corresponding static mappings list item, FW can carry out NAT to this request message to be processed, destination address is revised as the private net address of DNS Server, then be transmitted to DNS Server, DNS Server receives that rear generation DNS response message re-sends to FW.After FW identified the DNS response message, it was own through doing the NAT processing to be connected this connection with the static mappings list item according to link information (being connected with source IP such as purpose IP), need to be sent at this moment step 103 according to flow process of the present invention and process.Remove private net address in the matched static mapping item with the network address 192.168.2.253 of the HTTP Server that carries in the message, as previously mentioned, owing to there is the record of the mapping of 192.168.2.253 in the static mappings list item, therefore obviously can the match is successful, the 192.168.2.253 that the DNS response message need to be carried this moment is revised as the public network address 202.98.5.68 of its mapping, and then being transmitted to user from public network, public network user has successfully obtained the public network address that HTTP Server shines upon at FW thus.
For the situation of Fig. 2, just opposite, will be modified for the DNS response message that returns to Intranet user, and the DNS response message that returns to public network user can not be modified.Detailed process describes in detail no longer one by one.For Fig. 1 and two kinds of situations of Fig. 2, no matter where the user from initiating the DNS request, no matter how the HTTP Server address of the configuration on the DNS Server changes, or how the address configuration of the static mappings list item on the gateway device changes, and gateway device all can return to the network address of the optimal HTTP Server of user intelligently.The user can arbitrarily need to carry out the change of above-mentioned normal configuration according to own service, and such becoming can not cause producing any extra configuration effort, simplified user's network design and management work.
Described above only is the better implementation of the present invention, and in order to limit protection scope of the present invention, any variation that is equal to and modification all should not be encompassed within protection scope of the present invention.
Claims (8)
1. the DNS message processing method of an intelligence, it is applied in the gateway device, wherein this gateway device is between private network and public network, wherein said private network inside has at least one HTTP Server and DNS Server, described gateway device is used for that the message that transmits between private network and the public network is carried out network address translation NAT to be processed, and dispose the static mappings list item at the interface towards public network, described static mappings list item comprises the private net address of described HTTP Server and the public network address that has with it mapping relations, it is characterized in that the method comprises:
A identifies the message by gateway device, therefrom identifies the DNS response message;
B judges whether the connection under the described DNS response message has carried out the NAT processing; If so, turn step C, otherwise turn step D
C, remove to mate private net address in the described static mappings list item with the network address of the HTTP Server that carries in the described DNS response message, if the match is successful, transmit again after then according to described mapping relations the network address of the HTTP Server that carries in the DNS response message being revised, otherwise enter the message repeating flow process;
D, remove to mate public network address in the described static mappings list item with the network address of the HTTP Server that carries in the described DNS response message, if the match is successful, transmit again after then according to described mapping relations the network address of the HTTP Server that carries in the DNS response message being revised, otherwise enter the message repeating flow process.
2. method according to claim 1, it is characterized in that, before step C, also comprise: step e, the public network address in the static mappings list item is carried out Hash operation generate the public network address chained list, the private net address Hash operation in the static mappings list item is generated the private net address chained list; Matching process among the wherein said step C is specially: the network address of extracting the HTTP Server that carries in the described DNS response message is carried out Hash operation and is then mated described private net address chained list; Matching process among the described step D is specially: the network address of extracting the HTTP Server that carries in the described DNS response message is carried out Hash operation and is then mated described public network address chained list.
3. according to the described method of claim l, it is characterized in that described steps A identifies the DNS response message by the corresponding message identification of DNS.
4. method according to claim 1, it is characterized in that, the described HTTP Server address of carrying in the DNS response message modification according to mapping relations of step C or step D is specially: if the HTTP Server network address that the DNS response message carries is public network address, then it is revised as the private net address that shines upon mutually with this public network address; If the HTTP Server address that the DNS response message carries is private net address, then it is revised as the public network address with this private net address mapping.
5. the DNS message process device of an intelligence, it is applied in the gateway device, wherein this gateway device is between private network and public network, wherein said private network inside has at least one HTTP Server and DNS Server, described gateway device is used for that the message that transmits between private network and the public network is carried out network address translation NAT to be processed, and dispose the static mappings list item at the interface towards public network, described static mappings list item comprises the private net address of described HTTP Server and the public network address that has with it mapping relations, it is characterized in that, this processing unit comprises the message identification module, enquiry module and DNS application module, wherein
The message identification module is used for the message by gateway device is identified, and therefrom identifies DNS response message and submit Query module;
Enquiry module, the user judges whether the connection under the described DNS response message has carried out the NAT processing, and submits judged result to the DNS application module;
The DNS application module, be used in described judged result for when being, remove to mate private net address in the described static mappings list item with the network address of the HTTP Server that carries in the described DNS response message, if the match is successful, transmit again after then according to described mapping relations the address of the HTTP Server that carries in the DNS response message being revised, otherwise message is sent into normal forwarding process; Perhaps be used for described when the determination result is NO, remove to mate public network address in the described static mappings list item with the network address of the HTTP Server that carries in the described DNS response message, if the match is successful, transmit again after then according to described mapping relations the network address of the HTTP Server that carries in the DNS response message being revised, otherwise message is sent into normal forwarding process.
6. processing unit according to claim 5, it is characterized in that, comprise the chained list generation module, it is used for the public network address of static mappings list item is carried out Hash operation generation public network address chained list, and the private net address Hash operation in the static mappings list item is generated the private net address chained list; Wherein the matching process of DNS application module is specially: the network address of extracting the HTTP Server that carries in the described DNS response message is carried out Hash operation and is then mated described public network/private net address chained list.
7. processing unit according to claim 5 is characterized in that, described message identification module identifies the DNS response message by the corresponding message identification of DNS.
8. processing unit according to claim 5, it is characterized in that, described DNS application module is revised the HTTP Server network address of carrying in the DNS response message according to mapping relations and is specially: if the HTTP Server address that the DNS response message carries is public network address, then it is revised as the private net address with this public network address mapping, if the HTTP Server address that the DNS response message carries is private net address, then it is revised as the public network address with this private network IP address mapping.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201010508058 CN101969478B (en) | 2010-10-15 | 2010-10-15 | Intelligent DNS message processing method and processing device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201010508058 CN101969478B (en) | 2010-10-15 | 2010-10-15 | Intelligent DNS message processing method and processing device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101969478A CN101969478A (en) | 2011-02-09 |
| CN101969478B true CN101969478B (en) | 2013-03-20 |
Family
ID=43548580
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 201010508058 Active CN101969478B (en) | 2010-10-15 | 2010-10-15 | Intelligent DNS message processing method and processing device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101969478B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104735073B (en) * | 2015-03-30 | 2018-07-06 | 广州杰赛科技股份有限公司 | IPv4-IPv6 transition protocols dispatching method and device |
| CN107707683B (en) * | 2017-05-22 | 2018-06-08 | 贵州白山云科技有限公司 | A kind of method and apparatus for reducing DNS message lengths |
| CN108429684A (en) * | 2018-03-30 | 2018-08-21 | 上海地面通信息网络股份有限公司 | A kind of Network Access Method redirected based on dynamic routing with IP mapping techniques |
| CN113242299A (en) * | 2021-05-11 | 2021-08-10 | 鸬鹚科技(深圳)有限公司 | Disaster recovery system, method, computer device and medium for multiple data centers |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101610294A (en) * | 2009-07-15 | 2009-12-23 | 浪潮电子信息产业股份有限公司 | A kind of method of utilizing intelligent DNS to improve website visiting speed |
| CN101815105A (en) * | 2010-03-25 | 2010-08-25 | 上海交通大学 | Domain name resolution service system with intelligent buffer and service method thereof |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP4010830B2 (en) * | 2002-03-05 | 2007-11-21 | 富士通株式会社 | Communication apparatus and network system |
-
2010
- 2010-10-15 CN CN 201010508058 patent/CN101969478B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101610294A (en) * | 2009-07-15 | 2009-12-23 | 浪潮电子信息产业股份有限公司 | A kind of method of utilizing intelligent DNS to improve website visiting speed |
| CN101815105A (en) * | 2010-03-25 | 2010-08-25 | 上海交通大学 | Domain name resolution service system with intelligent buffer and service method thereof |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101969478A (en) | 2011-02-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8767737B2 (en) | Data center network system and packet forwarding method thereof | |
| CN102223365B (en) | User access method and device based on SSL (Secure Socket Layer) VPN (Virtual Private Network) gateway cluster | |
| CN100531229C (en) | Generic external proxy | |
| CN111131037B (en) | Data transmission method, device, medium and electronic equipment based on virtual gateway | |
| CA2968964C (en) | Source ip address transparency systems and methods | |
| KR100791298B1 (en) | Apparatus and method for controlling device of home network | |
| CN102948132A (en) | Distributed virtual network gateways | |
| CN101582856B (en) | Session setup method of portal server and BAS (broadband access server) device and system thereof | |
| CN100596111C (en) | Method and device for sending out ARP request under condition without VLAN virtual interface | |
| JP2007104624A (en) | Network appliance and management method thereof | |
| CN104202300A (en) | Data communication method and device based on network isolating device | |
| CN102281180A (en) | Virtual network interface card (NIC) communication device applied in mutual communication of terminals in different local area networks | |
| CN101136910B (en) | Network address and protocol translating equipment and application layer gateway equipment | |
| CN100481832C (en) | Communication device, edge router device, server device, communication system and communication method | |
| CN102724175A (en) | Remote communication security management architecture of ubiquitous green community control network and method for constructing the same | |
| CN101969478B (en) | Intelligent DNS message processing method and processing device | |
| CN101252604A (en) | Equipment and method to add IPV6 and DHCP support to the network support package | |
| CN101252583B (en) | Method to enable Infiniband network bootstrap and Infiniband host computer equipment | |
| CN104852840A (en) | Method and device for controlling mutual access between virtual machines | |
| US8472420B2 (en) | Gateway device | |
| CN101753637A (en) | Method and network address translation device preventing network attacks | |
| JPH10285204A (en) | Interconnected ethernet and 1394-network | |
| CN102223422A (en) | Domain name system (DNS) message processing method and network safety equipment | |
| CN112333030B (en) | Method, device, electronic equipment and storage medium for communication between private networks | |
| CN101252582A (en) | Method to enable Infiniband network bootstrap and Infiniband host computer equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C56 | Change in the name or address of the patentee | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 310000 Binjiang District, Hangzhou, Binjiang Avenue, No. Huarong Times Building, room 1601, room 3880 Patentee after: Hangzhou Dipu Polytron Technologies Inc Address before: 310000 Binjiang District, Hangzhou, Binjiang Avenue, No. Huarong Times Building, room 1601, room 3880 Patentee before: Hangzhou Dipu Technology Co., Ltd. |