Point of presence management in request routing

• US 10,225,322 B2
• Filed: 06/17/2013
• Issued: 03/05/2019
• 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:
  US13/919,912
• Publication Number:
  US 20130282864A1
• Time in Patent Office: 2,087 Days
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 67/01 Protocols
• 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
• CPC Class Codes: H04L 67/101 based on network conditions
• CPC Class Codes: H04L 67/1021 based on client or server locations
• CPC Class Codes: H04L 67/289 Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

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, performance threshold criteria, testing criteria, and the like.

Claims

1. A computer-implemented method comprising:

obtaining a domain name system (DNS) query from a client computing device at a first DNS server of a content delivery network (CDN) service provider, wherein the DNS query corresponds to a requested resource and comprises a first uniform resource locator (URL), and wherein the CDN service provider is configured to provide the requested resource to the client computing device;

selecting a second DNS server from one or more alternative DNS servers of the CDN service provider based, at least in part, on at least a calculated distance from each of the one or more alternative DNS servers, the second DNS server associated with a second URL, and wherein the second URL is different from the first URL;

obtaining a second DNS query from the client computing device at the second DNS server, the second DNS query corresponding to the second URL;

resolving the second DNS query, at the second DNS server, to identify a cache component for providing the requested resource; and

transmitting information identifying the identified cache component to the client computing device,

wherein the first and second URLs include information identifying a domain of the CDN service provider.

2. The method as recited in claim 1, wherein selecting the second DNS server from the one or more alternative DNS servers based, at least in part, on at least a calculated distance from each of the one or more alternative DNS servers includes selecting the second DNS server based, at least in part, on a calculated distance from each of the one or more alternate DNS servers and a reference node in a communication network.

3. The method as recited in claim 1, wherein selecting the second DNS server from the one or more alternative DNS servers based, at least in part, on at least a calculated distance from each of the one or more alternative DNS servers includes selecting the second DNS server based, at least in part, on a calculated distance from each of the one or more alternate DNS servers and the client computing device.

4. The method as recited in claim 1, wherein selecting the second DNS server from the one or more alternative DNS servers based, at least in part, on at least a calculated distance from each of the one or more alternative DNS servers includes determining a calculated maximum distance as a product of a latency time associated with a selected DNS server and a speed of transmission.

5. The method as recited in claim 1, wherein selecting the second DNS server from the one or more alternative DNS servers further includes selecting the second DNS server from the one or more alternative DNS servers based, at least in part, on performance measurement information associated with each of the one or more alternative DNS servers.

6. The method as recited in claim 5, wherein selecting the second DNS server from the one or more alternative DNS servers based, at least in part, on performance measurement information associated with each of the one or more alternative DNS servers includes:

determining performance measurement information for the one or more DNS servers;

determining whether the performance measurement information exceeds a minimum performance threshold; and

excluding DNS servers in which performance measurement information does not exceed the performance threshold.

7. The method as recited in claim 6, wherein the performance measurement information corresponds to a measured latency.

8. The method as recited in claim 1, wherein selecting the second DNS server from one or more alternative DNS servers includes:

determining that the first resource identifier is associated with an alternative DNS server; and

identifying the one or more alternative DNS servers that are authoritative to first DNS query.

9. A system comprising:

a first network point of presence (POP) including a domain name system (DNS) server of a content delivery network (CDN) service provider, wherein the DNS server receives a DNS query from a client computing device, wherein the DNS query corresponds to a requested resource and comprises a first uniform resource locator (URL), wherein the CDN service provider is configured to provide the requested resource to the client computing device, and wherein the DNS server in the first network POP includes a hardware component and is operative to;

select a second DNS server from one or more alternative DNS servers of the CDN service provider based, at least in part, on at least a calculated distance from each of the one or more alternative DNS servers; and

transmit an alternative URL corresponding to the second DNS server, wherein the alternative URL is different from the first URL; and

a second network POP including a DNS server of the CDN server provider that receives a subsequent DNS query from the client computing device, wherein the subsequent DNS query corresponds to the requested resource associated with the first and alternative URLs, and wherein the DNS server in the second network POP includes a hardware component and is operative to;

resolve the subsequent DNS query to identify a cache component for providing the requested resource; and

transmit information identifying the identified cache component to the client computing device,

wherein the first and alternative URLs include information identifying a domain of the CDN service provider.

10. The system as recited in claim 9, wherein the alternative URL corresponds to a canonical name record identifier.

11. The system as recited in claim 9, wherein selecting the second DNS server from the one or more alternative DNS servers based, at least in part, on at least a calculated distance from each of the one or more alternative DNS servers includes selecting the second DNS server based, at least in part, on a calculated distance from each of the one or more alternate DNS servers and a reference node in a communication network.

12. The system as recited in claim 9, wherein selecting the second DNS server from the one or more alternative DNS servers based, at least in part, on at least a calculated distance from each of the one or more alternative DNS servers includes selecting the second DNS server based, at least in part, on a calculated distance from each of the one or more alternate DNS servers and the client computing device.

13. The system as recited in claim 9, wherein selecting the second DNS server from the one or more alternative DNS servers based, at least in part, on at least a calculated distance from each of the one or more alternative DNS servers includes determining a calculated maximum distance as a product of a latency time associated with a selected DNS server and a speed of transmission.

14. The system as recited in claim 9, wherein selecting the second DNS server from the one or more alternative DNS servers further includes selecting the second DNS server from the one or more alternative DNS servers based, at least in part, on performance measurement information associated with each of the one or more alternative DNS servers.

15. The system as recited in claim 14, wherein selecting the second DNS server from the identified one or more alternative DNS servers based, at least in part, on performance measurement information associated with each of the one or more alternative DNS servers includes:

determining performance measurement information for the one or more DNS servers;

determining whether the performance measurement information exceeds a minimum performance threshold; and

excluding DNS servers in which performance measurement information does not exceed the performance threshold.

16. The system as recited in claim 14, wherein the performance measurement information corresponds to a measured latency.

17. The system as recited in claim 9, wherein information identifying the identified cache component to the client computing device includes a network address of a cache component in the second network POP.

18. The system as recited in claim 9, wherein information identifying the identified cache component to the client computing device includes a network address of a cache component in another network POP.