dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
3748
share rss forum feed


rchandra
Stargate Universe fan
Premium
join:2000-11-09
14225-2105

Actually faster over IPv6, by about 2.5-3x??

Just for grins, I decided to look at »www.youtube.com/my_speed when exploring around YT (right click on a video, select speed test from dropdown menu). While playing the video, I was getting around 10Mb/s through Hurricane Electric. For grins and giggles, I went into Firefox about:config and disabled IPv6 (network.dns.disableIPv6 true) and refreshed. This time, the average speed while playing the video was averaging a lot closer to three!

Just for full disclosure, I have google.com and youtube.com as BIND9 forwarded zones to HE's nameserver. Ergo, lookups under those domains will be recursed to HE, and HE will return AAAA records preferred instead of or in addition to the A records.

It was the last thing I expected, that IPv6 transport would be better...and by over double!

file it under "things that make you go 'hmmmmmm....'"
--
English is a difficult enough language to interpret correctly when its rules are followed, let alone when a writer chooses not to follow those rules.

Jeopardy! replies and randomcaps REALLY suck!



Matt3
All noise, no signal.
Premium
join:2003-07-20
Jamestown, NC
kudos:12

1 recommendation

Very neat. I would be curious to see what an IPv4 and IPv6 trace route shows ... specifically in reference to what provider you enter their network on.

I'd be curious to know if the speed increase was due to their IPv6 provider being less congested, or if they possibly have a set of servers for IPv6 that is less congested.

I'm going to play around also.



rchandra
Stargate Universe fan
Premium
join:2000-11-09
14225-2105

1 recommendation

Hurricane Electric seems to be a fairly substantial provider in and of themselves.

My last kilometer provider is the Buffalo, NY division (or whatever) of Time-Warner.

Actually, it has occurred to me since then (in light of the recent Google Public DNS/OpenDNS announcement) that the YouTube CDN may have handed me an IPv4 address optimized for the HE PoP to which I connect, which is (I think) Ashburn, VA, not my TWC address. I agree though that it would have been an interesting set of statistics if I could have done a traceroute and a traceroute6 to determine the "goodness" of the network connectivity. Higher RTT does not necessarily indicate bandwidth across any given link, but it's a at least somewhat of an indicator.
--
English is a difficult enough language to interpret correctly when its rules are followed, let alone when a writer chooses not to follow those rules.

Jeopardy! replies and randomcaps REALLY suck!



Matt3
All noise, no signal.
Premium
join:2003-07-20
Jamestown, NC
kudos:12

1 recommendation

My IPv6 link is through the HE.net Ashburn pop also.

For the trace route, I wasn't looking for RTT or latency, just what physical path it took. That would have given a clue as to whether you were coming into YouTube's CDN on Level 3, Limelight, etc.



aefstoggaflm
Open Source Fan
Premium
join:2002-03-04
Bethlehem, PA
kudos:3
Reviews:
·PenTeleData
·Verizon Online DSL
reply to Matt3

said by Matt3:

Very neat. I would be curious to see what an IPv4 and IPv6 trace route shows ... specifically in reference to what provider you enter their network on.

You mean like this..

a)

quote:
*@*-desktop:~$ traceroute google.com
traceroute to google.com (74.125.91.104), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 2.697 ms 3.485 ms 3.825 ms
2 L210.PHIL-DSL-RTR11.verizon-gni.net (71.242.247.1) 46.431 ms 47.124 ms 47.948 ms
3 so-0-3-0-0.PHIL-CORE-RTR1.verizon-gni.net (130.81.13.169) 49.159 ms 49.334 ms 50.063 ms
4 so-7-2-0-0.PHIL-BB-RTR1.verizon-gni.net (130.81.20.136) 51.043 ms 51.762 ms 52.633 ms
5 0.xe-3-0-1.XL3.IAD8.ALTER.NET (152.63.3.61) 59.258 ms 0.xe-3-1-0.XL3.IAD8.ALTER.NET (152.63.3.65) 62.320 ms 0.xe-6-1-1.XL3.IAD8.ALTER.NET (152.63.3.245) 60.885 ms
6 TenGigE0-6-0-0.GW7.IAD8.ALTER.NET (152.63.32.190) 63.453 ms TenGigE0-4-0-0.GW7.IAD8.ALTER.NET (152.63.37.150) 49.301 ms 49.175 ms
7 google-gw.customer.alter.net (152.179.50.62) 51.161 ms 51.927 ms 52.754 ms
8 216.239.46.248 (216.239.46.248) 60.724 ms 216.239.46.250 (216.239.46.250) 55.359 ms 216.239.46.248 (216.239.46.248) 60.885 ms
9 209.85.248.73 (209.85.248.73) 65.810 ms 209.85.248.75 (209.85.248.75) 64.966 ms 209.85.248.73 (209.85.248.73) 66.919 ms
10 209.85.254.233 (209.85.254.233) 67.761 ms 80.899 ms 209.85.254.237 (209.85.254.237) 66.534 ms
11 * 209.85.240.53 (209.85.240.53) 75.784 ms 63.434 ms
12 qy-in-f104.1e100.net (74.125.91.104) 57.505 ms 58.549 ms 58.924 ms
*@*-desktop:~$


