On Thu, 29 Jul 2010, Nicholas Weaver wrote:
Could someone with a IPv6 connected recursive resolver do a favor for
me?
Validate that
ipv6_dns.eaoe.n1.netalyzr.icsi.berkeley.edu
resolves to
67.202.37.63
host ipv6_dns.eaoe.n1.netalyzr.icsi.berkeley.edu
* Nicholas Weaver
> Actually, thats not unexpected: roland is V4 only, but the after
> is V6, so dig -6 is wrong
Well, you did ask for a v6-connected recursive resolver so I checked it
from a single-stack one. (It fails without the "-6" as well.)
But I suppose the answer you're after is in
Actually, thats not unexpected: roland is V4 only, but the after is V6, so
dig -6 is wrong (just dig on a v6 machine works, the name can't resolve if you
are V6 only as our primary DNS server is V4 only):
dig +trace ipv6_dns.eaoe.n1.netalyzr.icsi.berkeley.edu
; <<>> DiG 9.7.1-P2-RedHat-9
* Nicholas Weaver
> Could someone with a IPv6 connected recursive resolver do a favor for
> me?
>
> Validate that
>
> ipv6_dns.eaoe.n1.netalyzr.icsi.berkeley.edu
>
> resolves to
>
> 67.202.37.63
Hi Nicholas.
It doesn't work, the delegation chain stops at roland
Could someone with a IPv6 connected recursive resolver do a favor for
me?
Validate that
ipv6_dns.eaoe.n1.netalyzr.icsi.berkeley.edu
resolves to
67.202.37.63
(this is a new test name being integrated into Netalyzr, where the only
authority reco
