* [email protected] (Dantzig, Brian) [Thu 07 Jan 2021, 18:07 CET]:
When you send a DNS query to 8.8.8.8 it goes to the “nearest”
resolver. Not nearest in terms of location since 8.8.8.8 is an
anycast address and exists in many locations. It’s the BGP path to
8.8.8.8 that determines nearest. Next, the resolver does it’s thing
and sends a query to the akamai DNS. That DNS is probably also an
anycast address so again, how close is it? Akamai then tries to geo
locate you but they have the IP of Google, not you. You get an IP
and connect to that. Everything up till now probably doesn’t matter
as it’s probably not the DNS that is causing what you see. The IP is
not Nike but rather an akamai proxy. When you connect to akamai
proxy, the proxy can see your IP and may do the Geo location lookup
and pass what it thinks as your location to the content server. When
it gets to the content server, it may use that Geo information but
possibly not. It’s likely it’s not the content server but a load
balancer. In either case, they may ignore any Geo lookup done by
akamai and try to locate the incoming IP. Well, that’s actually the
address of the akamai proxy. Hopefully the developers thought of
this and had akamai pass your IP in a header and geo locate on that.
It’s probably the content server that is sending an HTTP redirect to
get you to the “/ca” location on the site.
I checked off list with Becki Kain and Akamai's geolocation is not
placing her in Canada. I can't speculate as to what company Nike would
be using for its decision to redirect to /ca on its website.
-- Niels.
