Another Big day for IPv6 - 10% native penetration

Mon Jan 4 22:48:06 UTC 2016

On Mon, 04 Jan 2016 17:23:20 -0500, Christopher Morrow said:
> https://developers.google.com/speed/public-dns/faq?hl=en
>
> there I asked jeeves for ya!

> > 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?

With 43 subnets for servers and only 13 unique airport codes, the conclusion
is that without additional fun and games, locating based on the DNS for 8.8.8.8
will be incorrect for *most* countries.  Probably gets the continent right.

On Mon, 04 Jan 2016 14:17:56 -0800, Owen DeLong said:
> Further, 8.8.8.8 actually fully supports EDNS0 Client Subnet capability, so
> if the geo-IP balancer in question wants, they can eliminate the failure mode
> you are describing in that case.

Which only helps for people using 8.8.8.8. Client Subnet does help the issue,
but it doesn't actually fix it until support is near ubiquitous across
intermediate nameservers that have clients in other geographic locations...

(I believe that the fact that Google found a need to create EDNS0 Client
Subnet *at all* is proof that using the DNS address for localization is
problematic...)

And again - it's still something that needs work upstream to support, and
you *still* have to deal with the case where the intermediate DNS server
doesn't do Client Subnet.

> I say slightly pessimistic because there arenâ€™t all that many 3XX responses
> being reported.

OK, that's a slightly different kettle of fish :)  To the nearest 10% or
so, how many are answering with a 3xx of any sort?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20160104/486128f6/attachment.sig>