WO2012119538A1

WO2012119538A1 - Method, system, intelligent dns, computer program and storage medium for parsing dns resolution requests

Info

Publication number: WO2012119538A1
Application number: PCT/CN2012/071972
Authority: WO
Inventors: 张娟; 周琳琅; 李晨
Original assignee: 中国移动通信集团公司
Priority date: 2011-03-09
Filing date: 2012-03-06
Publication date: 2012-09-13
Also published as: CN102685259A; CN102685259B

Abstract

A method, a system, an intelligent DNS, a computer program and a storage medium for parsing DNS parsing requests are provided. The method according to an embodiment comprises: an intranet DNS and an intelligent DNS are provided, and each stores the records indicating the relationship of URLs and IP addresses separately; when the record corresponding to the URL in the DNS parsing request is not found in the intranet DNS and intelligent DNS, the intelligent DNS queries an internet DNS; the intelligent DNS receives a feedback response packet from the internet DNS, and determines whether the business address of local network is comprised in the response packet; according to the result of the determination, IP addresses in the response packet are reordered or the response packet is sent to the intranet DNS directly. According to the scheme provided in the invention, when a Cache system and an intelligent system coexist, a user can access to IDC resources firstly, which optimizes the user access.

Description

The present application relates to the field of Internet data services, and in particular, to a method, a system, an intelligent DNS, a computer program, and a storage medium for parsing a DNS resolution request. At present, the services provided by operators can be divided into the following two categories: One is that operators have been introduced to the intranet, such as the construction of large IDC centers to introduce large websites such as sina and baidu into the intranet; The business has not been introduced, must access the external network or the business obtained through the Cache system of the network. Because the characteristics of these two types of business are very different, the solution is completely different.

For the Cache class service, the Cache system in the carrier network currently uses DNS (Domain Name Server, domain name server, working on port 53 to translate the domain name into a computer-recognizable IP address) to redirect specific content. Guide. First, the intranet DNS queries according to the DNS resolution request initiated by the user. If the website accessed by the user is the specific content cached by the Cache system, the IP address of the Cache system is directly returned to the user by hijacking the user's DNS request, and the Cache system is used. Respond to the client request; if the user accesses the non-cached website, the IP address of the source server is returned and the request is sent to the source server.

For operators that have been introduced to the intranet, such as the construction of large-scale IDC centers to introduce large-scale websites such as sina and baidu into the intranet, the existing solutions can be classified into the following three types.

The first solution is the ICP (Internet Content Provider, the network content service provider, which is a telecom operator that provides Internet information services and value-added services to a large number of customers). The company upgrades to support the smart DNS and feeds back the carrier services to the operators. Address, in which case each ICP provider is required to have a list of all addresses owned by the operator. When the ICP's DNS receives the DNS resolution request, it needs to match the source address of the request. If the source address is the carrier's IP address, the feedback has been introduced into the operator's IDC (Internet Data Center, Internet Data Center, which is the Internet). Content providers, enterprises, media, and various types of websites provide large-scale, high-quality, secure and reliable services for professional server hosting, space leases, network bandwidth, etc.) IP addresses; otherwise, feedback to other carriers' IP addresses. The second solution is a smart DNS configuration website URL (Uniform/Universal Resource Locator, also known as a web address, which is the address of a standard resource on the Internet, and also refers to the domain name accessed by the user) and corresponds to the IP address. Relationships: In this case, it is necessary to deploy the intelligent DNS on the intranet of the operator, and manually configure the URL list of all IDC resources that have been introduced into the intranet and the corresponding relationship with the IP address in the smart DNS device. When the smart DNS receives the request from the intranet DNS, it first queries the local UR.L record, and if there is a corresponding record, responds to the DNS request; if the URJL record is not saved, the intranet DNS is notified to query the external network.

