nanog mailing list archives
Re: Traffic engineering and peering for CDNs
From: Mark Tinka <mark.tinka () seacom mu>
Date: Tue, 7 Jun 2016 08:46:14 +0200
On 6/Jun/16 20:03, Tom Smyth wrote:
as far as im aware ... a friend of mine on INEX in Ireland said most cdns use source ip of the DNS requests to determine which network to direct them to ... so if you use you have your own resolver on an ip address in your network range cdns can accurately determine what network the request is comming from and determine what ip address / what network that the cdn has nearest to your network... ff you use 3rd party dns servers for your clients... you may not get an optimal ip answer for your dns queries from the CDNS involved
Some CDN's use DNS (in addition to latency, congestion levels, busy state, e.t.c.). Others use Anycast routing, which I tend to prefer. The problem is the latter run a network while the former may typically not. Mark.
Current thread:
- Traffic engineering and peering for CDNs Graham Johnston (Jun 06)
- Re: Traffic engineering and peering for CDNs Jon Lewis (Jun 06)
- Re: Traffic engineering and peering for CDNs Phil Rosenthal (Jun 06)
- Re: Traffic engineering and peering for CDNs Mike Hammett (Jun 06)
- Re: Traffic engineering and peering for CDNs Tom Smyth (Jun 06)
- Re: Traffic engineering and peering for CDNs Mark Tinka (Jun 06)
- Re: Traffic engineering and peering for CDNs Wolff, Nick (Jun 08)
- Re: Traffic engineering and peering for CDNs Tom Smyth (Jun 06)
- AW: Traffic engineering and peering for CDNs Bernd Spiess (Jun 06)