Parallel, side-effect based DNS pre-caching

• US 9,064,026 B2
• Filed: 02/07/2014
• Issued: 06/23/2015
• Est. Priority Date: 08/25/2008
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Roskind, James
• Primary Examiner(s): Huynh, Dung B
• Application Number:
  US14/175,102
• Publication Number:
  US 20140156780A1
• Time in Patent Office: 501 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 16/9566 URL specific, e.g. using aliases, detecting broken or misspelled links
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• 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/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-caching. A method for DNS pre-caching is provided. The method includes receiving uniform resource locator (URL) hostnames for DNS pre-fetch resolution prior to a user hostname request for any of the URL hostnames. The method also includes making a DNS lookup call for at least one of the URL hostnames that are not cached by a DNS cache prior to the user hostname request. The method further includes discarding at least one IP address provided by a DNS resolver for the URL hostnames, wherein a resolution result for at least one of the URL hostnames is cached in the DNS cache in preparation for the user hostname request. A system for DNS pre-caching is provided. The system includes a renderer, an asynchronous DNS pre-fetcher and a hostname table.

Claims

1. A method for domain name system (DNS) pre-caching comprising:

gathering one or more uniform resource locator (URL) hostnames for DNS pre-fetch resolution from one or more predicted hostnames during a detection of an entering activity, wherein the gathering occurs in parallel to the entering activity and occurs prior to a user entering a complete hostname for a user hostname request for any of the one or more URL hostnames;

making a DNS lookup call for at least one of the one or more URL hostnames that are not cached by a DNS cache, wherein the making occurs in parallel to the gathering and entering activity and prior to the user hostname request; and

caching at least one IP address provided by a DNS resolver for the one or more URL hostnames in the DNS cache in preparation for the user hostname request.

2. The method of claim 1, wherein at least one of the detecting, gathering and making steps are performed by one or more parallel threads.

3. The method of claim 1 further comprising gathering the one or more URL hostnames from one or more URL links in a web page prior to the user selecting a URL link in the web page.

4. The method of claim 1 further comprising:

determining a context associated with the one or more one or more uniform resource locator (URL) hostnames for DNS pre-fetch resolution, wherein the context identifies a value of the one or more URL hostnames to user; and

receiving at least one of the one or more URL hostnames for DNS pre-fetch resolution based on the context and prior to the user hostname request for any of the one or more URL hostnames.

5. The method of claim 4, wherein the receiving comprises:

identifying anchor tags in a web page associated with the one or more URL hostnames;

parsing the anchor tags; and

extracting the one or more URL hostnames from the parsed anchor tags.

6. The method of claim 4, wherein the receiving comprises:

augmenting a link tag associated with the one or more URL hostnames, the augmenting including;

replacing a relationship value in the link tag, such that the relationship value indicates that the one or more URL hostnames are available for pre-fetching.

7. The method of claim 4, wherein the receiving comprises:

scanning a web page associated with the one or more URL hostnames;

setting a limitation on a quantity of the one or more URL hostnames that are pre-fetched, wherein the limitation is based on a total number of URL links found during the scan of the web page; and

gathering the one or more URL hostnames based on the limitation, wherein the one or more URL hostnames are gathered based on the value identified by the context associated with the one or more URL hostnames.

8. The method of claim 1, further comprising:

gathering the one or more URL hostnames based upon one or more URL links on a web page that the user has moused over for a predetermined period of time, but has not selected.

9. The method of claim 1, further comprising:

storing DNS pre-fetch information associated with the one or more URL hostnames, wherein the DNS pre-fetch information is at least one of a DNS resolution tracking information for a DNS task and a transition time for the DNS task.

10. The method of claim 1 further comprising temporarily storing the one or more URL hostnames until a thread passes the one or more hostnames to an API for DNS pre-fetch resolution.

11. The method of claim 1, further comprising passing the one or more URL hostnames as an array.

12. The method of claim 1 further comprising updating pre-fetch information for the one or more URL hostnames in a data structure prior to discarding the IP address.

13. The method of claim 1 further comprising determining a cache eviction time for the one or more URL hostnames.

14. The method of claim 13, wherein the making step further comprises making DNS lookup calls for only the one or more URL hostnames that have not had a DNS lookup call within the determined cache eviction time.

15. The method of claim 1, wherein the making step further comprises limiting DNS lookup calls for the one or more URL hostnames based upon a number of URL links on a web page.

16. The method of claim 1, wherein gathering includes gathering the one or more URL hostnames from the one or more predicted hostnames based upon a result of autocompletion logic.

17. A system for domain name system (DNS) pre-caching comprising:

a gatherer implemented on a computing device and configured to gather one or more uniform resource locator (URL) hostnames from one or more predicted hostnames during a detection of an entering activity in a URL address bar prior to a user completely entering a hostname for a user hostname request, wherein the URL hostnames are gathered in parallel to the entering activity; and

a DNS pre-fetcher implemented on the computing device and configured to make a DNS lookup call for at least one of the one or more URL hostnames during the entering activity, wherein an IP address for the at least one URL hostname is cached in a DNS cache in preparation for the user hostname request, and further wherein the DNS lookup call is made in parallel to the gathering of the URL hostnames and the entering activity.

18. The system of claim 17, further comprising a renderer configured to pass the at least one URL hostname to the DNS pre-fetcher, wherein at least one of the DNS pre-fetcher and the renderer are configured to perform tasks using one or more parallel threads.

19. The system of claim 17, wherein the gatherer is further configured to gather the one or more URL hostnames from one or more URL links in a web page prior to the user selecting a URL link in the web page.

20. A non-transitory computer readable storage medium having control logic stored therein that, in response to execution by a computing device, causes the computing device to perform operations, the control logic comprising:

a first computer readable program code to cause the computing device to gather one or more uniform resource locator (URL) hostnames for DNS pre-fetch resolution from one or more predicted hostnames during a detection of an entering activity, wherein the gathering occurs in parallel to the entering activity and occurs prior to a user entering a complete hostname for a user hostname request for any of the one or more URL hostnames; and

a second computer readable program code to cause the computing device to make a DNS lookup call for at least one of the one or more URL hostnames that are not cached by a DNS cache, wherein the making occurs in parallel to the gathering and entering activity and prior to the user hostname request.