Adaptive DNS Pre-Resolution

• US 20150195243A1
• Filed: 03/31/2009
• Published: 07/09/2015
• Est. Priority Date: 03/31/2009
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Roskind, James
• Granted Patent: US 9,225,794 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• 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 the relationship information includes host-names of the sub-resource URLs associated with the referring URL, each of the sub-resource URLs being determined by the browser based on content received upon a previous navigation to the referring URL by the browser;

assigning a valuation to at least one relationship;

initiating, by the browser, and using the stored relationship information, a DNS lookup call for resolving one or more of the sub-resource URLs hostnames associated with the referring URL based on the relationship valuation, the DNS lookup call being initiated by the browser prior to another 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 another navigation to the referring URL by the browser; and

initiating the another 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 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, further comprising 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.

4. The method of claim 3, 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.

5. 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.

6. The method of claim 5, further comprising receiving the relationship information from a server.

7. The method of claim 5, wherein the relationship information is determined from autocompletion suggestions for the referring URL.

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

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

11. 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.

13. The method of claim 1, wherein the assigning is based upon an amount of reduced latency time for DNS resolution.

14. The method of claim 1, wherein the assigning is based upon a duration of DNS pre-resolution associated with a respective sub-resource URL.

15. The method of claim 1, wherein the assigning is based upon a number of the identified sub-resource URLs associated with the referring URL.

16. The method of claim 1, comprising removing at least one relationship from DNS pre-resolution based upon its respective valuation.

17. The method of claim 16, wherein the removing is based upon a number of stored relationships.

18. The method of claim 1, comprising removing a sub-resource of a relationship from the DNS pre-resolution based upon its respective valuation.

19. The method of claim 1, further comprising opening a connection to at least one of the one or more sub-resource URLs based upon a respective valuation.

34. The method of claim 1, wherein the initiating occurs upon user activity indicating a user may navigate to the referring URL.

35. The method of claim 1, wherein the referring URL is based on a predicted hostname.

36. The method of claim 1, wherein each of the one or more sub-resource URLs references a different web site.

37. The method of claim 1, wherein the initiating occurs upon detecting user activity indicating a user may navigate to the referring URL.

10. (canceled)

12. (canceled)

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

a relationship data store implemented by the browser on a computing device configured to store 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 the relationship information includes hostnames names of the sub-resource URLs associated with the referring URL, the sub-resource URLs being determined by the browser based on content received upon a previous navigation to the referring URL by the browser; and

a DNS pre-resolver, implemented by the browser on the computing device, configured to use the stored relationship information to initiate a DNS lookup call for resolving at least one of the one or more sub-resource URL hostnames associated with the referring URL based on a relationship valuation prior to another navigation by the browser to the referring URL, whereby a DNS resolution result including a resolved IP address for at least one hostname of the one or more sub-resource URLs hostnames is cached in a DNS cache in preparation for the another navigation to the referring URL by the browser;

wherein the browser is configured to perform the another 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.

21. The system of claim 20, wherein the DNS pre-resolver is further configured to receive the relationship information, each relationship including one or more sub-resource URLs associated with the referring URL for DNS pre-resolution.

22. The system of claim 20, wherein the DNS pre-resolver is further configured to receive the relationship information in at least one of XML or an embedded script.

23. The system of claim 20, further comprising a navigation monitor configured to identify the relationship information including the one or more sub-resource URLs associated with the referring URL for DNS pre-resolution.

24. The system of claim 23, wherein the navigation monitor is 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.

25. The system of claim 24, wherein the navigation monitor is further configured to determine the consequence based upon an HTTP referrer field found in a header of a request of the one or more loaded sub-resource URLs.

26. The system of claim 20, wherein the DNS pre-resolver is further configured to assign a valuation to at least one relationship including the one or more sub-resource URLs and the associated referring URL.

27. the system of claim 26, wherein the DNS pre-resolver is further configured to assign a valuation based upon an amount of reduced latency time for DNS resolution.

28. The system of claim 26, wherein the DNS pre-resolver is further configured to assign a valuation based upon a duration of DNS pre-resolution associated with a respective sub-resource URL of the one or more sub-resource URLs.

29. The system of claim 26, wherein the DNS pre-resolver is further configured to assign a valuation based upon a number of the identified sub-resource URLs associated with the referring URL.

30. The system of claim 26, wherein the DNS pre-resolver is configured to provide at least one of the one or more sub-resource URLs to a DNS pre-fetcher for DNS pre-resolution based upon a respective valuation.

31. The system of claim 26, wherein the DNS pre-resolver is further configured to remove at least one relationship from DNS pre-resolution based upon its respective valuation.

32. The system of claim 26, wherein the DNS pre-resolver is further configured to remove a sub-resource of a relationship from DNS pre-resolution based upon its respective valuation.

38. The system of claim 20, wherein the DNS pre-resolver is further configured to initiate the DNS lookup call for the one or more sub-resource URL hostnames upon user activity indicating a user may navigate to the referring URL.

39. The system of claim 20, wherein the referring URL is based on a predicted hostname.

40. The system of claim 20, wherein each of the one or more sub-resource URLs references a different web site.

reference to at least five other web sites.

33. (canceled)

41. 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 previous navigation to the referring URL;

assigning a valuation to at least one relationship;

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 based on the relationship valuation in concert with navigation to the referring URL, whereby a resolution result which includes a resolved internet protocol (IP) address for the at least one of the one or more sub-resource URLs hostnames is cached in a DNS cache in preparation for navigation to the one or more sub-resource URLs; and

initiating another 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.

42. The method of claim 41, further comprising 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.

43. The method of claim 41, wherein the relationship information is determined from autocompletion suggestions for the referring URL.

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

45. The method of claim 41, wherein the relationship information is determined from a browser history.

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

a relationship data store implemented by the browser on a computing device configured to store 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 host-name, the sub-resource URLs being determined by the browser based on content received upon a previous navigation to the referring URL; and

a DNS pre-resolver, implemented by the browser on the computing device, configured to use the stored relationship information to initiate a DNS lookup call for resolving at least one of the host-names of the one or more sub-resource URLs associated with a referring URL based on a relationship valuation in concert 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 by the browser to the one or more sub-resource URLs;

wherein the browser is configured to perform another 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.

47. The system of claim 46, wherein the browser is 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.

48. The system of claim 46, wherein the referring URL is based on a predicted hostname.

49. The system of claim 46, wherein each of the one or more sub-resource URLs includes a host-name referencing a different web site.