The third solution is to upgrade and support the smart DNS, so that when the smart DNS receives the parsing request, it first queries the local URL record, and if there is a corresponding record, responds to the DNS request; if the URL record is not saved, iteratively queries the external network. The query is performed, and the response is processed according to the received response: When the IP address of the local network operator exists in the DNS response packet, the service address list of the local network is fed back; when the DNS response data packet does not exist, the network operator does not exist. The IP address directly reports the received service address list to the user.

As the IDC resource and the Cache system resources respectively meet different service requirements, in order to coexist the two types of services, the two types of service systems need to be integrated together, that is, the solution for processing the Cache type service described above and the intranet Schemes one, two, and ≡ are processed separately.

When the Cache-based service solution is combined with the solution of the intranet-type service, it is necessary to tell the ICP of the address list held by the operator, and it is not suitable to protect the information of the operator. At the same time, when the operator address list needs to be updated, it is also necessary to notify the ICP in time. Otherwise, the ICP will not be able to identify the user of the carrier using the newly added IP address, and the IP address of the service platform of the network cannot be fed back. In addition, when the two types of services coexist, when the intranet DNS is iteratively queried to the external network, the redirecting device of the Cache system obtains the parsing request through the DPI, and firstly provides feedback to the user. The Cache system resources cannot access the IDC data resources that have been imported on the network, resulting in waste of resources.

When the Cache-type service scheme is combined with the scheme 2 of the intranet-type service, the mapping between the URL and the IP address of the IDC/Cache introduced by the internal network is required to be configured on the intelligent DNS device. When a new IDC resource is introduced, Also need to update the URL list in time. If it cannot be updated in time, the newly introduced IDC resources will be difficult to access. In addition, when two types of services coexist, the IDC resources that can update the URL list in time are not updated to the intelligent DNS because the newly introduced IDC resource information is not updated in time. The intelligent DNS will notify the intranet DNS to perform an iterative query to the external network. In this case, the redirecting device of the Cache system obtains the parsing request through DPI and first feedbacks. As the Cache system can provide feedback faster, the intranet DNS will first receive the Cache system service address list fed back by the Cache system, and feed back the user, causing the user to access the Cache system resources, but cannot access the IDC data resources imported by the network. , resulting in waste of resources.

When the Cache-based service solution is combined with the solution 3 of the intranet service, the service address of the local network is fed back. Therefore, when there is a problem with the service platform of the local network, the user cannot access the external network resources, resulting in a decrease in the user experience. In addition, when the two types of services coexist, for the service that has been introduced, when the smart DNS receives the parsing request, it first queries the local IML record, and if there is a corresponding record, responds to the DNS request; if the URL record is not saved, The query is queried through the iterative query and processed according to the received response. However, when the intelligent DNS performs an iterative query to the external network, the redirecting device of the Cache system obtains the parsing request through the DPI, and first provides feedback. Since the Cache system feeds back the IP address of the Cache resource in the local network, when the intelligent DNS receives the response packet, because there is an IP address of the Cache system of the local network operator, the Cache system feeds back the information in the local network. The service address list is fed back to the user, causing the user to access the Cache system resources, and cannot access the IDC data resources that have been imported on the network, thereby causing waste of resources. The present application aims to provide a method, system, intelligent DNS, computer program and storage medium for parsing DNS resolution requests to avoid the above problems.

This application provides a method for parsing a DNS resolution request.

According to an embodiment, a method for parsing a DNS resolution request includes: providing an intranet DNS and an intelligent DNS, respectively storing a record indicating a correspondence between a URL and an IP address; and the intranet DNS and the smart DNS When the record corresponding to the URL in the DNS resolution request is not found, the smart DNS queries the external network DNS; the intelligent DNS receives the response data packet fed back by the external network DNS, and determines the Responding to the data packet includes the local network service address; according to the determined result, reordering the IP address in the response data packet or directly transmitting the response data packet to the intranet DNS.

