Windows 7 DNS doesn't work
Shadow Hawkins on Monday, 25 January 2010 23:44:04
Hey everyone. I've tried to install IPv6 on my Windows 7 x64 computer, but so far I'm not having much luck.
This is the auto-test data from AICCU:
C:\>aiccu-2008-03-15-windows-console.exe autotest
sock_getline() : "200 SixXS TIC Service on noc.sixxs.net ready (http://www.sixx
.net)"
sock_printf() : "client TIC/draft-00 AICCU/2008.03.15-console-win32 WinNT/6.1.
600"
sock_getline() : "200 Client Identity accepted"
sock_printf() : "get unixtime"
sock_getline() : "200 1264458799"
sock_printf() : "username XXXX-SIXXS"
sock_getline() : "200 Choose your authentication challenge please"
sock_printf() : "challenge md5"
sock_getline() : "200 XXXX"
sock_printf() : "authenticate md5 XXXX
sock_getline() : "200 Succesfully logged in using md5 as XXXX-SIXXS (XXXX
) from 2001:960:800::2"
sock_printf() : "tunnel show T25035"
sock_getline() : "201 Showing tunnel information for T25035"
sock_getline() : "TunnelId: T25035"
sock_getline() : "Type: ayiya"
sock_getline() : "IPv6 Endpoint: 2001:610:600:63a::2"
sock_getline() : "IPv6 POP: 2001:610:600:63a::1"
sock_getline() : "IPv6 PrefixLength: 64"
sock_getline() : "Tunnel MTU: 1280"
sock_getline() : "Tunnel Name: My First Tunnel"
sock_getline() : "POP Id: nlams05"
sock_getline() : "IPv4 Endpoint: ayiya"
sock_getline() : "IPv4 POP: 192.87.102.107"
sock_getline() : "UserState: enabled"
sock_getline() : "AdminState: enabled"
sock_getline() : "Password: XXXX"
sock_getline() : "Heartbeat_Interval: 60"
sock_getline() : "202 Done"
Succesfully retrieved tunnel information for T25035
sock_printf() : "QUIT We will be the only two people left in the world, Yes--A
am and Evil!"
Tunnel Information for T25035:
PoP Id : nlams05
IPv6 Local : 2001:610:600:63a::2/64
IPv6 Remote : 2001:610:600:63a::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
Name : My First Tunnel
Flag: HAS_IFHEAD not present
Flag: NEED_IFHEAD not present
[warning] Error opening registry key: SYSTEM\CurrentControlSet\Control\Class\{4
36E972-E325-11CE-BFC1-08002BE10318}\Properties (t1)
Found interface named 'aiccu', with guid {C06C077A-DB7F-4685-A50A-1C4E12FDE787}
using it
[tun-start] Trying \\.\Global\{C06C077A-DB7F-4685-A50A-1C4E12FDE787}.tap
Flag: HAS_IFHEAD not present
Flag: NEED_IFHEAD not present
[AYIYA-start] : Anything in Anything (draft-02)
heartbeat_socket() - IPv4 : 192.168.1.13
#######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.1.13)
### 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
[AYIYA-tun->tundev] : (Socket to TUN) started
Pinging 192.168.1.13 with 32 bytes of data:
Reply from 192.168.1.13: bytes=32 time<1ms TTL=128
Reply from 192.168.1.13: bytes=32 time<1ms TTL=128
Reply from 192.168.1.13: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.1.13:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
######
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (192.87.102.107)
### 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
Pinging 192.87.102.107 with 32 bytes of data:
Reply from 192.87.102.107: bytes=32 time=11ms TTL=55
Reply from 192.87.102.107: bytes=32 time=12ms TTL=55
Reply from 192.87.102.107: bytes=32 time=11ms TTL=55
Ping statistics for 192.87.102.107:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 12ms, Average = 11ms
######
####### [3/8] Traceroute to the PoP (192.87.102.107) 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
Tracing route to 192.87.102.107 over a maximum of 30 hops
1 2 ms 2 ms 1 ms openrg.home [192.168.1.1]
2 18 ms 11 ms 11 ms 81.71.128.1
3 15 ms 11 ms 11 ms 194.134.187.52
4 12 ms 11 ms 11 ms 194.134.161.12
5 11 ms * 12 ms 194.134.161.11
6 12 ms 12 ms 12 ms 195.69.144.34
7 43 ms 12 ms 12 ms 145.145.80.70
8 12 ms 12 ms 15 ms 145.145.19.170
9 13 ms 12 ms 13 ms 192.87.102.107
Trace complete.
######
###### [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
Pinging ::1 with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Ping statistics for ::1:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
######
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:610:600:63a::2
)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
Pinging 2001:610:600:63a::2 with 32 bytes of data:
Reply from 2001:610:600:63a::2: time<1ms
Reply from 2001:610:600:63a::2: time<1ms
Reply from 2001:610:600:63a::2: time<1ms
Ping statistics for 2001:610:600:63a::2:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
######
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:610:600:63a::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 (both IPv4 and IPv6) of course
### If the previous test was succesful then this could be both
### a firewalling and a routing/interface problem
Pinging 2001:610:600:63a::1 with 32 bytes of data:
Reply from 2001:610:600:63a::1: time=13ms
Reply from 2001:610:600:63a::1: time=12ms
Reply from 2001:610:600:63a::1: time=12ms
Ping statistics for 2001:610:600:63a::1:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 13ms, Average = 12ms
######
###### [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 connecti
on
### If your browser supports IPv6 and uses it of course.
'tracert6' is not recognized as an internal or external command,
operable program or batch file.
######
###### [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
'tracert6' is not recognized as an internal or external command,
operable program or batch file.
######
###### 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.
As you can see, everything looks fine, but as soon as I'm trying to lookup some DNS records I get this:
C:\>nslookup -type=AAAA www.ipv6.sixxs.net
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 192.168.1.1
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
Any other data that might help:
C:\>netsh int ipv6 show address
Interface 1: Loopback Pseudo-Interface 1
Addr Type DAD State Valid Life Pref. Life Address
--------- ----------- ---------- ---------- ------------------------
Other Preferred infinite infinite ::1
Interface 12: Wireless Network Connection
Addr Type DAD State Valid Life Pref. Life Address
--------- ----------- ---------- ---------- ------------------------
Manual Preferred infinite infinite 2002:81a8:102::
Other Preferred infinite infinite fe80::642c:15f5:a2c1:597f%12
Interface 11: Local Area Connection
Addr Type DAD State Valid Life Pref. Life Address
--------- ----------- ---------- ---------- ------------------------
Other Deprecated infinite infinite fe80::101a:8195:c914:c70f%11
Interface 25: Bluetooth Network Connection 2
Addr Type DAD State Valid Life Pref. Life Address
--------- ----------- ---------- ---------- ------------------------
Other Deprecated infinite infinite fe80::a848:c5d9:5a8e:a3ec%25
Interface 26: aiccu
Addr Type DAD State Valid Life Pref. Life Address
--------- ----------- ---------- ---------- ------------------------
Manual Preferred infinite infinite 2001:610:600:63a::2
Other Preferred infinite infinite fe80::35ef:a053:82e1:68c7%26
---
C:\>netsh int ipv6 show route
Publish Type Met Prefix Idx Gateway/Interface Name
------- -------- --- ------------------------ --- ------------------------
No Manual 256 ::/0 26 2001:610:600:63a::1
No Manual 256 ::1/128 1 Loopback Pseudo-Interface
1
No Manual 256 2001:610:600:63a::/64 26 aiccu
No Manual 256 2001:610:600:63a::2/128 26 aiccu
No Manual 256 2002:81a8:102::/64 12 Wireless Network Connecti
on
No Manual 256 2002:81a8:102::/128 12 Wireless Network Connecti
on
No Manual 256 fe80::/64 11 Local Area Connection
No Manual 256 fe80::/64 25 Bluetooth Network Connect
ion 2
No Manual 256 fe80::/64 12 Wireless Network Connecti
on
No Manual 256 fe80::/64 26 aiccu
No Manual 256 fe80::101a:8195:c914:c70f/128 11 Local Area Connectio
n
No Manual 256 fe80::35ef:a053:82e1:68c7/128 26 aiccu
No Manual 256 fe80::642c:15f5:a2c1:597f/128 12 Wireless Network Con
nection
No Manual 256 fe80::a848:c5d9:5a8e:a3ec/128 25 Bluetooth Network Co
nnection 2
No Manual 256 ff00::/8 1 Loopback Pseudo-Interface
1
No Manual 256 ff00::/8 11 Local Area Connection
No Manual 256 ff00::/8 25 Bluetooth Network Connect
ion 2
No Manual 256 ff00::/8 12 Wireless Network Connecti
on
No Manual 256 ff00::/8 26 aiccu
---
C:\>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : Penryn
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : home
Ethernet adapter aiccu:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Win32 Adapter V9
Physical Address. . . . . . . . . : 00-FF-C0-6C-07-7A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:610:600:63a::2(Preferred)
Link-local IPv6 Address . . . . . : fe80::35ef:a053:82e1:68c7%26(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.104.199(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 2001:610:600:63a::1
DHCPv6 IAID . . . . . . . . . . . : 671154112
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-1A-31-A2-00-90-F5-8C-60-0E
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Bluetooth Network Connection 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
#2
Physical Address. . . . . . . . . : 00-09-DD-50-19-81
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : home
Description . . . . . . . . . . . : Intel(R) WiFi Link 5100 AGN
Physical Address. . . . . . . . . : 00-21-5D-2D-F3-A6
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2002:81a8:102::(Preferred)
Link-local IPv6 Address . . . . . : fe80::642c:15f5:a2c1:597f%12(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.13(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : maandag 25 januari 2010 22:28:13
Lease Expires . . . . . . . . . . : maandag 1 februari 2010 22:28:13
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 218112349
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-1A-31-A2-00-90-F5-8C-60-0E
DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 00-90-F5-8C-60-0E
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Does anybody know what could be wrong?
Thanks in advance! :)
Windows 7 DNS doesn't work
Jeroen Massar on Monday, 25 January 2010 23:58:23 C:\>nslookup -type=AAAA www.ipv6.sixxs.net DNS request timed out. timeout was 2 seconds. Server: UnKnown Address: 192.168.1.1
I'll assume 192.168.1.1 is your DSL/Cable-modem thingy that does NAT for you. It clearly does not support AAAA records.
You'll need to update it to have a proper DNS server which does not just drop DNS queries it does not support.
If you can't update it, you'll have to resort to using alternate DNS servers, preferably the ones of your ISP.
Windows 7 DNS doesn't work
Shadow Hawkins on Tuesday, 26 January 2010 00:11:52
Dang... That something that small f*cked it up...
I changed the DNS servers to OpenDNS' address, and guess what? It works!
C:\>nslookup -type=AAAA www.ipv6.sixxs.net
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 208.67.222.222
Non-authoritative answer:
Name: nginx.ipv6.sixxs.net
Addresses: 2001:1af8:1:f006::6
2001:7b8:3:4f:202:b3ff:fe46:bec
2001:838:2:1::30:67
2001:960:800::2
Aliases: www.ipv6.sixxs.net
Thanks so much! :)
Posting is only allowed when you are logged in. |