Methods and systems for processing a DNS request

• US 9,912,630 B2
• Filed: 04/22/2014
• Issued: 03/06/2018
• Est. Priority Date: 12/13/2013
• Status: Active Grant

• Current Assignee: Pismo Labs Technology Limited
• Original Assignee: Pismo Labs Technology Limited
• Inventors: Chan, Alex Wing Hong, Chan, Ho Ming, Chau, Kit Wai, Yip, Chi Pan, Tsai, Min-Fu
• Primary Examiner(s): Etienne, Ario
• Assistant Examiner(s): WAUGH, THORNE
• Application Number:
  US14/410,107
• Publication Number:
  US 20160269353A1
• Time in Patent Office: 1,414 Days
• Field of Search: 709203-230
• CPC Class Codes: G06F 16/29 Geographical information databases
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• CPC Class Codes: H04L 12/6418 Hybrid transport
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 2101/69 using geographic information, e.g. room number
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/5053 Lease time; Renewal aspects

Abstract

A method and system for processing Domain name Services (DNS) request in a gateway. The gateway receives a DNS request from a host from its local area network. The gateway then selects DNS server(s) and transmits a new DNS request to at least one DNS server(s). DNS server(s) may or may not be accessible through a first tunnel. The contents of the new DNS request are the same as the content of the received DNS request. Further, when the gateway receives a DNS response corresponding to the DNS request, it determines a decision whether to transfer data to the host whose IP address is specified in the DNS response through a second tunnel. The decision may be based on a geographical location of an IP address.

Claims

1. A method for processing Domain Name Services (DNS) request in a gateway, wherein the gateway comprises at least one local area network (LAN) interface and at least one wide area network (WAN) interface, the method comprising:

(a) receiving a first DNS request from a first host via one of the at least one LAN interface of the gateway;

(b) selecting, according to at least one predefined selection policy, at least one DNS server;

(c) transmitting a plurality of new DNS requests, containing all the contents of the first DNS request to the at least one DNS server through at least one tunnel via the at least one WAN interface if the at least one DNS server is accessible through the at least one tunnel;

(d) transmitting the plurality of new DNS requests to the at least one DNS server without using a tunnel via the at least one WAN interface if the at least one DNS server is not accessible through any of the at least one tunnel;

(e) receiving a plurality of DNS responses corresponding to the plurality of new DNS requests within a first predefined time period;

(f) storing the plurality of DNS responses;

(g) when the first predefined time period has expired;

selecting a first DNS response from the received plurality of DNS responses according to at least one predefined DNS response selection policy;

wherein when at least one of the plurality of DNS responses is valid, the selection policy is to select one of the at least one valid DNS response based on time of arrival, contents of each of the plurality of DNS responses, identity of DNS servers from which each of the plurality of DNS responses are received, or source of each of the plurality of DNS responses;

wherein when none of the DNS responses are valid;

the selection policy is to select one of the DNS responses randomly, statistically, according to the time of receiving or according to the order of receiving;

(h) transmitting a new DNS response to the host wherein the content of the new DNS response is based on the content of the first DNS response;

wherein if the first DNS response is not a valid DNS response, setting return code (RCODE) of the new DNS response to an RCODE contained in a majority of the plurality of DNS responses; and

(i) when the gateway has information to respond to the first DNS request;

responding to the DNS request; and

not transmitting the plurality of new DNS requests.

2. The method of claim 1, wherein the step of selecting the at least one DNS server comprising:

determining one or more DNS servers that are accessible by the gateway through the at least one tunnel; and

selecting at least one DNS server from the one or more DNS servers.

3. The method of claim 1, further comprising:

(j) determining the geographical location of an IP address specified in the first DNS response by using an IP geo location database;

(k) determining a decision whether to transfer data to a second host using a second tunnel;

transferring data to the second host using the second tunnel if the decision is to use the second tunnel; and

(l) transferring data to the second host not using the second tunnel if the decision is not to use the second tunnel or there is no decision;

wherein the second host is accessible through the IP address specified in the first DNS response.

4. The method of claim 3, wherein the first DNS response is received through a first tunnel, wherein the first tunnel is one of the at least one tunnel used to transmit the plurality of new DNS requests and the first tunnel is the same as the second tunnel.

5. The method of claim 3, wherein the first DNS response is received through a first tunnel, wherein the first tunnel is one of the at least one tunnel used to transmit the plurality of new DNS requests and the first tunnel is not the same as the second tunnel.

6. The method of claim 3, wherein the step of determining whether to transfer data is based on the geographical location of the IP address specified in the first DNS response.

7. The method of claim 3,

wherein the first DNS response is selected from a plurality of DNS responses, wherein:

if there is at least one DNS response received through the at least one tunnel, the first DNS response is selected from the at least one DNS response received through the at least one tunnel; and

if there is no DNS response received through any of the at least one tunnel, the first DNS response is selected from the plurality of DNS responses received.

8. The method of claim 7, wherein the new DNS response has a non-zero return code when no DNS response corresponding to the plurality of new DNS request is received within the first redefined time period.

9. The method of claim 7, wherein the step of determining whether to transfer data is based on the whether the IP addresses specified in at least two of the plurality of DNS responses are the same.

10. The method of claim 3, wherein the decision is stored in a computer readable storage medium of the gateway;

