Adaptive DNS pre-resolution

• US 10,244,073 B2
• Filed: 11/23/2015
• Issued: 03/26/2019
• Est. Priority Date: 03/31/2009
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google LLC (Alphabet Inc.)
• Inventors: Roskind, James
• Primary Examiner(s): Elfervig, Taylor A
• Application Number:
  US14/948,855
• Publication Number:
  US 20160182674A1
• Time in Patent Office: 1,219 Days
• Field of Search: 709223
• CPC Class Codes: G06F 12/0862 with prefetch
• CPC Class Codes: G06F 16/95 Retrieval from the web
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: H04L 61/10 of different types
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/58 Caching of addresses or names
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/5681 Pre-fetching or pre-delivering data based on network characteristics

Abstract

Embodiments of the present invention include methods and systems for domain name system (DNS) pre-resolution. A method for DNS pre-resolution is provided. The method includes initiating a DNS lookup call for one or more sub-resource uniform resource locator (URL) hostnames associated with a referring URL prior to navigation to the referring URL, whereby a resolution result for at least one of the sub-resource URL hostnames is cached in a DNS cache in preparation for navigation to the sub-resource URLs. The method further includes learning relationship information including the sub-resource URLs associated with the referring URL for DNS pre-resolution. A system for DNS pre-resolution is also provided. The system includes a DNS pre-resolver, a navigation monitor and a relationship data store.

Claims

1. A method for domain name system (DNS) pre-resolution in a processor executing a browser that utilizes a DNS to resolve network addresses comprising:

storing, by the browser, relationship information including one or more relationships, each relationship including one or more sub-resource uniform resource locators (URLs) in association with a referring URL, wherein each of the sub-resource URLs is determined by the browser based on content received upon a first navigation to the referring URL by the browser;

initiating, by the browser, and using the stored relationship information, a DNS lookup call for resolving one or more hostnames of the sub-resource URLs associated with the referring URL, the DNS lookup call being initiated by the browser prior to a second navigation by the browser to the referring URL, whereby a resolution result including a resolved internet protocol (IP) address for at least one of the one or more sub-resource URLs hostnames is cached in a DNS cache in preparation for the second navigation to the referring URL by the browser; and

initiating the second navigation to the referring URL and utilizing the resolution result cached in the DNS cache to resolve at least one of the one or more sub-resource URLs hostnames.

2. The method of claim 1, further comprising, prior to storing the relationship information, identifying the relationship information including the one or more sub-resource URLs associated with the referring URL for DNS pre-resolution.

3. The method of claim 2, wherein the identifying comprises detecting the relationship information based upon the one or more sub-resource URLs being loaded into the browser as a consequence of obtaining the content of the referring URL, and the method further comprising determining the consequence based upon an HTTP referrer field found in a header of a request of the one or more sub-resource URLs.

4. The method of claim 1, further comprising receiving the relationship information in the browser, each relationship including the one or more sub-resource URLs associated with the referring URL for DNS pre-resolution.

5. The method of claim 4, wherein the relationship information is received from a server.

6. The method of claim 4, wherein the relationship information is determined from auto-completion suggestions for the referring URL.

7. The method of claim 4, wherein the relationship information is received in a search page.

8. The method of claim 4, wherein the relationship information is received in at least one of XML or an embedded script.

9. The method of claim 1, further comprising removing from DNS pre-resolution a sub-resource URL having an explicit embedded URL link from a second referring URL, wherein a DNS lookup call is not performed for the removed sub-resource URL.

10. The method of claim 1, further comprising removing at least one relationship from the one or more relationships when the at least one relationship is stored within the browser for longer than a threshold time period.

11. A method for domain name system (DNS) pre-resolution in a processor executing a browser that utilizes a DNS to resolve network addresses comprising:

storing, at the browser, relationship information including one or more relationships, each relationship including one or more sub-resource uniform resource locators (URLs) in associations with a referring URL, wherein each of the one or more sub-resource URLs is determined by the browser based on content received from a first navigation to the referring URL;

initiating, by the browser, and using the stored relationship information, a DNS lookup call for resolving at least one hostname of the one or more sub-resource URLs associated with the referring URL simultaneously with navigation to the referring URL;

caching a resolution result that includes a resolved internet protocol (IP) address for the at least one of the one or more sub-resource URLs hostnames in a DNS cache in preparation for navigation to the one or more sub-resource URLs; and

initiating a second navigation to the referring URL and utilizing the resolution result cached in the DNS cache to resolve at least one of the one or more sub-resource URLs hostnames.

12. The method of claim 11, further comprising, prior to storing the relationship information, detecting the relationship information based upon one or more sub-resource URLs being loaded into the browser as a consequence of the browser obtaining the content of the referring URL.

13. The method of claim 11, wherein the relationship information is determined from auto-completion suggestions for the referring URL.

14. The method of claim 11, further comprising opening a connection to at least one of the one or more sub-resource URLs hostnames based upon a relationship valuation.

15. The method of claim 11, wherein the relationship information is determined from domain contents as expressed by the browser'"'"'s history.

16. A system for domain name system (DNS) pre-resolution with a browser that utilizes a DNS to resolve network addresses comprising:

memory, coupled to one or more processors, storing executable instructions for a browser; and

the one or more processors coupled to the memory, the one or more processors being configured to;

store, in the memory, relationship information including one or more relationships, each relationship including one or more sub-resource uniform resource locators (URLs) in association with a referring URL, wherein each sub-resource URL includes a hostname, the sub-resource URLs being determined by the browser based on content received upon a first navigation to the referring URL; and

initiate a DNS lookup call for resolving at least one of the hostnames of the one or more sub-resource URLs associated with a referring URL, based on the stored relationship information, simultaneously with navigation to the referring URL, whereby a DNS resolution result including a resolved internet protocol (IP) address for the at least one of the hostnames of the one or more sub-resource URLs is cached in a DNS cache in preparation for navigation to the one or more sub-resource URLs;

wherein the one or more processors are further configured to perform a second navigation to the referring URL and the resolution result cached in the DNS cache is used to resolve at least one of the one or more sub-resource URLs hostnames.

17. The system of claim 16, wherein the one or more processors are further configured to detect the relationship information based upon the one or more sub-resource URLs being loaded into the browser as a consequence of obtaining the content of the referring URL.

18. The system of claim 16, wherein the referring URL is based on a predicted hostname, wherein the predicted hostname is determined based on previously visited URLs.

19. The system of claim 16, wherein each of the one or more sub-resource URLs includes a hostname referencing a different web site.

20. The system of claim 16, wherein the one or more processors are further configured to identify the relationship information including the one or more sub-resource URLs associated with the referring URL for DNS pre-resolution.