According to another embodiment, a method for parsing a DNS resolution request includes: providing an intranet DNS and an intelligent DNS, respectively storing a record indicating a correspondence between a URL and an IP address, The intelligent DNS is deployed on a link connecting the local network and the external network; when the internal network DNS does not find the record corresponding to the URL in the DNS resolution request, the external network DNS is sent through the link. Performing an inquiry; the intelligent DNS acquires the DNS resolution request from the link by capturing packets and locally finds whether there is a record corresponding to the URL in the DNS resolution request; if the DNS resolution request is found The UR.L corresponding record returns the corresponding IP address to the intranet DNS; otherwise, after the packet is retrieved from the link to the response packet returned by the external network DNS, the response data is determined. Whether the IP address of the local network is included in the packet, and further determining, according to the determined result, whether the IP address in the response data packet is rearranged and sent to the intranet DNS.

The present application also provides a system for parsing DNS resolution requests.

According to an embodiment, a system for parsing a DNS resolution request includes an intranet DNS and an intelligent DNS configured on the local network, and is configured to store a record indicating a correspondence between a URL and an IP address, where the smart DNS is configured. After receiving the response data packet fed back by the external network DNS, determining whether the local network service address is included in the response data packet, and rearranging the IP address in the response data packet according to the determined result or The response packet is sent directly to the intranet DNS o

According to another embodiment, a system for parsing a DNS resolution request includes an intranet DNS set on the local network and an intelligent DNS disposed on a link connecting the local network and the external network, respectively a record indicating a correspondence between the URL and the IP address; wherein the smart DNS is capable of acquiring, by the packet, the DNS resolution request sent by the intranet DNS to the external network DNS, and the external network DNS Returning the response data packet; if the smart DNS locally finds the record corresponding to the URL in the DNS resolution request, and feeding back the corresponding IP address to the intranet DNS; otherwise, determining the captured response data Whether the IP address of the local network is included in the packet, and further determining, according to the determined result, whether the IP address in the response data packet is rearranged and sent to the intranet DNS.

According to still another aspect of the present application, an intelligent DNS is provided, including: an obtaining module, acquiring a response data packet returned by an external network DNS for a DNS resolution request; and a determining module, determining whether the response data packet includes a local network IP address And the rewriting module, when the determining module determines that the response data packet includes the local network IP address, rewriting the response data packet to arrange the local network IP address in the response data packet Before the IP address of the network. With the method, the system and the corresponding intelligent DNS provided by the present application, in the case where the Cache-type service and the intranet-type service coexist, the IDC data resource that has been introduced into the intranet is fed back to the user for the service that has been introduced into the intranet. The IP address of the Caehe system resource is not fed back, thus avoiding waste of resources.

DRAWINGS

FIG. 1 illustrates a method of parsing a DNS resolution request in accordance with an embodiment of the present application;

2 illustrates a system for parsing a DNS resolution request in accordance with an embodiment of the present application;

FIG. 3 illustrates a method of parsing a DNS resolution request according to another embodiment of the present application;

4 illustrates a system for parsing a DNS resolution request in accordance with another embodiment of the present application;

Figure 5 illustrates a smart DNS in accordance with one embodiment of the present application;

FIG. 6 shows a smart DNS in accordance with another embodiment of the present application. 1 and 2 illustrate a method 100 and a corresponding system for parsing a DNS resolution request, respectively, in accordance with one embodiment of the present application. As shown in the figure, the intranet DNS 11 and the intelligent DNS 12 are set in the operator's local network 10, and the user's access is directed to the IDC resource or the Cache resource in the local network as needed, wherein the IDC resource is stored in the IDC data center. 13. The Cache resource is stored in the Cache system 14.

After the user initiates the DNS resolution request in step S101, the DNS resolution request is received by the intranet DNS 11 and the local query is made in step S102 whether the request can be resolved. Specifically, the DNS resolution request includes a URL that the user desires to access, and the intranet DNS stores a record indicating a correspondence between the URL and the IP address. Based on the received DNS request, the intranet DNS II queries whether the locally stored record includes an entry corresponding to the URL included in the received request. If so, it is determined that the intranet DNS 11 can parse the received request, and proceeds to step S109 to feed back the parsed corresponding IP address to the user. If the intranet DNS 11 does not find an entry corresponding to the URL included in the received request in its locally saved record, it is determined that the intranet DNS 11 cannot receive the received Request for resolution. In this case, the DNS resolution request is sent to the intelligent DNS in the local network for analysis.