and

wherein the decision is deleted from the computer readable storage medium when a time period specified in a time-to-live (TTL) field of the first DNS response has expired.

11. The method of claim 3, wherein the decision is stored in a computer readable storage medium, and the decision contains the IP address specified in the first DNS response;

wherein the IP address in the decision is updated to an IP address specified in a second DNS response;

wherein the first DNS response corresponds to a first one of the plurality of new DNS requests;

wherein the second DNS response corresponds to a second one of the plurality of new DNS requests; and

wherein the second DNS response is received after transmitting the second one of the plurality of new DNS requests, wherein the second at least one new DNS request is transmitted when a time period specified in a TTL field of the first DNS response has expired.

12. A gateway for processing Domain Name Services (DNS) request, comprising:

at least one local area network (LAN) interface;

at least one wide area network (WAN) interface;

at least one processing unit;

at least one computer readable storage medium storing program instructions executable by the at least one processing unit for;

(a) receiving a first DNS request from a first host via one of the at least one LAN interface of the gateway;

(b) selecting, according to at least one predefined selection policy, at least one DNS server,

(c) transmitting a plurality of new DNS requests, containing all the contents of the first DNS request to the at least one DNS server through at least one tunnel via the at least one WAN interface if the at least one DNS server is accessible through the at least one tunnel;

(d) transmitting the plurality of new DNS requests to the at least one DNS server without using a tunnel via the at least one WAN interface if the at least one DNS server is not accessible through any of the at least one tunnel;

(e) receiving a plurality of DNS responses corresponding to the plurality of new DNS requests within a first predefined time period;

(f) storing the plurality of DNS responses;

(g) when the first predefined time period has expired;

selecting a first DNS response from the received plurality of DNS responses according to at least one predefined DNS response selection policy;

wherein when at least one of the plurality of DNS responses is valid, the selection policy is to select one of the at least one valid DNS response based on time of arrival, contents of each of the plurality of DNS responses, identity of DNS servers from which each of the plurality of DNS responses are received, or source of each of the plurality of DNS responses;

wherein when none of the DNS responses are valid;

the selection policy is to select one of the DNS responses randomly, statistically, according to the time of receiving or according to the order of receiving;

(h) transmitting a new DNS response to the host wherein the content of the new DNS response is based on the content of the first DNS response;

wherein if the first DNS response is not a valid DNS response, setting return code (RCODE) of the new DNS response to an RCODE contained in a majority of the plurality of DNS responses; and

(i) when the gateway has information to respond to the first DNS request;

responding to the DNS request; and

not transmitting the plurality of new DNS requests.

13. The gateway of claim 12, wherein the step of selecting the at least one DNS server comprising:

determining one or more DNS servers that are accessible by the gateway through the at least one tunnel; and

selecting at least one DNS server from the one or more DNS servers.

14. The gateway of claim 12, wherein the at least one computer readable storage medium further storing program instructions executable by the at least one processing unit for:

(j) determining the geographical location of an IP address specified in the first DNS response by using an IP geo location database;

(k) determining a decision whether to transfer data to a second host using a second tunnel;

transferring data to the second host using the second tunnel if the decision is to use the second tunnel;

(l) transferring data to the second host not using the second tunnel if the decision is not to use the second tunnel or there is no decision;

wherein the second host is accessible through the IP address specified in the first DNS response.

15. The gateway of claim 14, wherein the first DNS response is received through a first tunnel, wherein the first tunnel is one of the at least one tunnel used to transmit the plurality of new DNS requests and the first tunnel is the same as the second tunnel.

16. The gateway of claim 14, wherein the first DNS response is received through a first tunnel, wherein the first tunnel is one of the at least one tunnel used to transmit the plurality of new DNS requests and the first tunnel is not the same as the second tunnel.

17. The gateway of claim 14, wherein the step of determining whether to transfer data is based on the geographical location of the IP address specified in the first DNS response.

18. The gateway of claim 14,

wherein the first DNS response is selected from a plurality of DNS responses, wherein:

if there is at least one DNS response received through the at least one tunnel, the first DNS response is selected from the at least one DNS response received through the at least one tunnel; and

if there is no DNS response received through any of the at least one tunnel, the first DNS response is selected from the plurality of DNS responses received.

19. The gateway of claim 18, wherein the new DNS response has a non-zero return code when no DNS response corresponding to the plurality of new DNS request is received within the first predefined time period.

20. The gateway of claim 18, wherein the step of determining whether to transfer data is based on the whether the IP addresses specified in at least two of the plurality of DNS responses are the same.

21. The gateway of claim 14, wherein the decision is stored in the computer readable storage medium of the gateway;

and

wherein the decision is deleted from the computer readable storage medium when a time period specified in a time-to-live (TTL) field of the first DNS response has expired.

22. The gateway of claim 14, wherein the decision is stored in a computer readable storage medium, and the decision contains the TP address specified in the first DNS response;

wherein the IP address in the decision is updated to an IP address specified in a second DNS response;

wherein the second DNS response corresponds to a second at least one new DNS request;

and wherein the second DNS response is received after transmitting the second at least one new DNS request, wherein the second at least one new DNS request is transmitted when a time period specified in a TTL field of the first DNS response has expired.