Determining Network Delay and CDN Deployment

• US 20100088405A1
• Filed: 10/08/2008
• Published: 04/08/2010
• Est. Priority Date: 10/08/2008
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Wang, Angela, Li, Jin, Huang, Cheng, Ross, Keith Wimberly
• Application Number:
  US12/247,394
• Publication Number:
  US 20100088405A1
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 43/0864 Round trip delays
• CPC Class Codes: H04L 47/10 Flow control; Congestion control

Abstract

Charting a content distribution system (CDN) involves identifying a set of DNS servers that may be used as vantage points to test delay performance to a CDNs content server. As provided herein, to identify potential vantage point DNS servers, a set of authoritative name servers is identified and, from that set, those authoritative name servers that respond to a DNS query are identified as responsive authoritative name servers. Identifying a CDN content server that serves a particular vantage point DNS server involves retrieving an IP address for the CDN content server from a DNS query to the DNS server corresponding to the vantage point. The delay performance between the vantage point DNS server and the CDN content server can then be determined. Further, one can determine locations to deploy new data centers for a CDN based on delay performance, A delay from one or more vantage points to an existing CDN'"'"'s DNS servers can be measured, and desired rank of locations can be generated. A location of a new data center can be selected based on a desired delay performance ranking.

Claims

1. A method for determining delay performance of an Internet content provider using network latency between a target server and one or more vantage point domain name system (DNS) servers, comprising:

identifying a set of vantage point DNS servers, comprising;

identifying a set of potential vantage point DNS servers comprising authoritative name servers; and

identifying responsive authoritative name servers as open recursive DNS servers comprising identifying authoritative name servers that respond to a trial DNS query from a remote client;

identifying a local DNS (LDNS) server co-located with the target server serving a vantage point comprising retrieving an IP address from a DNS query to a vantage point DNS server, the IP address corresponding to the target server used to serve the vantage point DNS server; and

determining a delay between the LDNS server and the vantage point DNS servers.

2. The method of claim 1, identifying a set of authoritative name servers to use as potential vantage points comprising at least one of:

using a reverse DNS lookup to identify authoritative name servers corresponding to IP addresses from a set of IP addresses; and

using a reverse DNS lookup to identify authoritative name servers corresponding to web hostnames from a set of web hostnames.

3. The method of claim 1, the target server comprises a DNS server in a content delivery network (CDN), and the LDNS server merely comprises the DNS server.

4. The method of claim 3, identifying the LDNS server co-located with the content server comprising:

identifying a canonical name (CNAME) that resolves to a desired number of CDN servers in a desired geographic region;

sending a query to one of the vantage point DNS servers, the query comprising a DNS query for resolving the identified CNAME; and

retrieving an IP address from the DNS query, the IP address corresponding to a CDN content server used to serve the vantage point DNS server.

5. The method of claim 3, identifying a CNAME comprising:

performing a DNS query on web hostnames from a set of hostnames;

determining if the DNS query of a web hostname resolves to a canonical name (CNAME); and

determining if a CNAME query resolves to a hostname of the CDN;

6. The method of claim 1, identifying a set of vantage point DNS servers using a distributed execution platform comprising:

dividing the identifying task into more than one smaller tasks; and

distributing the smaller tasks to more than one separate computing node to perform an assigned task.

7. The method of claim 1, comprising grouping target servers into clusters based on a desired network delay between the target servers in the cluster and the vantage point DNS servers.

8. The method of claim 1, determining a delay between the target server and the vantage point DNS server comprising:

sending a mock DNS query to the vantage point DNS server from a measurement client to resolve a mock name claimed under an authority of the LDNS server;

using a response from the mock DNS query to determine a delay between the measurement client and the LDNS server; and

subtracting a delay between the measurement client and the vantage point DNS server from the delay between the measurement client and the LDNS server.

9. The method of claim 8, determining a delay between the LDNS server and the vantage point DNS server comprising:

registering a measurement domain;

operating a DNS server for responding to queries for the measurement domain; and

caching an authoritative name server reference for the LDNS server for the vantage point DNS server, the authoritative name server reference for the LDNS server comprising the measurement domain.

10. The method of claim 9, caching comprising:

sending a DNS query to the vantage point DNS server from the measurement client to resolve a name, comprising the measurement domain, claimed under an authority of the LDNS server; and