Then, in step S103, the intelligent DNS 12 performs a local inquiry based on the received request. Similarly, the smart DNS 12 may also store a record indicating the correspondence between the URL and the IP address. The records stored in the smart DNS 12 may or may not be the same as the records stored in the intranet DNS 11. If the smart DNS 12 locally finds the record corresponding to the URL in the DNS resolution request, the corresponding IP address is fed back to the intranet DNS 1 in step S108; otherwise, the DNS resolution request is sent to the other operator in step S104. The external network DNS 21 in the network 20 and/or sent to the ICP DNS 31 via the Internet 30 for inquiry. The external network DNS 21 or ICP DNS 31 feeds the query results back to the smart DNS 12 through the response packet. For the sake of brevity, the external network DNS below may represent any DNS other than the one deployed on the carrier's network, including the external network DNS 21 and the ICP DNS 31.

After receiving the response packet returned by the external network DNS, the intelligent DNS ???2 determines whether the received service data packet includes the local network service address in step S105.

If the service address of the local network is included, the service corresponding to the URL is the service that has been imported by the local network, but the correspondence between the URL of the service and the service address of the local network is not recorded in the intranet DNS and the intelligent DNS. In this case, in step S106, the intelligent DNS 12 rewrites the IP address in the received response data packet, and ranks the service address of the local network before the external network service address, so that the user can preferentially access the data service of the local network, and Step S108 feeds back the overwritten response packet to the intranet DNS 11. In this way, for the services that have been introduced on the local network, even if the correspondence between the URL and the service address of the local network is not saved in the intranet DNS II and the intelligent DNS 12, the user's access can be correctly directed to the local network service resources, that is, , IDC Data Center 13.

If the service data address of the local network is not included in the received response data packet, the received response data packet is directly fed back to the intranet DNS 11, and at the same time, the Cache system 14 is instructed to access the address in the response data packet in step S107. The corresponding data obtained is cached, and the intelligent DNS 12 adds the correspondence between the URL in the resolution request and the IP address of the Cache system to its locally saved record. In this way, when the subsequent user needs to access the URL, at step SI03, the smart DNS 12 will find that the local has a corresponding record, and feed back the Cache system IP address to the intranet DNS 11, thereby enabling the user to access the Cache system 14. Resources. By caching resources that have not been introduced on this network in time, This ensures that users on the local network can preferentially access related service resources within the network.

In one embodiment, the intranet DNS 1 can also count and sort the URLs in the received DNS resolution request. In this case, when it is determined that the received response packet does not include the IP address of the local network, the smart DNS 12 first checks the statistics and sorting result of the URL in the intranet DNS 11, and ranks the top UR for the number of times visited. L, the intelligent DNS 12 instructs the Cache system 14 to perform corresponding access and caching. For example, the URLs are sorted according to how many times UR.L is accessed, and only for UR.L ranked within a predetermined number, the smart DNS 12 instructs the Cache system 14 to access and cache. In this case, only the hotspots with more user access are cached in the Cache system 14, thereby reducing the amount of cache of the Cache system 14.

In the above embodiment, if the intranet DNS 11 does not receive the data response packet sent by the smart DNS 12 within a predetermined time, the intranet DNS I I may directly initiate an analysis request to the external network DNS. In this way, when the intelligent DNS 12 or the local network service resources fail, the user can continue to access the external network resources to obtain the analysis result.

3 and 4 illustrate a method 200 and a corresponding system for parsing a DNS resolution request, respectively, in accordance with one embodiment of the present application. The same or similar components in Fig. 4 and Fig. 2 are denoted by the same or similar reference numerals.