b)

quote:
*@*-desktop:~$ traceroute ipv6.google.com
traceroute to ipv6.google.com (2001:4860:b009::63), 30 hops max, 80 byte packets
1 gw-298.bos-01.us.sixxs.net (2001:4830:1100:129::1) 59.155 ms 61.376 ms 65.594 ms
2 bbr01-ve402.bstn01.occaid.net (2001:4830:e1:b::1) 71.837 ms 71.095 ms 71.275 ms
3 bbr01-p1-0.whkn01.occaid.net (2001:4830:ff:15c4::1) 77.426 ms 77.573 ms 77.657 ms
4 bbr01-g1-0.asbn01.occaid.net (2001:4830:ff:f150::2) 85.631 ms 86.846 ms 88.180 ms
5 pr61.iad07.net.google.com (2001:504:0:2:0:1:5169:1) 90.503 ms 91.664 ms 93.442 ms
6 2001:4860::1:0:5dc (2001:4860::1:0:5dc) 95.592 ms 76.787 ms 2001:4860::1:0:9ff (2001:4860::1:0:9ff) 74.341 ms
7 2001:4860::1:0:613 (2001:4860::1:0:613) 82.824 ms 84.731 ms 88.807 ms
8 2001:4860::2:0:618 (2001:4860::2:0:618) 101.372 ms 2001:4860::2:0:617 (2001:4860::2:0:617) 98.679 ms 2001:4860::2:0:618 (2001:4860::2:0:618) 95.259 ms
9 2001:4860:0:1::33 (2001:4860:0:1::33) 96.058 ms 95.224 ms 95.986 ms
10 qy-in-x63.1e100.net (2001:4860:b009::63) 96.147 ms 96.087 ms 96.417 ms
*@*-desktop:~$

--
Please use the "yellow (IM) envelope" to contact me and please leave the URL intact.


Matt3
All noise, no signal.
Premium
join:2003-07-20
Jamestown, NC
kudos:12

Yep, but to youtube.com.



aefstoggaflm
Open Source Fan
Premium
join:2002-03-04
Bethlehem, PA
kudos:3
Reviews:
·PenTeleData
·Verizon Online DSL

While I am not the OP, this what I got..

IPv4

quote:
*@*-desktop:~$ traceroute youtube.com
traceroute to youtube.com (64.233.169.136), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 1.260 ms 1.685 ms 2.024 ms
2 L210.PHIL-DSL-RTR11.verizon-gni.net (71.242.247.1) 44.919 ms 45.178 ms 45.930 ms
3 so-0-3-0-0.PHIL-CORE-RTR2.verizon-gni.net (130.81.13.173) 47.131 ms 48.129 ms 48.766 ms
4 so-7-2-0-0.PHIL-BB-RTR2.verizon-gni.net (130.81.20.138) 49.783 ms 50.062 ms 51.102 ms
5 0.xe-3-0-1.XL4.IAD8.ALTER.NET (152.63.3.69) 58.694 ms 59.700 ms 0.xe-3-0-2.XL4.IAD8.ALTER.NET (152.63.3.57) 59.167 ms
6 0.so-1-0-1.XL4.NYC4.ALTER.NET (152.63.1.170) 64.021 ms 0.xe-2-1-2.XL4.NYC4.ALTER.NET (152.63.4.50) 106.362 ms 106.480 ms
7 TenGigE0-7-0-0.GW8.NYC4.ALTER.NET (152.63.22.45) 55.615 ms TenGigE0-7-4-0.GW8.NYC4.ALTER.NET (152.63.21.133) 53.712 ms TenGigE0-5-1-0.GW8.NYC4.ALTER.NET (152.63.21.73) 54.437 ms
8 Internet-gw.customer.alter.net (152.179.72.66) 53.884 ms 54.572 ms 54.922 ms
9 216.239.43.114 (216.239.43.114) 83.919 ms 57.521 ms 209.85.252.215 (209.85.252.215) 58.343 ms
10 209.85.252.2 (209.85.252.2) 63.751 ms 209.85.251.37 (209.85.251.37) 60.396 ms 209.85.252.2 (209.85.252.2) 64.096 ms
11 209.85.249.11 (209.85.249.11) 68.457 ms 66.511 ms 57.083 ms
12 72.14.236.200 (72.14.236.200) 58.095 ms 64.233.175.111 (64.233.175.111) 58.471 ms 72.14.236.200 (72.14.236.200) 58.482 ms
13 216.239.49.149 (216.239.49.149) 68.081 ms 68.370 ms 72.14.232.21 (72.14.232.21) 67.426 ms
14 yo-in-f136.1e100.net (64.233.169.136) 60.366 ms 61.960 ms 62.174 ms
*@*-desktop:~$

