Point of presence management in request routing

• US 9,003,035 B1
• Filed: 09/28/2010
• Issued: 04/07/2015
• Est. Priority Date: 09/28/2010
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Richardson, David R., Cormie, John, MacCarthaigh, Colm, Redman, Benjamin W. S.
• Primary Examiner(s): Fan, Hua
• Application Number:
  US12/892,818
• Time in Patent Office: 1,652 Days
• Field of Search: 709/226
• US Class Current: 709/226
• CPC Class Codes: G06F 16/43 Querying
• CPC Class Codes: H04L 61/10 of different types
• CPC Class Codes: H04L 61/301 Name conversion
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

A system and method for the management of client computing device DNS queries and subsequent resource requests within a content delivery network service provider domain are provided. The management of the DNS queries can include the selection of computing devices corresponding to various Point of Presence locations for processing DNS queries. Additionally, the management of the content requests can include the selection of computing devices corresponding to resource cache components corresponding to various Point of Presence locations for providing requested content. The selection of the computing devices can incorporate logic related to geographic criteria, testing criteria, and the like.

Claims

1. A computer-implemented method for processing content requests comprising:

obtaining, by a content delivery network (CDN) service provider, at a first DNS server a DNS query from a client computing device, wherein the DNS query corresponds to a requested resource, wherein the DNS query is associated with an original resource identifier which corresponds to a uniform resource locator such that the DNS query resolves to a domain corresponding to the CDN service provider;

dynamically identifying two or more alternative DNS servers operative to receive DNS queries;

determining a calculated maximum distance for individual ones of the two or more alternative DNS servers, the calculated maximum distance determined as a product of a latency time between respective individual ones of the two or more alternative DNS servers and a reference node in the communication network;

selecting an alternative DNS server from the identified two or more alternative DNS servers, the alternative DNS server being selected as a function of at least a comparison between a threshold maximum distance and the calculated maximum distance associated with individual ones of the two or more alternative DNS servers;

transmitting an alternative resource identifier corresponding to the selected alternative DNS server to the client computing device;

obtaining a subsequent DNS query from the client computing device at the selected alternative DNS server, wherein the subsequent DNS query corresponds to the alternative resource identifier provided by the CDN service provider;

determining whether the selected alternative DNS server is authoritative to the subsequent DNS query;

selecting a cache component for providing content associated with the original resource identifier if the selected alternative DNS server is authoritative to the subsequent DNS query; and

transmitting information identifying the selected cache component if the selected alternative DNS server is determined to be authoritative.

2. The method as recited in claim 1, wherein the selected alternative DNS server corresponds to the CDN service provider.

3. The method as recited in claim 1, wherein the original resource identifier is provided by a content provider and wherein the content provider is different from the CDN service provider.

4. The method as recited in claim 1, wherein the alternative resource identifier corresponds to a canonical name record identifier.

5. The method as recited in claim 1, wherein the original resource identifier and the alternative resource identifier include information identifying a same domain corresponding to the CDN service provider.

6. The method as recited in claim 1, wherein the original resource identifier includes information identifying a first domain corresponding to the CDN service provider and wherein the alternative resource identifier includes information identifying a second domain corresponding to the CDN service provider.

7. The method as recited in claim 1, wherein the original resource identifier is provided by at least one of a content provider or a CDN service provider, the CDN service provider different from the content provider.

8. The method as recited in claim 1, wherein the reference node corresponds to the client computing device.

9. The method as recited in claim 1, wherein the reference node corresponds to a communication network node.

10. The method as recited in claim 9, wherein the reference node corresponds to at least one of mobile network infrastructure equipment, a DNS server, a DNS resolver component, or a router.

11. A system for request routing comprising:

a first network point of presence associated with a content delivery network (CDN) service provider, wherein the first network point of presence includes a DNS server that receives a DNS query from a client computing device, wherein the DNS query corresponds to requested content associated with an original resource identifier, and wherein the DNS server in the first network point of presence includes a hardware component and is operative to;

identify two or more alternative DNS servers operative to receive DNS queries;

determine a calculated maximum distance for individual ones of the two or more alternative DNS servers, the calculated maximum distance determined as a product of a latency time and a speed of transmission, the latency time being between respective individual ones of the two or more alternative DNS servers and a reference node;

select an alternative DNS server from the identified two or more alternative DNS servers, the alternative DNS server being selected as a function of at least a comparison between a threshold maximum distance and the calculated maximum distance associated with individual ones of the two or more alternative DNS servers; and

transmit an alternative resource identifier corresponding to the selected alternative DNS server to the client computing device; and

a second network point of presence, wherein the second network point of presence includes the selected alternative DNS server and wherein the selected alternative DNS server includes a hardware component and is operative to;

obtain a subsequent DNS query from the client computing device, wherein the subsequent DNS query corresponds to the alternative resource identifier provided by the CDN service provider;

determine whether the selected alternative DNS server is authoritative to the subsequent DNS query;

select a cache component for providing content associated with the original resource identifier if the selected alternative DNS server is authoritative to the subsequent DNS query; and

transmit information identifying the selected cache component if the selected alternative DNS server is determined to be authoritative.

12. The system as recited in claim 11, wherein the second network point of presence is associated with the CDN service provider.

13. The system as recited in claim 11, wherein the original resource identifier is provided by a content provider and wherein the content provider is different from the CDN service provider.

14. The system as recited in claim 11, wherein the alternative resource identifier corresponds to a canonical name record identifier.

15. The system as recited in claim 11, wherein information identifying the identified cache component to the client computing device includes a network address of a cache component in the second network point of presence.

16. The system as recited in claim 11, wherein information identifying the identified cache component to the client computing device includes a network address of a cache component in another network point of presence.

17. The system as recited in claim 11, wherein the original resource identifier and the alternative resource identifier include information identifying a same domain corresponding to the CDN service provider.

18. The system as recited in claim 11, wherein the original resource identifier includes information identifying a first domain corresponding to the CDN service provider and wherein the alternative resource identifier includes information identifying a second domain corresponding to the CDN service provider.

19. The system as recited in claim 11, wherein the original resource identifier is provided by at least one of a content provider or a CDN service provider, the CDN service provider different from the content provider.

20. The system as recited in claim 11, wherein the reference node corresponds to the client computing device.

21. The system as recited in claim 11, wherein the reference node corresponds to a communication network node.

22. The system as recited in claim 21, wherein the reference node corresponds to at least one of mobile network infrastructure equipment, a DNS server, a DNS resolver component, or a router.