As shown in the figure, after the user initiates the DNS resolution request in step S201, the DNS resolution request is received by the intranet DNS 1 deployed in the operator's own network 10, and the request is locally queried in step S102. If the intranet DNS 1 can parse the received request, the process goes to step S210 to feed back the corresponding IP address that is parsed to the user. If the intranet DNS 1 does not find an entry in its locally saved record that corresponds to the URL contained in the received request, then it is determined that the intranet DNS I 1 ' cannot resolve the received request. In this case, the parsing request is initiated to the external network DNS in step S203. The external network DNS will feedback the query results through the response packet. Similarly, the external network DNS may include any DNS other than the one deployed in the carrier network, including the external network DNS 21 in the other carrier networks 20 and the ICP DNS 31 communicatively connected via the Internet 30.

In the present embodiment, the intelligent DNS 12 is disposed on a link that connects the local network to the external network. The intelligent DNS 12' also integrates the DPI packet capture function to actively capture DNS resolution requests and returned response packets on the link. In step S204, the smart DNS 12' resolves the crawled DNS request Perform local resolution. If the smart DNS 12' locally finds the record corresponding to the URL in the DNS resolution request, the corresponding IP address is fed back to the intranet DNS in step S209; otherwise, it waits to retrieve the return of the external network DNS in step S205. Response packet. Then, the intelligent DNS 12' determines in step S206 whether the received service data packet includes the local network service address.

If the service address of the local network is included, the service corresponding to the URL is the service that has been imported by the local network, but the correspondence between the URL of the service and the service address of the local network is not recorded in the intranet DNS 1 and the intelligent DNS 12'. In this case, in step S207, the intelligent DNS 12' rewrites the IP address in the received response data packet, and ranks the service address of the local network before the external network service address, so that the user can preferentially access the data service of the local network. And in response to step S209, the rewritten response packet is fed back to the intranet DNS 11 '. In this way, for the services that have been introduced on the local network, even if the correspondence between the URL and the service address of the local network is not saved in the intranet DNS 1 and the intelligent DNS 12', the user's access can be correctly directed to the local network service resources. , ie, IDC Data Center 13.

If the service address of the local network is not included in the received response data packet, the smart DNS 2' may instruct the Cache system 14 to access the address in the response data packet and cache the obtained corresponding data in step S208, the intelligent DNS 12 'Add the correspondence between the URL in the resolution request and the Cache system IP address to its locally saved record. Thus, when the subsequent user needs to access the URL, in step S204, the smart DNS 12' will find that the local has the corresponding record, and feed back the Cache system IP address to the intranet DNS 1 Γ. By timely buffering the resources introduced by the network, the users of the local network can preferentially access related service resources in the network.

In one embodiment, after receiving the response packet, the intranet DNS 1 may first determine whether the response is from the smart DNS 12' or from the external network DNS. If it is from the intelligent DNS 12% intranet DNS 1 Γ can send DNS resolution response directly to the user. If it is from the external network DNS, the value of TTL (Time to Live, which indicates that the DNS record is cached on the DNS server) in the response packet is reduced (for example, reduced to half) and is in TTL. Re-URL resolution after failure. In this way, for resources that have not been introduced on the network, the household re-requests the parsing after a short time (decreased TTL value). Since the smart DNS 12' has instructed the Cache system 14 to cache after fetching the response packet, the Cache system 14 has already cached the relevant resources upon re-parsing, and the smart DNS 12' has recorded the corresponding correspondence. In this way, when the intelligent DNS 12' performs local parsing, it will find the corresponding record and return the Cache system IP address, thereby guiding the user access to The Cache system 14 enables the users of the local network to preferentially access related service resources in the network. In one embodiment, the intelligent DNS 12' or the intranet DNS 1 统计 counts and ranks the URLs in the received DNS resolution request. In this case, when the intelligent DNS 2'' determines that the received response packet does not include the local IP address, first check the statistics and sorting results of the URL in the smart DNS 12' or the intranet DNS 1 , The URL with the highest number of accesses, the smart DNS 12', instructs the Cache system 14 to perform corresponding access and caching. For example, the URLs are sorted according to the number of times the UR.L is accessed, and only for URLs ranked within a predetermined number, the smart DNS 12' instructs the Cache system to access and cache. In this case, only the hotspots with more user accesses are cached in the Cache System 4, thereby reducing the amount of buffering of the Cache System 4.