Tried IPv6, but got back
quote:
*@*-desktop:~$ traceroute -6 youtube.com
youtube.com: No address associated with hostname
Cannot handle "host" cmdline arg `youtube.com' on position 1 (argc 2)
*@*-desktop:~$ traceroute-6 youtube.com
No command 'traceroute-6' found, did you mean:
Command 'traceroute6' from package 'iputils-tracepath' (main)
Command 'traceroute6' from package 'traceroute' (main)
Command 'traceroute6' from package 'ndisc6' (universe)
traceroute-6: command not found
*@*-desktop:~$ traceroute6 youtube.com
youtube.com: No address associated with hostname
Cannot handle "host" cmdline arg `youtube.com' on position 1 (argc 1)
*@*-desktop:~$ traceroute6 ipv6.google.com
traceroute to ipv6.google.com (2001:4860:b009::69), 30 hops max, 80 byte packets
1 gw-298.bos-01.us.sixxs.net (2001:4830:1100:129::1) 60.047 ms 60.981 ms 62.616 ms
2 bbr01-ve402.bstn01.occaid.net (2001:4830:e1:b::1) 64.405 ms 64.863 ms 63.973 ms
3 bbr01-p1-0.nwrk01.occaid.net (2001:4830:ff:15c4::1) 72.361 ms 73.474 ms 74.994 ms
4 bbr01-g1-0.asbn01.occaid.net (2001:4830:ff:f150::2) 81.896 ms 83.432 ms 84.964 ms
5 * * *
6 2001:4860::1:0:5dc (2001:4860::1:0:5dc) 86.467 ms 2001:4860::1:0:9ff (2001:4860::1:0:9ff) 215.419 ms 77.466 ms
7 2001:4860::1:0:613 (2001:4860::1:0:613) 83.948 ms 94.202 ms 95.131 ms
8 2001:4860::2:0:618 (2001:4860::2:0:618) 90.124 ms 2001:4860::2:0:617 (2001:4860::2:0:617) 91.172 ms 92.364 ms
9 2001:4860:0:1::33 (2001:4860:0:1::33) 100.751 ms 101.123 ms 101.644 ms
10 qy-in-x69.1e100.net (2001:4860:b009::69) 98.271 ms 99.691 ms 101.537 ms
*@*-desktop:~$

^^^
--
Please use the "yellow (IM) envelope" to contact me and please leave the URL intact.


Matt3
All noise, no signal.
Premium
join:2003-07-20
Jamestown, NC
kudos:12
reply to rchandra

Click for full size
It looks like he.net has direct peering with Google via IPv6, at least in certain locations. Not surprising really.

That would explain the speed difference.


rchandra
Stargate Universe fan
Premium
join:2000-11-09
14225-2105

1 recommendation

reply to aefstoggaflm

You would have to be querying a Google IPv6 partner (such as HE) to obtain an IPv6 address for youtube.com (or any other Google property). For example, for BIND9:


# HE DNS server for google IPv6 service

zone "google.com" IN {
type forward;
forward first;
forwarders {
2001:470:20::2;
74.82.42.42;
};
};

zone "youtube.com" IN {
type forward;
forward first;
forwarders {
2001:470:20::2;
74.82.42.42;
};
};
You could of course do all your recursion through HE if you wanted; they'll allow that for their tunnelbroker.net 6in4 customers (participants?).