the measurement domain DNS server responding to the query from the vantage point DNS server with a referral delegating a sub-domain to a mock name server having an IP address of LDNS server.

11. The method of claim 8, determining a delay between LDNS server and the vantage point DNS server comprising filtering out undesirable vantage point DNS servers

12. The method of claim 11, filtering out vantage point DNS servers that are behind forwarders comprising:

the measurement domain server checking if a source address in a query matches to the DNS server;

if no match is found the measurement domain server responding with a referral that comprises a name server identifying that no match was found; and

the measurement client, detecting that no match was found, filtering out the DNS server.

13. The method of claim 11, comprising filtering out retrial DNS servers comprising DNS servers that attempt to contact a measurement domain DNS server after an error message is received.

14. The method of claim 7, grouping target servers into clusters comprising:

identifying a common last hop router for the target servers;

measuring a network delay between the last hop router and a desired number of target servers behind the last hop router; and

clustering target servers based on a network delay threshold value.

15. A method for determining a desired location of one or more data centers based on a delay performance, comprising:

identifying a set of desired vantage point open recursive domain name system (DNS) servers corresponding to a client distribution, comprising;

identifying a set of potential vantage point DNS servers comprising authoritative name servers that correspond to client distribution; and

identifying responsive authoritative name servers from the set of potential vantage point DNS servers comprising identifying authoritative name servers that respond to a trial DNS query;

identifying a set of potential data center locations comprising DNS servers in a data center of a first existing content delivery network (CDN);

determining a delay between the set of potential data center locations and the set of desired vantage point open recursive DNS servers; and

selecting a set of potential data center locations corresponding to a desired delay performance for the client distribution.

16. The method of claim 15, comprising:

identifying a set of a second CDN'"'"'s existing DNS servers collocated with the second CDN'"'"'s content servers serving a vantage point;

determining a delay performance for a set of the second CDN'"'"'s existing DNS servers with respective first CDN'"'"'s existing DNS servers, from the set of a first CDN'"'"'s existing DNS servers collocated with the first CDN'"'"'s content servers serving a vantage point, for the set of desired vantage point open recursive DNS servers;

17. The method of claim 16, selecting a set of potential data center locations comprising:

selecting a new data center location to add to the second existing CDN from a set of potential data center locations based on a desired delay performance determined for the set of the second CDN'"'"'s existing DNS servers with the respective first CDN'"'"'s existing DNS servers, from the set of a first CDN'"'"'s existing DNS servers collocated with the first CDN'"'"'s content servers serving a vantage point; and

if selecting a location for another new data center to add to the second CDN;

adding the selected new data center to the set of the second CDN'"'"'s existing DNS servers collocated with the CDN'"'"'s content servers serving a vantage point; and

determining a delay between the identified set of the first CDN'"'"'s existing DNS servers and the set of desired vantage point open recursive DNS servers.

18. The method of claim 17, if a first CDN comprises an existing DNS server in a same location as a second CDN'"'"'s existing DNS servers collocated with the second CDN'"'"'s content servers, select the existing DNS server from the CDN having a desired delay performance.

19. The method of claim 15, the client distribution comprising a weighted geographic distribution based on an amount of content distribution from a CDN.

20. A method for determining delay performance of an Internet content provider using network latency between a content server in a content delivery network (CDN) and vantage point domain name system (DNS) servers, comprising:

identifying a set of DNS servers for use as vantage points, comprising;

locating DNS servers to use as potential vantage points

identifying responsive authoritative name servers comprising identifying the located DNS servers that respond to a trial DNS query;

identifying a CDN content server serving a vantage point comprising;

identifying a canonical name (CNAME) that resolves to a desired number of CDN servers in a desired geographic region;

sending a query to the DNS server corresponding to a vantage point, the query comprising a DNS query for resolving the identified CNAME; and

retrieving an IP address from the DNS query, the IP address corresponding to a CDN content server used to serve the vantage point DNS server; and

determining a delay between the CDN content server and the vantage point DNS server comprising;

sending a mock DNS query to the vantage point DNS server from a measurement client to resolve a mock name claimed under an authority of the CDN content server;

using a response from the mock DNS query to determine a delay between the measurement client and the CDN content server; and

subtracting a delay between the measurement client and the vantage point DNS server from the delay between the measurement client and the CDN content server.