This application also proposes a smart DNS. As shown in FIG. 5, the smart DNS 50 according to one embodiment includes an acquisition module 51, a determination module 52, and a rewrite module 53. The acquisition module 5] obtains the response packet returned by the external network DNS for the DNS resolution request. As described above in connection with various embodiments, the response data packet can be directly received by the acquisition module 51 or acquired by packet capture. The determining module 52 determines whether the local network IP address is included in the response packet obtained by the obtaining module 51. In the case that the determining module 52 determines that the response data packet includes the local network IP address, the rewriting module 53 rewrites the response data packet to arrange the local network IP address in the response data packet before the external network IP address, thereby enabling the user Priority access to resources within the network.

As shown in FIG. 6, the smart DNS 50' according to one embodiment may further include a Cache indication module 54 and a storage module 55. In the case that the determining module 52 determines that the response data packet does not include the local network IP address, the Cache indication module 54 instructs the Cache system in the local network to access the external network IP address in the response data packet and cache the acquired data. In the same manner, the storage module 55 stores the correspondence between the URL in the DNS resolution request and the IP address of the Cache system in the smart DNS, so that the subsequent user accesses the URL address and then directs the user to the Cache system.

According to another embodiment, the intelligent DNS 50 may further include a query module (not shown) disposed between the determining module 52 and the Cache indicating module 54. According to this embodiment, the query module can query the URL access system if result in the network. The URL access system results can be saved, for example, in the intranet DNS and/or smart DNS. The Cache indication module 54 selectively instructs the Cache system to access the external network IP address in the response data packet according to the URL access system result obtained by the query module. Specifically, the Cache indication module 54 indicates the Cache in the local network according to the URL access statistics result. The system accesses the external network IP address in the response packet corresponding to the top URL in the URL access statistics result and caches the acquired data. The storage module 55 stores a record corresponding to the URL accessed by the Cache system and the IP address of the Cache system.

Features described above in connection with the specific embodiments of the present application are to be understood as being applicable to other embodiments, unless such features are inconsistent with other embodiments. All of the features disclosed in the present application and/or all of the disclosed methods can be combined in any suitable manner unless at least some of the features and/or steps of the combination are mutually exclusive. The present invention is not limited to the above-described embodiments in detail, but is intended to include appropriate modifications, variations and/or combinations of the above-described embodiments.

Claims

1. A method for parsing a DNS resolution request, including:

Providing an intranet DNS and an intelligent DNS, respectively storing records indicating a correspondence between a URL and an IP address;

When the records corresponding to the URL in the DNS resolution request are not found in the intranet DNS and the smart DNS, the smart DNS queries the external network DNS;

Receiving, by the smart DNS, a response data packet fed back by the external network, and determining whether the response data packet includes a service address of the local network;

Based on the determined result, the address in the response packet is rearranged or the response packet is sent directly to the intranet DNS.

2. The method according to claim 1, wherein, if the smart DNS determines that the received response data packet includes the local network IP address, rewriting the response data packet to rank the local network IP address in the external network IP address. Before the address, the rewritten response data packet is sent to the intranet DNS;

Otherwise, the received response packet is sent to the intranet DNS.

3. The method according to claim 2, wherein, in case the smart DNS determines that the received response data packet does not include the local network IP address, the smart DNS instructs the Cache system to access the received response data packet. The external network IP address is cached and the acquired data is cached, and the smart DNS adds a record indicating that the URL corresponds to the IP address of the Cache system.

