dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
70
share rss forum feed


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

1 recommendation

reply to aefstoggaflm

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

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!


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

1 recommendation

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