CACHING RESPONSES FOR SCOPED AND NON-SCOPED DOMAIN NAME SYSTEM QUERIES

• US 20120317153A1
• Filed: 06/07/2011
• Published: 12/13/2012
• Est. Priority Date: 06/07/2011
• Status: Abandoned Application

• Current Assignee: Apple Inc.
• Original Assignee: Apple Inc.
• Inventors: Parthasarathy, Mohan, Graessley, Joshua V.
• Application Number:
  US13/155,271
• Publication Number:
  US 20120317153A1
• Time in Patent Office: Days
• US Class Current: 707/805
• CPC Class Codes: H04L 2101/677 Multiple interfaces, e.g. multihomed nodes
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/58 Caching of addresses or names

Abstract

In the described embodiments, while executing a DNS resolver, a processing subsystem in an electronic device with a set of network interfaces receives a scoped request from an application to determine an IP address for a domain name. Generally, a DNS query generated from a scoped request is to be transmitted only on network interfaces specified in the scoped request, whereas a DNS query generated from a non-scoped request can be transmitted on any of the network interfaces. The processing subsystem then generates a DNS query from the scoped request and transmits the DNS query on the specified network interfaces. Upon receiving a response to the DNS query, the processing subsystem stores a record of the response in a scoped portion of a DNS resolution cache that is used only for storing responses to scoped requests. The DNS resolution cache also comprises a non-scoped portion that is used only for storing responses to non-scoped requests.

Claims

1. A method for domain name resolution in an electronic device with a plurality of network interfaces, comprising:

in the electronic device,

receiving a scoped request from an application to determine an IP address for a domain name, wherein the scoped request comprises an indication that a DNS query generated from the scoped request is to transmitted only on network interfaces specified in the scoped request, and wherein a non-scoped request comprises an indication that a DNS query generated from the non-scoped request can be transmitted on any of the network interfaces;

generating a DNS query from the scoped request and transmitting the DNS query only on the network interfaces specified in the scoped request; and

upon receiving a response to the DNS query,

forwarding the response to the application; and

storing a record of the response in a scoped portion of a DNS resolution cache that is used only for storing responses to scoped requests, wherein a non-scoped portion of the DNS resolution cache is used only for storing responses to non-scoped requests.

2. The method of claim 1, further comprising:

receiving a subsequent scoped request to determine an IP address for a domain name from an application; and

checking stored responses in the scoped portion of the DNS resolution cache to determine if a stored response can be used to satisfy the subsequent scoped request;

if so, using the stored response to satisfy the subsequent scoped request;

otherwise, generating a DNS query based on the subsequent scoped request and transmitting the DNS query only on the network interfaces specified in the scoped request.

3. The method of claim 1, further comprising:

receiving a non-scoped request to determine an IP address for a domain name from an application;

generating a DNS query based on the non-scoped request and transmitting the DNS query on any of the network interfaces; and

upon receiving a response to the DNS query,

forwarding the response to the requesting application; and

storing a record of the response in the non-scoped portion of the DNS resolution cache.

4. The method of claim 3, further comprising:

receiving a subsequent non-scoped request to determine an IP address for a domain name from an application; and

checking stored responses in the non-scoped portion of the DNS resolution cache to determine if a stored response can be used to satisfy the subsequent non-scoped request;

if so, using the stored response to satisfy the subsequent non-scoped request;

otherwise, generating a DNS query based on the subsequent non-scoped request and transmitting the DNS query on any of the network interfaces.

5. The method of claim 1, wherein receiving the scoped request comprises:

receiving a call to a function in an application programming interface (API), wherein the call to the function comprises an argument that specifies the network interfaces upon which the DNS query is to be transmitted.

6. The method of claim 1, wherein the method further comprises:

storing a record of the scoped request, wherein the record comprises information to identify the application that made the request and to determine that the request was scoped;

upon receiving the response to the DNS query, using the information in the record of the scoped request to determine the application that sent the request and to determine that the request was scoped; and

performing the forwarding and storing operations based on the determination.

7. The method of claim 1, wherein storing the record of the response in the scoped portion of the DNS resolution cache comprises:

updating an entry in the scoped portion of the DNS resolution cache with information comprising;

the domain name from the response;

the IP address from the response;

the network interface that was used to send the DNS query; and

a DNS server that responded to the request.

8. An apparatus, comprising:

a DNS resolution cache, wherein the DNS resolution cache comprises a memory for caching records of responses to DNS queries;

a scoped portion in the DNS resolution cache, wherein the scoped portion is used for caching records of responses to scoped DNS queries; and

a non-scoped portion in the DNS resolution cache, wherein the non-scoped portion is used for caching records of responses to non-scoped DNS queries.

9. The apparatus of claim 8, wherein the memory in the DNS resolution cache is a contiguous block of memory, and wherein the DNS resolution cache further comprises:

one or more mechanisms configured to indicate the scoped portion and the non-scoped portion.

10. The apparatus of claim 8, wherein the memory in the DNS resolution cache comprises two or more a non-contiguous blocks of memory, and wherein the DNS resolution cache further comprises:

one or more mechanisms configured to indicate the scoped portion and the non-scoped portion.

11. The apparatus of claim 8, wherein the DNS resolution cache further comprises:

one or more adjustment mechanisms configured to dynamically adjust at least one of a size or an arrangement of at least one of the scoped portion, the non-scoped portion, or the DNS resolution cache at runtime based on one or more conditions.

12. The apparatus of claim 8, wherein the DNS resolution cache further comprises:

one or more lookup mechanisms configured to;

compare non-scoped requests with cached records of responses to non-scoped requests to determine if the non-scoped requests can be satisfied from the cached records of responses to non-scoped requests; and

compare scoped requests to cached records of responses to scoped requests to determine if the scoped requests can be satisfied from the cached records of responses to scoped requests; and

a returning mechanism configured to return recorded responses to scoped and non-scoped requests when the scoped and non-scoped requests can be satisfied from corresponding cache records.

13. The apparatus of claim 8, wherein the memory for caching records of responses from DNS queries in the DNS resolution cache comprises a set of entries used to store the records of the responses, each entry comprising information for identifying and satisfying requests for IP addresses based on domain names.

14. The apparatus of claim 13, wherein the information in each entry comprises:

the domain name from a response to DNS query;

the IP address from the response to DNS query;

the interface that was used to send the DNS query; and

the DNS server that sent the response.

15. An electronic device, comprising:

a processing subsystem, wherein the processing subsystem performs computational operations for the electronic device;

a networking subsystem coupled to the processing subsystem, wherein the networking subsystem comprises a plurality of network interfaces; and

a DNS resolution cache coupled to the networking subsystem, wherein the DNS resolution cache comprises;

a scoped portion that is used to cache responses for scoped requests to determine an IP address for a domain name, wherein a scoped request comprises an indication that a DNS query generated from the scoped request is to transmitted only on network interfaces specified in the scoped request; and

a non-scoped portion that is used to cache responses from non-scoped requests to determine an IP address for a domain name, wherein a non-scoped request comprises an indication that a DNS query generated from the non-scoped request is to transmitted on any of the network interfaces.

16. The electronic device of claim 15, further comprising:

a memory subsystem coupled to the network interfaces, wherein the memory subsystem includes one or more computer-readable storage mediums, wherein the DNS resolution cache is implemented in at least one of the computer-readable storage mediums.

17. A computer-readable storage medium storing computer program instructions that, when executed by a processing subsystem, cause the processing subsystem to perform a method for domain name resolution in an electronic device with a plurality of network interfaces, the method comprising:

receiving a scoped request from an application to determine an IP address for a domain name, wherein the scoped request comprises an indication that a DNS query generated from the scoped request is to transmitted only on network interfaces specified in the scoped request, and wherein a non-scoped request comprises an indication that a DNS query generated from the non-scoped request can be transmitted on any of the network interfaces;

generating a DNS query from the scoped request and transmitting the DNS query only on the network interfaces specified in the scoped request; and

upon receiving a response to the DNS query,

forwarding the response to the application; and

storing a record of the response in a scoped portion of a DNS resolution cache that is used only for storing responses to scoped requests, wherein a non-scoped portion of the DNS resolution cache is used only for storing responses to non-scoped requests.

18. The computer-readable storage medium of claim 17, wherein the method further comprises:

receiving a subsequent scoped request to determine an IP address for a domain name from an application; and

checking stored responses in the scoped portion of the DNS resolution cache to determine if a stored response can be used to satisfy the subsequent scoped request;

if so, using the stored response to satisfy the subsequent scoped request;

otherwise, generating a DNS query based on the subsequent scoped request and transmitting the DNS query only on the network interfaces specified in the scoped request.

19. The computer-readable storage medium of claim 17, wherein the method further comprises:

receiving a non-scoped request to determine an IP address for a domain name from an application;

generating a DNS query based on the non-scoped request and transmitting the DNS query on any of the network interfaces; and

upon receiving a response to the DNS query,

forwarding the response to the requesting application; and

storing a record of the response in the non-scoped portion of the DNS resolution cache.

20. The computer-readable storage medium of claim 19, wherein the method further comprises:

receiving a subsequent non-scoped request to determine an IP address for a domain name from an application; and

checking stored responses in the non-scoped portion of the DNS resolution cache to determine if a stored response can be used to satisfy the subsequent non-scoped request;

if so, using the stored response to satisfy the subsequent non-scoped request;

otherwise, generating a DNS query based on the subsequent non-scoped request and transmitting the DNS query on any of the network interfaces.

21. The computer-readable storage medium of claim 17, wherein receiving the scoped request comprises:

receiving a call to a function in an application programming interface (API), wherein the call to the function comprises an argument that specifies the network interfaces upon which the DNS query is to be transmitted.

22. The computer-readable storage medium of claim 17, wherein the method further comprises:

storing a record of the scoped request, wherein the record comprises information to identify the application that made the request and to determine that the request was scoped;

upon receiving the response to the DNS query, using the information in the record of the scoped request to determine the application that sent the request and to determine that the request was scoped; and

performing the forwarding and storing operations based on the determination.

23. The computer-readable storage medium of claim 17, wherein storing the record of the response in the scoped portion of the DNS resolution cache comprises:

updating an entry in the scoped portion of the DNS resolution cache with information comprising;

the domain name from the response;

the IP address from the response;

the network interface that was used to send the DNS query; and

a DNS server that responded to the request.