|
Setting ipv6 resolving as preferred
![[dk]](/s/countries/dk.gif) Shadow Hawkins on Thursday, 23 October 2003 16:57:46
Hello,
I'm very proud to have set up ipv6, and I was hoping to get a reward by seeing the dancing turtle at http://www.kame.net/
However, mozilla seems to always resolve www.kame.net's A-record in stead of the AAAA-record. I wonder if I can somehow change the preferred resolving, such that AAAA-records are searched before A-records.
My system is Red Hat 9, updated kernel 2.6.0-test8 and some updated network-related tools.
I've tried setting
options ipv6
in my /etc/resolv.conf, but that doesn't seem to get me a dancing turtle; all it does is to cause seemingly random A-record resolving problems.
(I have found out that I can get a "dancing" Kame turtle by going to http://[2001:200:0:8002:203:47ff:fea5:3085]/ but that's sort of cheating.)
Setting ipv6 resolving as preferred
Mozilla should work, as you say that the, now deprecated, http://[<IPv6>] method works it should work. Does the bottom of this page say that you are using IPv6?
You might want to check:
http://www.ipv6.sixxs.net - IPv6 Only
http://www.ipv4.sixxs.net - IPv4 Only
Check the bottom of the page to see with what you are connecting.
Use the tcpdump etc... maybe Mozilla times out on connecting to http://www.kame.net ?
Setting ipv6 resolving as preferred
Shadow Hawkins on Friday, 24 October 2003 12:55:00
What's the non-deprecated way to access a web-server per IP-address, if http://[ipv6-addr] is deprecated?
Anyways:
On the bottom of this page (https://noc.sixxs.net/forum/?msg=apps-56028-56058&reply=true), it says "SSL IPv6 connection from 2001:960:2:91::2".
About www.kame.net : It's currently down, when I access it on the AAAA address, but it responds when I use its A-address. Strange.
I have no problem accessing http://www.ipv6.sixxs.net/ or http://www.ipv4.sixxs.net/
Setting ipv6 resolving as preferred
![[nl]](/s/countries/nl.gif) Shadow Hawkins on Friday, 24 October 2003 13:10:15
I cant access www.kame.net too. All other ipv6 sites work fine.
# ping6 www.kame.net
PING www.kame.net(orange.kame.net) 56 data bytes
--- www.kame.net ping statistics ---
32 packets transmitted, 0 received, 100% packet loss, time 31000ms
# ping6 2001:200:0:8002:203:47ff:fea5:3085
PING 2001:200:0:8002:203:47ff:fea5:3085(2001:200:0:8002:203:47ff:fea5:3085) 56 data bytes
--- 2001:200:0:8002:203:47ff:fea5:3085 ping statistics ---
9 packets transmitted, 0 received, 100% packet loss, time 8001ms
# traceroute6 www.kame.net
traceroute to orange.kame.net (2001:200:0:8002:203:47ff:fea5:3085) from 2001:838:300:71::2, 30 hops max, 16 byte packets
1 gw-114.ams-01.nl.sixxs.net (2001:838:300:71::1) 26.499 ms 26.991 ms 25.714 ms
2 fe3.ams-ix.ipv6.concepts-ict.net (2001:838:0:1::1) 28.475 ms 26.564 ms 28.295 ms
3 ams-ix.sara.xs4all.net (2001:7f8:1::a500:3265:1) 26.017 ms 24.814 ms 26.407 ms
4 eth10-0-0.xr1.ams1.gblx.net (2001:7f8:1::a500:3549:1) 28.954 ms 24.755 ms 23.703 ms
5 2001:450:1:1::26 (2001:450:1:1::26) 137.569 ms 138.311 ms 137.794 ms
6 3ffe:81d0:ffff:3::2 (3ffe:81d0:ffff:3::2) 333.699 ms 210.514 ms 207.415 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Setting ipv6 resolving as preferred
From the POP:
traceroute to orange.kame.net (2001:200:0:8002:203:47ff:fea5:3085) from 2001:838:0:1:2a0:24ff:feab:3b53,
30 hops max, 16 byte packets
1 fe3.ams-ix.ipv6.concepts-ict.net (2001:838:0:1::1) 0.565 ms 0.525 ms 0.567 ms
2 ams-ix.sara.xs4all.net (2001:7f8:1::a500:3265:1) 0.617 ms 0.562 ms 6.718 ms
3 eth10-0-0.xr1.ams1.gblx.net (2001:7f8:1::a500:3549:1) 2.729 ms 3.477 ms 4.87 ms
4 2001:450:1:1::26 (2001:450:1:1::26) 114.383 ms 112.102 ms 111.816 ms
5 3ffe:81d0:ffff:3::2 (3ffe:81d0:ffff:3::2) 181.675 ms 181.658 ms 183.468 ms
6 3ffe:3900:10::1 (3ffe:3900:10::1) 341.875 ms 342.411 ms 351.244 ms
7 3ffe:3900:1000:1::1 (3ffe:3900:1000:1::1) 344.601 ms 343.628 ms 344.695 ms
8 pc7.otemachi.wide.ad.jp (2001:200:0:1802:2e0:18ff:fe98:a28d) 343.54 ms 342.228 ms 341.237 ms
9 hitachi1.otemachi.wide.ad.jp (2001:200:0:1802:240:66ff:fe10:cf7c) 341.26 ms 342.476 ms 341.738 ms
10 pc3.yagami.wide.ad.jp (2001:200:0:1c04::1000:2000) 342.133 ms 343.588 ms 343.018 ms
11 2001:200:0:8002::2000:1 (2001:200:0:8002::2000:1) 344.416 ms 344.04 ms 343.772 ms
12 2001:200:0:8002:203:47ff:fea5:3085 (2001:200:0:8002:203:47ff:fea5:3085) 343.46 ms 342.684 ms 343.369 ms
Thus it does work, at this moment. Can be any kind of routing problem ofcourse. That box is in japan after all and the route goes crisscross around the world.
|
![[ch]](/s/countries/ch.gif)
on Friday, 24 October 2003 00:30:17
Posting is only allowed when you are