--
English is a difficult enough language to interpret correctly when its rules are followed, let alone when a writer chooses not to follow those rules.

Jeopardy! replies and randomcaps REALLY suck!


rchandra
Stargate Universe fan
Premium
join:2000-11-09
14225-2105
reply to Matt3


1 14:08:45 rchandra@sal9000:/ 0> traceroute youtube.com
traceroute to youtube.com (64.233.169.190), 30 hops max, 40 byte packets
1 rootin.local.ether (192.168.1.21) 1.160 ms 1.257 ms 1.471 ms
2 cable-mac1.wsvlnywf-ar4002.nyroc.rr.com (67.246.160.1) 30.801 ms 31.774 ms 48.994 m s
3 gig2-2-5.buffnyamh-pe01.nyroc.rr.com (98.0.2.93) 35.077 ms 36.054 ms 36.156 ms
4 ae3-0.lkwnnyad-rtr001.nyroc.rr.com (98.0.3.16) 32.634 ms 33.611 ms 33.699 ms
5 ae6-0.vstlny11-rtr000.nyroc.rr.com (98.0.3.5) 38.550 ms 39.527 ms 39.629 ms
6 ae1-0.albynyyf-rtr000.nyroc.rr.com (24.24.21.208) 43.719 ms 34.936 ms 35.946 ms
7 ae-5-0.cr0.nyc30.tbone.rr.com (66.109.6.74) 43.042 ms 107.14.19.26 (107.14.19.26) 46 .846 ms 53.926 ms
8 ae-0-0.cr0.nyc30.tbone.rr.com (66.109.6.26) 65.385 ms 61.607 ms 62.462 ms
9 66.109.9.30 (66.109.9.30) 60.192 ms 89.282 ms ae-4-0.cr0.dca20.tbone.rr.com (66.109. 6.28) 93.623 ms
10 ae-1-0.pr0.dca10.tbone.rr.com (66.109.6.165) 66.376 ms 67.605 ms 107.14.19.135 (107. 14.19.135) 67.358 ms
11 74.125.49.181 (74.125.49.181) 87.254 ms 88.232 ms 88.094 ms
12 216.239.48.112 (216.239.48.112) 68.434 ms 68.285 ms 216.239.48.108 (216.239.48.108) 34.874 ms
13 64.233.175.109 (64.233.175.109) 40.583 ms 64.233.175.111 (64.233.175.111) 40.791 ms 72.14.236.200 (72.14.236.200) 39.279 ms
14 72.14.232.25 (72.14.232.25) 48.370 ms 216.239.49.149 (216.239.49.149) 51.086 ms 51. 937 ms
15 yo-in-f190.1e100.net (64.233.169.190) 40.790 ms 40.142 ms 45.366 ms
1 14:08:59 rchandra@sal9000:/ 0> traceroute6 youtube.com
traceroute to youtube.com (2607:f8b0:4002:c00::5d), 30 hops max, 40 byte packets
1 rootinv6.local.ether (2001:470:e107:2001::21) 0.410 ms 0.492 ms 0.840 ms
2 rchandra-1.tunnel.tserv13.ash1.ipv6.he.net (2001:470:7:520::1) 40.046 ms 49.057 ms 51.529 ms
3 gige-g4-12.core1.ash1.he.net (2001:470:0:90::1) 53.017 ms 53.113 ms 53.082 ms
4 pr61.iad07.net.google.com (2001:504:0:2:0:1:5169:1) 53.556 ms 54.787 ms 54.889 ms
5 2001:4860::1:0:5dc (2001:4860::1:0:5dc) 54.876 ms 47.237 ms 2001:4860::1:0:9ff (2001 :4860::1:0:9ff) 250.966 ms
6 2001:4860::2:0:c3 (2001:4860::2:0:c3) 52.804 ms 45.933 ms 2001:4860::2:0:b3 (2001:48 60::2:0:b3) 48.632 ms
7 2001:4860:0:1::2db (2001:4860:0:1::2db) 48.492 ms 37.707 ms 2001:4860:0:1::2d9 (2001 :4860:0:1::2d9) 42.357 ms
8 yo-in-x5d.1e100.net (2607:f8b0:4002:c00::5d) 41.567 ms 40.182 ms 41.780 ms
1 14:09:41 rchandra@sal9000:/ 0>


--
English is a difficult enough language to interpret correctly when its rules are followed, let alone when a writer chooses not to follow those rules.