4. The method of claim 2, further comprising the intranet DNS assorting and sorting URLs in the received DNS resolution request;

Wherein, in the case that the intelligent DNS does not include the IP address of the local network in determining the received response packet,

The smart DNS checks statistics and sorting results in the intranet DNS, and for a URL ranked first by the number of accesses, the smart DNS instructs the Cache system to access the external network IP address in the corresponding response data packet and The acquired data is cached, and the smart DNS adds a record indicating that the UR.L corresponds to the IP address of the Cache system.

5. The method of claim 1 further comprising: If the intranet DNS does not receive the data response packet sent by the smart DNS within a predetermined time, the intranet DNS directly initiates a parsing request to the external network DNS.

6. A method for parsing a DNS resolution request, including:

Providing an intranet DNS and an intelligent DNS, respectively, storing a record indicating a correspondence between a URL and an IP address, where the smart DNS is deployed on a link connecting the local network and the external network;

When the intranet DNS does not find the record corresponding to the UR.L in the DNS resolution request, the intranet DNS queries the external network DNS through the link;

The smart DNS obtains the DNS resolution request from the link by capturing packets and locally finds whether there is a record corresponding to the URL in the DNS resolution request;

If the record corresponding to the URL in the DNS resolution request is found, the corresponding IP address is fed back to the intranet DNS;

Otherwise, after acquiring the response data packet returned by the external network DNS from the link by the packet capture, determining whether the local IP address is included in the response data packet, and further determining, according to the determined result, whether the The IP address in the response packet is rearranged and sent to the intranet DNS.

7. The method according to claim 6, wherein, if the smart DNS determines that the received response data packet includes the local network IP address, the response data packet is rewritten to rank the local network IP address in the external network IP. Before the address, the rewritten response packet is sent to the intranet DNS.

8. The method according to claim 6, wherein, in a case where the smart DNS determines that the received response data packet does not include the local network IP address, the smart DNS instructs the Cache system to access the received response data packet. The external network IP address in the cache and the obtained data are cached, and at the same time, the smart DNS adds a record indicating that the URL corresponds to the IP address of the Caehe system.

9. The method of claim 6, further comprising the intranet DNS or the smart DNS reconciling and sorting URLs in the received DNS resolution request;

Wherein, in the case that the smart DNS determines that the received response data packet does not include the local network IP address,

The smart DNS checks statistics and sorting results in the intranet DNS or the smart DNS, and ii ranks a top URL for the number of times visited, and the smart DNS indicates that the Cache system is outside the corresponding response data packet. The network IP address accesses and caches the acquired data, and the smart DNS adds a record indicating that the URL corresponds to the IP address of the Cache system.

10. The method of claim 6 further comprising:

The intranet DNS determines that the received response data packet is from the smart DNS or the external network DNS;

When it is determined that the received response data packet is from the external network DNS, the TTL value in the response data packet is decreased, and the URL resolution is re-executed after the reduced TTL value is invalid.

1 L A system for parsing a DNS resolution request, including an intranet DNS and an intelligent DNS set on the local network, respectively for storing a record indicating a correspondence between a URL and an IP address;

After receiving the response data packet fed back by the external network DNS, the smart DNS determines whether the service data address of the local network is included in the response data packet, and performs an IP address in the response data packet according to the determined result. Rearranging or sending the response packet directly to the intranet DNS.

12. The system according to claim 1, wherein, if the smart DNS determines that the received response data packet includes the local network IP address, the response data packet is rewritten to rank the local network CP address in the external network IP. Before the address, the rewritten response data packet is sent to the intranet DNS;

Otherwise, the received response packet is sent to the intranet DNS.

The system according to claim 2, wherein the intelligent DNS determines that the received response data packet does not include the local network IP address, and instructs the Cache system to access the external network in the received response data packet. The IP address caches the acquired data, and the smart DNS adds a record indicating that the URL corresponds to the IP address of the Cache system.

