[186801] in North American Network Operators' Group
Re: Another Big day for IPv6 - 10% native penetration
daemon@ATHENA.MIT.EDU (Owen DeLong)
Mon Jan 4 18:36:36 2016
X-Original-To: nanog@nanog.org
From: Owen DeLong <owen@delong.com>
In-Reply-To: <101658.1451945370@turing-police.cc.vt.edu>
Date: Mon, 4 Jan 2016 15:35:05 -0800
To: Valdis.Kletnieks@vt.edu
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
> On Jan 4, 2016, at 14:09 , Valdis.Kletnieks@vt.edu wrote:
>=20
> On Mon, 04 Jan 2016 13:52:46 -0800, Damian Menscher said:
>=20
>> While I agree with your general sentiment about 3xx responses (often =
used
>> to redirect example.com to www.example.com) I think your concerns =
about
>> 8.8.8.8 are over-stated. 8.8.8.8 is deployed in many locations, =
which
>> gives DNS-based geolocation a decent chance of working.
>=20
> So in how many of the 196 or so extant countries does 8.8.8.8 resolve =
to
> a host which, when it sends a query up the chain, appears to be in the
> same country as the machine that made the original query?
>=20
> How does a company know that another instance of 8.8.8.8 has been =
turned up or
> down or re-peered, causing a shift in the mapping of DNS queries to =
countries/
> states?
>=20
>=20
You do realize that the query source address is not 8.8.8.8 when it goes =
to the
authoritative server, right?
The client sees 8.8.8.8. The authoritative server does not.
The query from Google to the authoritative server will come from a =
unique address local to the particular instance.
Owen