Jeopardy! replies and randomcaps REALLY suck!


Matt3
All noise, no signal.
Premium
join:2003-07-20
Jamestown, NC
kudos:12

1 recommendation

reply to rchandra

said by rchandra:

You would have to be querying a Google IPv6 partner (such as HE) to obtain an IPv6 address for youtube.com (or any other Google property).

Very good point, if you're not using an IPv6 "partner" DNS server, you won't receive the proper AAAA addresses.

said by »www.google.com/intl/en/ipv6/ :
Google over IPv6 uses the IPv4 address of your DNS resolver to determine whether a network is IPv6-capable. If you enable Google over IPv6 for your resolver, IPv6 users of that resolver will receive AAAA records for IPv6-enabled Google services.
I have found the HE.net IPv6 caching resolver to be terribly slow however. Have you noticed this or was it perhaps just a blip the day I tested it?

If you use Google Public DNS (they offer IPv4 and IPv6 addressing, »code.google.com/speed/public-dns···ing.html) you will get the addressing as well.

I use Google Public DNS and OpenDNS in both IPv4 and IPv6 mode as primary and secondary.

OpenDNS offers IPv6 servers here: »www.opendns.com/ipv6/


rchandra
Stargate Universe fan
Premium
join:2000-11-09
14225-2105

1 recommendation

said by Matt3:

said by rchandra:

You would have to be querying a Google IPv6 partner (such as HE) to obtain an IPv6 address for youtube.com (or any other Google property).

Very good point, if you're not using an IPv6 "partner" DNS server, you won't receive the proper AAAA addresses.
.
.
.
I have found the HE.net IPv6 caching resolver to be terribly slow however. Have you noticed this or was it perhaps just a blip the day I tested it?

Oh, idunno...seems OK to me. But then again, I'm not using them for recursive services, just the forwarded zones.

said by Matt3:

If you use Google Public DNS (they offer IPv4 and IPv6 addressing, »code.google.com/speed/public-dns···ing.html) you will get the addressing as well.

Don't think so...

6 14:59:50 rchandra@sal9000:~ 0> host -v -t aaaa google.com 8.8.8.8
Trying "google.com"
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7955
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;google.com. IN AAAA

;; AUTHORITY SECTION:
google.com. 590 IN SOA ns1.google.com. dns-admin.google.com. 1461 099 7200 1800 1209600 300

Received 78 bytes from 8.8.8.8#53 in 39 ms
6 14:59:52 rchandra@sal9000:~ 0> host -v -t aaaa google.com 2001:4860:4860::8888
Trying "google.com"
Using domain server:
Name: 2001:4860:4860::8888
Address: 2001:4860:4860::8888#53
Aliases:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7392
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;google.com. IN AAAA

;; AUTHORITY SECTION:
google.com. 519 IN SOA ns1.google.com. dns-admin.google.com. 1461 099 7200 1800 1209600 300

Received 78 bytes from 2001:4860:4860::8888#53 in 56 ms
6 15:00:04 rchandra@sal9000:~ 0> host -v -t aaaa www.google.com 8.8.8.8
Trying "www.google.com"
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59544
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;www.google.com. IN AAAA

;; ANSWER SECTION:
www.google.com. 86399 IN CNAME www.l.google.com.

;; AUTHORITY SECTION:
l.google.com. 600 IN SOA ns1.google.com. dns-admin.google.com. 1461 099 900 900 1800 60

Received 102 bytes from 8.8.8.8#53 in 144 ms
6 15:00:13 rchandra@sal9000:~ 0> host -v -t aaaa www.l.google.com 8.8.8.8
Trying "www.l.google.com"
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33142
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;www.l.google.com. IN AAAA

;; AUTHORITY SECTION:
l.google.com. 600 IN SOA ns3.google.com. dns-admin.google.com. 1461 100 900 900 1800 60

Received 84 bytes from 8.8.8.8#53 in 64 ms
6 15:00:22 rchandra@sal9000:~ 0>

Maybe there's a flaw in my methodology, but I think when one queries for a particular RR type (such as AAAA), and one gets back an SOA record (instead of said record type), it means there are RRs for that name, but not of the type requested. The other result is NXDOMAIN, which didn't occur for me.

--
English is a difficult enough language to interpret correctly when its rules are followed, let alone when a writer chooses not to follow those rules.

Jeopardy! replies and randomcaps REALLY suck!