14. The system according to claim 2, wherein the intranet DNS performs statistics and ordering on URLs in the received DNS resolution request; the intelligent DNS does not include the local network IP in determining the received response data packet. In the case of an address, the system performs the sorting result in the intranet DNS, and, for the URL ranked first by the number of accesses, the smart DNS instructs the Cache system to perform the external network IP address in the corresponding response packet. Accessing and caching the acquired data, and the smart DNS adds a record indicating that the URL corresponds to an IP address of the Cache system.

The system according to claim ,, wherein, if the intranet DNS does not receive the data response packet sent by the smart DNS within a predetermined time, the DNS request is directly sent to the external network DNS.

16. A system for parsing a DNS resolution request, comprising: an intranet DNS set on the local network and an intelligent DNS disposed on a link connecting the local network and the external network, respectively for storing an indication a record of the correspondence between the URL and the IP address;

The smart DNS can acquire, by the packet capture, the DNS resolution request sent by the intranet DNS to the external network DNS, and the response data packet returned by the external network DNS.

If the smart DN S finds the record corresponding to the URL in the DNS resolution request locally, the smart DN S feeds back the corresponding IP address to the intranet DNS;

Otherwise, determining whether the captured response packet includes the local network IP address, and further determining, according to the determined result, whether the IP address in the response packet is rearranged and sent to the intranet

17. The system according to claim 6, wherein the intelligent DNS rewrites the response data packet to exclude the local network IP address when determining that the received response data packet includes the local network IP address. Before the network IP address, the rewritten response data packet is sent to the intranet DNS.

18. The system according to claim 16, wherein the intelligent DNS instructs the Caete system to access the external network in the received response data packet if it is determined that the received response data packet does not include the local network IP address. The IP address caches the acquired data, and the smart DNS adds a record indicating that the URL corresponds to the IP address of the Cache system.

19. The system according to claim 16, wherein the intranet DNS or the smart DNS performs statistics and ordering on URLs in the received DNS resolution request; the intelligent DNS does not determine in the received response packet. In the case of the IP address of the local network, the statistics and the sorting result in the intranet DNS or the smart DNS are viewed, and the smart DNS instructs the Cache system to respond to the URL ranked first in the number of times visited. The external network IP address in the data packet is accessed and the obtained data is cached, and at the same time, the intelligent DNS adds a record indicating that the URL corresponds to the IP address of the Cache system.

20. The system of claim 6, wherein the intranet DNS determines that the received response data packet is from the smart DNS or the external network DNS; and when determining that the received response data packet is from the In the case of the external network DNS, the TTL value in the response packet is reduced, and the URL resolution is re-executed after the reduced TTL value expires.

21. A smart DNS, including:

Obtaining a module, and obtaining a response packet returned by the external network DNS to the DNS resolution request;

Determining a module, determining whether the local IP address is included in the response packet; Rewriting the module, in the case that the determining module determines that the response data packet includes the local network address, rewriting the response data packet to rank the local network IP address in the external network IP address in the response data packet prior to.

22. The intelligent DNS of claim 21, further comprising:

The Cache indication module, when the determining module determines that the response data packet does not include the local network address, instructs the Cache system in the local network to access the external network IP address in the response data packet and The acquired data is cached;

The storage module stores a record corresponding to a URL in the DNS resolution request and a 1GP address of the Cache system.

23. The intelligent DNS of claim 21, further comprising:

The query module queries the URL access statistics in the local network.

The Cache indication module, according to the URL access statistics result, instructs the Cache system in the local network to access and obtain the external network IP address in the response data packet corresponding to the top URL in the URL access statistics result. Data is cached; and

And a storage module, configured to store the record corresponding to the IP address of the Cache system.

24. The intelligent DNS of claim 2, wherein the obtaining module directly receives the response data packet or acquires the response data packet by capturing a packet.

25. A computer program comprising instructions, which when executed by a processor, are arranged to cause the processor to perform the method of any of claims.

26. A storage medium storing a computer program as claimed in claim 25.