And they want to charge me more for the same running shoes and duty, since they think I'm in Canada. I mean, it's *right* there. I can kayak to Canada but don't buy running shoes š -----Original Message----- From: NANOG <nanog-bounces+bkain1=ford.com@nanog.org> On Behalf Of Christopher Morrow Sent: Wednesday, January 06, 2021 5:00 PM To: William Herrin <bill@herrin.us> Cc: nanog@nanog.org Subject: Re: nike.com->nike.com/ca On Wed, Jan 6, 2021 at 4:52 PM William Herrin <bill@herrin.us> wrote:
On Wed, Jan 6, 2021 at 1:48 PM William Herrin <bill@herrin.us> wrote:
On Wed, Jan 6, 2021 at 1:42 PM Kain, Becki (.) <bkain1@ford.com> wrote:
At home, using 8.8.8.8, if I goto https://clicktime.symantec.com/3Uht9nQajoHJ8ns9Tk5znnb7Vc?u=www.ni ke.com, I get rerouted to nike.com/ca. I cleared the dns cache (Iām running Catalina macos) and rebooted just because. Anyone else seen a weirdism on this? thanks
Welcome to Why You Shouldn't Make Customer-Visible Decisions Based On DNS Resolver Geolocation or DNS Load Balancing Sucks 101.
Nike.com is geolocating the server IP address which requests the web site address. This isn't yours or 8.8.8.8 but instead some unicast IP address to which your 8.8.8.8 packet was routed. Possibly in Canada. Nike appears to think so.
Though I'm probably talking out my tail since this is an HTTP redirect
quite possible' :) (you don't normally, but I think the HTTP thing is the 'gotcha')
which would know your originating IP address (unless you're knowingly or unknowingly using a proxy).
the flow here is PROBABLY: "some dns query which doesn't really matter" by client "some http(s) connect to the server by the client (beki)" "server looks up 'client address' in a 'database of geo ip mapping' and says; "you are in CA(nada) so... 302 /ca pls!" good times! :) (also, typical geo ip problems :( bummer!)
-Bill
-- Hire me! https://clicktime.symantec.com/32qZnFpJTAE5S9HAzgn8RnY7Vc?u=https%3A%2 F%2Fbill.herrin.us%2Fresume%2F