Issue: Cannot access DNS server nscache.us.sixxs.net. Attempts to resolve names fail. Attempts to resolve names against nscache.us.sixxs.net fail. Attempts to ping6 nscache.us.sixxs.net fail. Other info: yesterday my provider was returning AAAA records for ipv6.google.com. This is no longer occurring. Resolution for yahoo.com works in IPv4 network. User id: PFY3-SIXXS Tunnel id: T59961 email: pfranzek@clearaccess.com Using Linux platform as IPv6 router. Platform is Fedora core 14. Router is connected to an Ethernet Gateway which implements NAT. Ethernet Gateway connects to Cable Modem. Linux Brighton 2.6.35.6-45.fc14.i686 #1 SMP Mon Oct 18 23:56:17 UTC 2010 i686 i686 i386 GNU/Linux Tunnel has been up for over a week. Subnet added yesterday and was operational. Problem discovered this morning at 9AM EDT when ping6 ipv6.google.com failed. This was discovered on a client behind the router. Duplicated the results on the router. The following operations were performed on the router. These operations had succeeded the day before. ping6 ipv6.google.com PING ipv6.google.com(yx-in-x69.1e100.net) 56 data bytes ^C --- ipv6.google.com ping statistics --- 319 packets transmitted, 0 received, 100% packet loss, time 318001ms dig on ipv6.google.com failed: dig @nscache.us.sixxs.net ipv6.google.com AAAA ; <<>> DiG 9.7.2-P2-RedHat-9.7.2-2.P2.fc14 <<>> @nscache.us.sixxs.net ipv6.google.com AAAA ; (2 servers found) dig AAAA nscache.us.sixxs.net ; <<>> DiG 9.7.2-P2-RedHat-9.7.2-2.P2.fc14 <<>> AAAA nscache.us.sixxs.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28006 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;nscache.us.sixxs.net. IN AAAA ;; ANSWER SECTION: nscache.us.sixxs.net. 3600 IN AAAA 2001:4de0:1000:a4::2 nscache.us.sixxs.net. 3600 IN AAAA 2001:4de0:1000:a3::2 ;; Query time: 153 msec ;; SERVER: 192.168.200.1#53(192.168.200.1) ;; WHEN: Fri Mar 18 10:29:48 2011 ;; MSG SIZE rcvd: 94 ping6 of nscache.us.sixxs.net failed: ping6 2001:4de0:1000:a4::2 PING 2001:4de0:1000:a4::2(2001:4de0:1000:a4::2) 56 data bytes ^C --- 2001:4de0:1000:a4::2 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 1999ms ping of tunnel endpoint passed: ping6 2001:4830:1100:12a::1 PING 2001:4830:1100:12a::1(2001:4830:1100:12a::1) 56 data bytes 64 bytes from 2001:4830:1100:12a::1: icmp_seq=1 ttl=64 time=65.9 ms 64 bytes from 2001:4830:1100:12a::1: icmp_seq=2 ttl=64 time=67.1 ms 64 bytes from 2001:4830:1100:12a::1: icmp_seq=3 ttl=64 time=66.4 ms 64 bytes from 2001:4830:1100:12a::1: icmp_seq=4 ttl=64 time=67.0 ms IPv4 network is operational: nslookup yahoo.com Server: 192.168.200.1 Address: 192.168.200.1#53 Non-authoritative answer: Name: yahoo.com Address: 98.137.149.56 Name: yahoo.com Address: 209.191.122.70 Name: yahoo.com Address: 67.195.160.76 Name: yahoo.com Address: 69.147.125.65 Name: yahoo.com Address: 72.30.2.43 ping yahoo.com PING yahoo.com (72.30.2.43) 56(84) bytes of data. 64 bytes from ir1.fp.vip.sk1.yahoo.com (72.30.2.43): icmp_req=1 ttl=52 time=106 ms 64 bytes from ir1.fp.vip.sk1.yahoo.com (72.30.2.43): icmp_req=2 ttl=52 time=84.3 ms AICCU test passed: [root@Brighton pfranzek]# aiccu test Tunnel Information for T59961: POP Id : usbos01 IPv6 Local : 2001:4830:1100:12a::2/64 IPv6 Remote : 2001:4830:1100:12a::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.200.11) ### This should return so called 'echo replies' ### If it doesn't then check your firewall settings ### Your local endpoint should always be pingable ### It could also indicate problems with your IPv4 stack PING 192.168.200.11 (192.168.200.11) 56(84) bytes of data. 64 bytes from 192.168.200.11: icmp_req=1 ttl=64 time=0.092 ms 64 bytes from 192.168.200.11: icmp_req=2 ttl=64 time=0.087 ms 64 bytes from 192.168.200.11: icmp_req=3 ttl=64 time=0.090 ms --- 192.168.200.11 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 0.087/0.089/0.092/0.011 ms ###### Did this work? [Y/n] ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (216.93.250.26) ### These pings should reach the PoP and come back to you ### In case there are problems along the route between your ### host and the PoP this could not return replies ### Check your firewall settings if problems occur PING 216.93.250.26 (216.93.250.26) 56(84) bytes of data. 64 bytes from 216.93.250.26: icmp_req=1 ttl=48 time=85.9 ms 64 bytes from 216.93.250.26: icmp_req=2 ttl=48 time=67.4 ms 64 bytes from 216.93.250.26: icmp_req=3 ttl=48 time=64.4 ms --- 216.93.250.26 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 64.472/72.608/85.936/9.505 ms ###### Did this work? [Y/n] ####### [3/8] Traceroute to the PoP (216.93.250.26) over IPv4 ### This traceroute should reach the PoP ### In case this traceroute fails then you have no connectivity ### to the PoP and this is most probably the problem traceroute to 216.93.250.26 (216.93.250.26), 30 hops max, 60 byte packets 1 ClearView.Home (192.168.200.1) 0.389 ms 0.426 ms 0.519 ms 2 1-60.200-68.tampabay.res.rr.com (68.200.60.1) 19.130 ms 32.999 ms 39.341 ms 3 gig12-0-0-2011.tampfledc-rtr2.tampflrdc.rr.com (65.32.37.238) 17.543 ms 17.822 ms 18.082 ms 4 ge2-2-0.tampfledc-rtr4.tampflrdc.rr.com (65.32.13.66) 18.142 ms 18.356 ms 18.406 ms 5 ae-11-0.cr0.dfw10.tbone.rr.com (66.109.10.12) 41.605 ms 41.427 ms 41.576 ms 6 ae-3-0.pr0.dfw10.tbone.rr.com (66.109.6.209) 47.005 ms 37.882 ms 43.191 ms 7 66.109.11.22 (66.109.11.22) 37.054 ms 35.800 ms 35.399 ms 8 xe-1-1-0.cr2.dfw2.us.above.net (64.125.26.213) 35.705 ms 35.470 ms 35.374 ms 9 xe-4-2-0.cr2.iah1.us.above.net (64.125.31.122) 40.428 ms 41.195 ms 40.933 ms 10 xe-2-1-0.cr2.dca2.us.above.net (64.125.28.49) 58.111 ms 55.389 ms 55.391 ms 11 xe-0-1-0.mpr4.bos2.us.above.net.29.125.64.in-addr.arpa (64.125.29.33) 64.962 ms 64.994 ms 71.345 ms 12 abovenet.ge2-1.ibr01.bos1.twdx.net (64.124.198.45) 71.182 ms 71.737 ms 71.550 ms 13 OCCAID-230.ibr01.bos1.twdx.net (216.93.255.6) 70.354 ms 70.171 ms 70.003 ms 14 usbos01.sixxs.net (216.93.250.26) 71.495 ms 71.624 ms 68.497 ms ###### Did this work? [Y/n] ###### [4/8] Checking if we can ping IPv6 localhost (::1) ### This confirms if your IPv6 is working ### If ::1 doesn't reply then something is wrong with your IPv6 stack PING ::1(::1) 56 data bytes 64 bytes from ::1: icmp_seq=1 ttl=64 time=0.151 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.106 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.120 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 0.106/0.125/0.151/0.022 ms ###### Did this work? [Y/n] ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:4830:1100:12a::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:4830:1100:12a::2(2001:4830:1100:12a::2) 56 data bytes 64 bytes from 2001:4830:1100:12a::2: icmp_seq=1 ttl=64 time=0.110 ms 64 bytes from 2001:4830:1100:12a::2: icmp_seq=2 ttl=64 time=0.115 ms 64 bytes from 2001:4830:1100:12a::2: icmp_seq=3 ttl=64 time=0.110 ms --- 2001:4830:1100:12a::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.110/0.111/0.115/0.012 ms ###### Did this work? [Y/n] ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:4830:1100:12a::1) ### This confirms the reachability of the other side of the tunnel ### If it doesn't reply then check your interface and routing tables ### Don't forget to check your firewall of course ### If the previous test was succesful then this could be both ### a firewalling and a routing/interface problem PING 2001:4830:1100:12a::1(2001:4830:1100:12a::1) 56 data bytes 64 bytes from 2001:4830:1100:12a::1: icmp_seq=1 ttl=64 time=85.5 ms 64 bytes from 2001:4830:1100:12a::1: icmp_seq=2 ttl=64 time=69.1 ms 64 bytes from 2001:4830:1100:12a::1: icmp_seq=3 ttl=64 time=66.5 ms --- 2001:4830:1100:12a::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 66.534/73.735/85.517/8.405 ms ###### Did this work? [Y/n] ###### [7/8] Traceroute6 to the central SixXS machine (noc.sixxs.net) ### This confirms that you can reach the central machine of SixXS ### If that one is reachable you should be able to reach most IPv6 destinations ### Also check http://www.sixxs.net/ipv6calc/ which should show an IPv6 connection ### If your browser supports IPv6 and uses it of course. traceroute to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c), 30 hops max, 80 byte packets 1 gw-299.bos-01.us.sixxs.net (2001:4830:1100:12a::1) 65.806 ms 66.033 ms 75.494 ms 2 bbr01-ve402.bstn01.occaid.net (2001:4830:e1:b::1) 75.450 ms 75.415 ms 75.412 ms 3 bbr01-p1-0.whkn01.occaid.net (2001:4830:ff:15c4::1) 82.807 ms 82.783 ms 82.755 ms 4 bbr01-p2-0.lndn01.occaid.net (2001:4830:fe:1010::1) 153.699 ms 153.760 ms 153.735 ms 5 ge0-1-0-0.er0.thlon.uk.easynet.net (2001:7f8:4::11ed:1) 157.548 ms 154.825 ms 157.343 ms 6 2001:6f8:1::12:1 (2001:6f8:1::12:1) 154.208 ms 149.244 ms 156.273 ms 7 2001:6f8:1::3:2 (2001:6f8:1::3:2) 158.575 ms 158.554 ms 158.539 ms 8 * 2001:6f8:1:0:87:86:77:31 (2001:6f8:1:0:87:86:77:31) 163.171 ms * 9 2001:6f8:1:0:87:86:77:60 (2001:6f8:1:0:87:86:77:60) 163.086 ms * * 10 2001:6f8:1:0:87:86:77:42 (2001:6f8:1:0:87:86:77:42) 165.102 ms * * 11 * 2001:6f8:1:0:87:86:77:56 (2001:6f8:1:0:87:86:77:56) 164.871 ms * 12 2001:6f8:1:0:87:82:50:232 (2001:6f8:1:0:87:82:50:232) 159.596 ms 160.390 ms 160.133 ms 13 2001:838:5:9::2 (2001:838:5:9::2) 161.862 ms 162.005 ms 162.267 ms 14 2001:838:5:8::2 (2001:838:5:8::2) 161.893 ms 162.309 ms 162.321 ms 15 noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) 161.538 ms 161.652 ms 160.198 ms ###### Did this work? [Y/n] ###### [8/8] Traceroute6 to (www.kame.net) ### This confirms that you can reach a Japanese IPv6 destination ### If that one is reachable you should be able to reach most IPv6 destinations ### You should also check http://www.kame.net which should display ### a animated kame (turtle), of course only when your browser supports and uses IPv6 traceroute to www.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 80 byte packets 1 gw-299.bos-01.us.sixxs.net (2001:4830:1100:12a::1) 65.992 ms 65.869 ms 65.769 ms 2 bbr01-ve402.bstn01.occaid.net (2001:4830:e1:b::1) 65.765 ms 71.714 ms 71.707 ms 3 bbr01-p1-0.whkn01.occaid.net (2001:4830:ff:15c4::1) 78.913 ms 78.903 ms 79.034 ms 4 bbr01-g1-0.asbn01.occaid.net (2001:4830:ff:f150::2) 85.489 ms 85.466 ms 85.480 ms 5 xe-0.equinix.asbnva01.us.bb.gin.ntt.net (2001:504:0:2::2914:1) 86.289 ms 86.280 ms 86.572 ms 6 ae-4.r20.snjsca04.us.bb.gin.ntt.net (2001:418:0:2000::266) 179.441 ms 172.355 ms 172.287 ms 7 as-2.r20.tokyjp01.jp.bb.gin.ntt.net (2001:218:0:2000::ce) 297.727 ms as-1.r20.osakjp01.jp.bb.gin.ntt.net (2001:218:0:2000::7e) 284.416 ms as-2.r20.tokyjp01.jp.bb.gin.ntt.net (2001:218:0:2000::ce) 295.143 ms 8 ae-4.r20.tokyjp01.jp.bb.gin.ntt.net (2001:218:0:2000::d9) 293.235 ms ae-1.r24.tokyjp01.jp.bb.gin.ntt.net (2001:218:0:2000::11a) 364.775 ms ae-4.r20.tokyjp01.jp.bb.gin.ntt.net (2001:218:0:2000::d9) 293.566 ms 9 po-1.a15.tokyjp01.jp.ra.gin.ntt.net (2001:218:0:6000::10e) 295.483 ms 295.498 ms 295.561 ms 10 ge-8-2.a15.tokyjp01.jp.ra.gin.ntt.net (2001:218:2000:5000::82) 291.600 ms 291.567 ms 291.553 ms 11 ge-8-2.a15.tokyjp01.jp.ra.gin.ntt.net (2001:218:2000:5000::82) 290.683 ms ve44.foundry6.otemachi.wide.ad.jp (2001:200:0:10::141) 295.372 ms 297.704 ms 12 ve42.foundry4.nezu.wide.ad.jp (2001:200:0:11::66) 302.410 ms ve44.foundry6.otemachi.wide.ad.jp (2001:200:0:10::141) 296.868 ms ve42.foundry4.nezu.wide.ad.jp (2001:200:0:11::66) 302.339 ms 13 ve42.foundry4.nezu.wide.ad.jp (2001:200:0:11::66) 300.752 ms 300.733 ms cloud-net1.wide.ad.jp (2001:200:0:1c0a:218:8bff:fe43:d1d0) 293.311 ms 14 2001:200:dff:fff1:216:3eff:feb1:44d7 (2001:200:dff:fff1:216:3eff:feb1:44d7) 303.210 ms 303.520 ms 303.475 ms ###### Did this work? [Y/n] ###### ACCU Quick Connectivity Test (done) ### Either the above all works and gives no problems ### or it shows you where what goes wrong ### Check the SixXS FAQ (http://www.sixxs.net/faq/ ### for more information and possible solutions or hints ### Don't forget to check the Forums (http://www.sixxs.net/forum/) ### for a helping hand. ### Passing the output of 'aiccu autotest >aiccu.log' is a good idea. *** press a key to continue *** [root@Brighton pfranzek]# aiccu start sock_getline() : "200 SixXS TIC Service on nlams04.sixxs.net ready (http://www.sixxs.net)" sock_printf() : "client TIC/draft-00 AICCU/2007.01.15-console-linux Linux/2.6.35.6-45.fc14.i686" sock_getline() : "200 Client Identity accepted" sock_printf() : "get unixtime" sock_getline() : "200 1300456030" sock_printf() : "starttls" sock_getline() : "400 This service is not SSL enabled (yet)" TIC Server does not support TLS but TLS is not required, continuing sock_printf() : "username PFY3-SIXXS" sock_getline() : "200 PFY3-SIXXS choose your authentication challenge please" sock_printf() : "challenge md5" sock_getline() : "200 f99e4519e8c393d0fc1aa56b07632cb0" sock_printf() : "authenticate md5 4861214d42387c3339acadbdff27b721" sock_getline() : "200 Successfully logged in using md5 as PFY3-SIXXS (Peter Franzek)" sock_printf() : "tunnel show T59961" sock_getline() : "201 Showing tunnel information for T59961" sock_getline() : "TunnelId: T59961" sock_getline() : "Type: ayiya" sock_getline() : "IPv6 Endpoint: 2001:4830:1100:12a::2" sock_getline() : "IPv6 POP: 2001:4830:1100:12a::1" sock_getline() : "IPv6 PrefixLength: 64" sock_getline() : "Tunnel MTU: 1280" sock_getline() : "Tunnel Name: My First Tunnel" sock_getline() : "POP Id: usbos01" sock_getline() : "IPv4 Endpoint: ayiya" sock_getline() : "IPv4 POP: 216.93.250.26" sock_getline() : "UserState: enabled" sock_getline() : "AdminState: enabled" sock_getline() : "Password: [..]" sock_getline() : "Heartbeat_Interval: 60" sock_getline() : "202 Done" Succesfully retrieved tunnel information for T59961 Overriding Local IPv4 address from ayiya to 192.168.200.11 sock_printf() : "QUIT Running Down That Hill" Tunnel Information for T59961: POP Id : usbos01 IPv6 Local : 2001:4830:1100:12a::2/64 IPv6 Remote : 2001:4830:1100:12a::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled [AYIYA-start] : Anything in Anything (draft-02) [AYIYA-tun->tundev] : (Socket to TUN) started Steps taken to rectify issue: Restart Tunnel. Test Tunnel. Restart Router. Restart Ethernet Gateway.