Akamai Edgekey issues ?

Tue Sep 3 13:58:20 UTC 2013

----- Original Message -----
> From: "Matthew Petach" <mpetach at netflight.com>

> On Mon, Sep 2, 2013 at 7:33 PM, Jorge Amodio <jmamodio at gmail.com>
> wrote:
> 
> > Here is another bit of data... www.apple.com not reachable from a
> > machine
> > using Google's NS, reachable from an iPad using TWC NS
> >
> > IP addresses returned by each are different ... could be load
> > balancing, or
> > creative (broken) traffic engineering

> Far more likely to be simply due to Akamai
> localizing the IP addresses to be as "close"
> to the resolving nameserver as possible;
> so, when using Google DNS, you end up
> at an Akamai node "close" to the Google
> DNS server; when using the TWC nameservers,
> you end up pointing to an Akamai node closer
> to those TWC nameservers.
> 
> Not a case of "broken" traffic engineering at all.

Sure it is. 

It's assuming that the geographic location of a customer resolver server
has anything whatever to do with the geographic location of the end node,
which it's not in fact a valid proxy for.

Cheers,
-- jra
-- 
Jay R. Ashworth                  Baylink                       jra at baylink.com
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates     http://baylink.pitas.com         2000 Land Rover DII
St Petersburg FL USA               #natog                      +1 727 647 1274