IPv6 at 50% for VZW (Re: NAT IP and Google)

Thu May 29 03:37:07 UTC 2014

On Wed, May 28, 2014 at 3:29 PM, Ryan Rawdon <ryan at u13.net> wrote:

> On May 22, 2014, at 9:18 PM, Matthew Petach <mpetach at netflight.com> wrote:
>
> On Thu, May 22, 2014 at 8:49 AM, Lee Howard <Lee at asgard.org> wrote:
>
>
>
> On 5/22/14 8:04 AM, "Livingood, Jason" <Jason_Livingood at cable.comcast.com>
> wrote:
> [snip]
>
> In his really useful listing of content providers' IPv6 support,
> https://www.vyncke.org/ipv6status/  Eric Vyncke has added "CDN" to sites
> using an identifiable CDN.
>
>
> I suspect there's a problem with
> the data collection on that site;
> looking at
> https://www.vyncke.org/ipv6status/detailed.php?country=us
> I really don't think the top 5 players
> don't support IPv6 DNS queries at all.
> I'd be curious to know more about how the
> data there is collected; I don't see any links
> to any description of the data collection
> methodology on the site.
>
> Matt
>
>
>
> The data is correct — The top 5 players on that page do not have AAAA
> records published for their authoritative name servers (despot all being
> v6-capable for most or all of their content):
>
>
> ryan at lion:~$ echo google.com facebook.com youtube.com yahoo.com
> wikipedia.org | xargs -n1 dig +short -t NS | xargs -n1 dig +short -t AAAA
> ryan at lion:~$
>
> (no results for the authoritative servers of all 5 domains)
>
> ryan at lion:~$ echo google.com facebook.com youtube.com yahoo.com
> wikipedia.org | xargs -n1 dig +short -t NS | xargs -n1 dig +short -t A
> 216.239.34.10
> 216.239.32.10
> 216.239.38.10
> 216.239.36.10
> 69.171.239.12
> 69.171.255.12
> 216.239.38.10
> 216.239.34.10
> 216.239.36.10
> 216.239.32.10
> 68.180.131.16
> 119.160.247.124
> 203.84.221.53
> 68.142.255.16
> 121.101.144.139
> 98.138.11.157
> 91.198.174.239
> 208.80.152.214
> 208.80.154.238
> ryan at lion:~$
>
> (19 A record total results for the 5 domains in question)
>
>
> The same query done together with host(1), excluding various MX responses,
> which would show v6 answers alongside the v4:
> ryan at lion:~$ echo google.com facebook.com youtube.com yahoo.com
> wikipedia.org | xargs -n1 dig +short -t NS | xargs -n1 host | grep -v mail
> ns1.google.com has address 216.239.32.10
> ns2.google.com has address 216.239.34.10
> ns4.google.com has address 216.239.38.10
> ns3.google.com has address 216.239.36.10
> b.ns.facebook.com has address 69.171.255.12
> a.ns.facebook.com has address 69.171.239.12
> ns4.google.com has address 216.239.38.10
> ns2.google.com has address 216.239.34.10
> ns1.google.com has address 216.239.32.10
> ns3.google.com has address 216.239.36.10
> ns5.yahoo.com has address 119.160.247.124
> ns2.yahoo.com has address 68.142.255.16
> ns3.yahoo.com has address 203.84.221.53
> ns1.yahoo.com has address 68.180.131.16
> ns4.yahoo.com has address 98.138.11.157
> ns6.yahoo.com has address 121.101.144.139
> ns0.wikimedia.org has address 208.80.154.238
> ns1.wikimedia.org has address 208.80.152.214
> ns2.wikimedia.org has address 91.198.174.239
> ryan at lion:~$
>
>
Aha!  Thank you for the clarification, Ryan; the
page is somewhat confusing, as it seemed like
it was saying there was no quad-A support from
the DNS servers; but what it's actually saying
is that the DNS servers support IPv6 queries,
but only over IPv4 transport.

Thank you for explaining the methodology
behind the report.  It would definitely be
useful for the site to have a link explaining
the nature of the tests being done, to avoid
similar confusion on the part of others who
see it.

Thanks!

Matt