[189804] in North American Network Operators' Group
Re: Traffic engineering and peering for CDNs
daemon@ATHENA.MIT.EDU (Mark Tinka)
Tue Jun 7 02:46:05 2016
X-Original-To: nanog@nanog.org
To: Tom Smyth <tom.smyth@wirelessconnect.eu>, Mike Hammett <nanog@ics-il.net>
From: Mark Tinka <mark.tinka@seacom.mu>
Date: Tue, 7 Jun 2016 08:46:14 +0200
In-Reply-To: <CAJ3iMJTD9kU0OoJFDVO7PTbsTHn0piABT_bQ1F5OpOTyd9a=gA@mail.gmail.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
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.
