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