Matt3
All noise, no signal.
Premium
join:2003-07-20
Jamestown, NC
kudos:12

1 recommendation

said by rchandra:

said by Matt3:

If you use Google Public DNS (they offer IPv4 and IPv6 addressing, »code.google.com/speed/public-dns···ing.html) you will get the addressing as well.

Don't think so...

Google Public DNS works for me, however you prompted me to test OpenDNS and it in fact, does not. OpenDNS only returns AAAA records when querying their IPv6 server directly.

Google Public DNS IPv4:
C:\Users\Matt>nslookup -q=aaaa www.google.com 8.8.8.8
Server:  google-public-dns-a.google.com
Address:  8.8.8.8
 
Name:    www.google.com
 

OpenDNS IPv4:
C:\Users\Matt>nslookup -q=aaaa www.google.com 208.67.222.222
Server:  resolver1.opendns.com
Address:  208.67.222.222
 
*** No IPv6 address (AAAA) records available for www.google.com
 

Google Public DNS IPv6:
C:\Users\Matt>nslookup -q=aaaa www.google.com 2001:4860:4860::8888
Server:  google-public-dns-a.google.com
Address:  2001:4860:4860::8888
 
Name:    www.google.com
 

OpenDNS IPv6:
C:\Users\Matt>nslookup -q=aaaa www.google.com 2620:0:ccc::2
Server:  UnKnown
Address:  2620:0:ccc::2
 
Non-authoritative answer:
Name:    www.google.com
 


rchandra
Stargate Universe fan
Premium
join:2000-11-09
14225-2105

right...if you would turn on Windows' nslookup's debug and/or d2 flags, you would probably see that lack of response (as printed by the default settings) is actually returning an SOA RR. As it is, you're just getting "Name: www.google.com" printed, no IPv6 address. That's the same sort of thing my host(1) will do w/o the -verbose flag.

I cannot directly explain why OpenDNS is telling you different results depending on whether you query via v4 or v6, and it looks like they're not telling you the correct results. From the output you show, it's/they're returning NXDOMAIN (which is not true, which is what I would gather is what "*** No IPv6 address (AAAA) records available for www.google.com" means) instead of an SOA. (wellll...put it this way...I'm not a DNS RFC hound, I'm just going from previous nslookup/host/dig usage and results experience. So take these comments with a grain of salt.)

The only way you may have gotten AAAAs from GoogPubDNS w/o querying a partner such as HE is to have done it on World IPv6 Day.

I'm sure it's not too tough to find; I read Google's page once on applying to be allowed to get their AAAAs through recursive queries to a partner's server.
--
English is a difficult enough language to interpret correctly when its rules are followed, let alone when a writer chooses not to follow those rules.

Jeopardy! replies and randomcaps REALLY suck!



Matt3
All noise, no signal.
Premium
join:2003-07-20
Jamestown, NC
kudos:12

said by rchandra:

right...if you would turn on Windows' nslookup's debug and/or d2 flags, you would probably see that lack of response (as printed by the default settings) is actually returning an SOA RR. As it is, you're just getting "Name: www.google.com" printed, no IPv6 address. That's the same sort of thing my host(1) will do w/o the -verbose flag.

I cannot directly explain why OpenDNS is telling you different results depending on whether you query via v4 or v6, and it looks like they're not telling you the correct results. From the output you show, it's/they're returning NXDOMAIN (which is not true, which is what I would gather is what "*** No IPv6 address (AAAA) records available for www.google.com" means) instead of an SOA. (wellll...put it this way...I'm not a DNS RFC hound, I'm just going from previous nslookup/host/dig usage and results experience. So take these comments with a grain of salt.)

The only way you may have gotten AAAAs from GoogPubDNS w/o querying a partner such as HE is to have done it on World IPv6 Day.

I'm sure it's not too tough to find; I read Google's page once on applying to be allowed to get their AAAAs through recursive queries to a partner's server.

Yep, you are correct. I was mistaking the same nslookup output behavior under IPv4 and IPv6 as evidence that Google Public DNS was returning the same results. Now that you mention it, just returning the name does look weird.

When running the same nslookup query through the he.net server, a proper IPv6 address in addition to the name is returned.

C:\Users\Matt>nslookup -q=aaaa www.google.com. 2001:470:20::2
Server:  ordns.he.net
Address:  2001:470:20::2
 
Name:    www.l.google.com
Address:  2001:4860:800f::68
Aliases:  www.google.com