On Tue, 2 Sep 2003, Nenad Pudar wrote:
OK The point is that ipv6 connection is not good enough to be used.
Wrong the v6 connection for your host isn't good enough to use. It works fine from here...
And for the sites that have the same dns for ipv4 and ipv6 ipv6 in a way "blackhole" ipv4 connection.
that's a routing issue for you, not a problem with the dns.
In this case puck.nether.net is timinig out from time to time (going over ipv6) instead of going over ipv4 network.
So really what you want is for you dns resolver to understand the qualitiative differwences between the v6 and v4 paths to the same host, that's seems somewhat unreasonable to expect from the dns.
Joel Jaeggli wrote:
On Tue, 2 Sep 2003, Nenad Pudar wrote:
Jared
Ido not understand what you consider as problem here (the problem is not the latency which is more or less normal thing for ipv6 at this time) "The problem" also showing on you box is that dns6 is resolved first forcing the connection to be ipv6 which is not something that we really want at this stage.
really, why not? I don't know anyone who wants to use v6 only if v4 connection attemts fail.
That is why my point is that at this stage people should not have the same dns for ipv4 and ipv6 site.
Does any body know what is needed in config (resolver library) in order to force the client to look first in dns 4 and not dns6 ?
thanks
nenad
Jared Mauch wrote:
On Tue, Sep 02, 2003 at 11:32:34AM -0400, Nenad Pudar wrote:
Jared
The "problem " with your site is that it has the same dns for ipv4 and ipv6 In may case on dual-stack unix (sun) box dns6 is always resolved first (properly) and then sometimes because of the latency (ipv6) it times out. On the other hand that prevents me from going through ipv4 connection which is good
Sounds like a sun related issue, I'm seeing no problem with my other IPv6 enabled hosts.
eg:
;; Total query time: 166 msec ;; FROM: punk.nether.net to SERVER: puck 2001:418:3f4:0:2a0:24ff:fe83:53d8 ;; WHEN: Tue Sep 2 11:37:44 2003 ;; MSG SIZE sent: 17 rcvd: 509
# getent ipnodes puck.nether.net 2001:418:3f4:0:2a0:24ff:fe83:53d8 puck.nether.net 204.42.254.5 puck.nether.net # traceroute puck.nether.net traceroute: Warning: Multiple interfaces found; using :: @ ? traceroute to puck.nether.net (2001:418:3f4:0:2a0:24ff:fe83:53d8), 30 hops max, 60 byte packets 1 2001:5a0:5000:1:: 2.078 ms 1.316 ms 1.149 ms 2 2001:5a0:8::1 1.648 ms 1.539 ms 1.351 ms 3 viagenie.tu-3.r00.snjsca06.us.b6.verio.net (2001:418:0:4000::26) 34.631 ms 34.674 ms 34.540 ms 4 tu-3.r00.snjsca06.us.b6.verio.net (2001:418:0:4000::25) 122.123 ms * 122.248 ms 5 tu-840.r00.asbnva01.us.b6.verio.net (2001:418:0:2000::22) 184.074 ms 184.211 ms 184.405 ms 6 t2914.nnn-7202.nether.net (2001:418:0:5000::15) 261.417 ms 245.284 ms 233.555 ms 7 2001:418:3f4:0:2a0:24ff:fe83:53d8 224.388 ms 225.100 ms 226.350 ms #
I think everybody should think about using the same dns for ipv4 and ipv6
phat:~> getent ipnodes puck.nether.net. 2001:418:3f4:0:2a0:24ff:fe83:53d8 puck.nether.net 204.42.254.5 puck.nether.net phat:~> traceroute puck.nether.net traceroute: Warning: Multiple interfaces found; using 3ffe:a00:f:4::2 @ le0:1 traceroute to puck.nether.net (2001:418:3f4:0:2a0:24ff:fe83:53d8), 30 hops max, 60 byte packets 1 rtr2-eth1-1.blackrose.org (3ffe:a00:f:4::1) 1.433 ms 1.509 ms 1.318 ms 2 nnn-3640-tu2 (3ffe:a00:f:1::9) 84.991 ms 24.209 ms 12.557 ms 3 2001:418:3f4:0:2a0:24ff:fe83:53d8 12.423 ms 15.002 ms 46.298 ms
nenad
Jared Mauch wrote:
On Fri, Aug 29, 2003 at 05:14:49AM -0500, neal rauhauser wrote:
>I didn't know their NOC number, puck.nether.net is down, normal phone > > > > > > Uh, puck is fine.
http://puck.nether.net/netops/nocs.cgi?ispname=sprint
>channels lead to voicemail jail. Sorry to disturb your morning but its >much easier to complete by 0600 than to have five counties worth of >users dialing a phone right next to where you're working. > > > > > > - Jared
--
Nenad Pudar IP Network Engineer TELEGLOBE phone: 1 514 868 8053
-- -------------------------------------------------------------------------- Joel Jaeggli Unix Consulting joelja@darkwing.uoregon.edu GPG Key Fingerprint: 5C6E 0104 BAF0 40B0 5BD3 C38B F000 35AB B67F 56B2