|
Vista x64 DNS Problem
![[us]](/s/countries/us.gif) Shadow Hawkins on Tuesday, 22 April 2008 19:22:33
I am running Vista x64 with AICCU. I can ping ipv6 addresses and an ipv6 hostname if i use "ping -6".
Only "ping -6", "tracert -6", and nslookup can resolve an ipv6 hostname. So if I type ipv6.google.com into firefox I get a "Server Not Found" Error. Wireshark reveals that it is not even doing the AAAA lookup.
Any ideas on how to get this to work? :?
Vista x64 DNS Problem
![[ca]](/s/countries/ca.gif) Shadow Hawkins on Wednesday, 23 April 2008 23:30:31
Can you connect to http://[2001:4860:0:2001::68]/ , which is the IPv6 numerical address for ipv6.google.com
Check in the about:config and see what the state of 'network.dns.disableIPv6' is. If it is set to true, then change it to false. Try accessing ipv6.google.com again and see if this changes anything.
Next, check to see if there is a firewall active that may be causing connectivity issues. I have not used Vista, so I don't know what particularities it may have.
Vista x64 DNS Problem
Shadow Hawkins on Tuesday, 29 April 2008 07:40:55
http://[2001:4860:0:2001::68]/ works great.
network.dns.disableIPv6 IS false.
ipv6.google.com gets a server not responding.
Firewall turned off has no effect.
nslookup ipv6.google.com returns:
Server: DD-WRT
Address: 192.168.1.1
Non-authoritative answer:
Name: ipv6.l.google.com
Address: 2001:4860:0:2001::68
Aliases: ipv6.google.com
Vista x64 DNS Problem
Shadow Hawkins on Tuesday, 29 April 2008 18:17:44
Does using Firefox 3 beta 5 (current beta at this point), or any other browser, make any difference?
Vista x64 DNS Problem
Shadow Hawkins on Saturday, 03 May 2008 05:08:57
Firefox 3 and IE 7 have the same problem.
Vista x64 DNS Problem
Shadow Hawkins on Tuesday, 06 May 2008 03:32:53
This would tend to suggest that the issue is not browser related, but a system configuration issue. Maybe this may have the winning answer:
http://technet.microsoft.com/en-us/library/bb878057.aspx
Vista x64 DNS Problem
![[au]](/s/countries/au.gif) Shadow Hawkins on Sunday, 11 May 2008 10:47:05
I have the same problem.
1. I can ping an IPv6 address ok.
2. I can view IPv6 web sites if using the IP (http://[ipv6ip] format)
3. I can resolve a hostname with nslookup
C:\Users\gm22>nslookup ipv6.google.com
Server: UnKnown
Address: 202.124.84.2
Non-authoritative answer:
Name: ipv6.l.google.com
Address: 2001:4860:0:2001::68
Aliases: ipv6.google.com
4. What I can't do is to ping an IPv6 hostname or access an IPv6 web site using a hostname:
http://ipv6.google.com
Same for IE and Firefox. Is there somewhere I can add a DNS server for IPv6 lookups? Is there a public DNS server that has an IPv6 IP address?
Thanks.
GM
Vista x64 DNS Problem
Shadow Hawkins on Sunday, 11 May 2008 13:21:50
Are you capable of pinging your tunnel end-point? Is aiccu running? What does the following give you:
ipconfig /all
I haven't looked at IPv6 usage much under Windows, but in some operating systems you need to use the command 'ping6' to ping using IPv6.
Vista x64 DNS Problem
Shadow Hawkins on Friday, 16 May 2008 08:32:52
What version of windows are you using?
I tried using the registry hack to disable Teredo & 6to4 but didn't help.
Also I included this to see if any of you could see anything odd.
Windows IP Configuration
Host Name . . . . . . . . . . . . : Defcon1V
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Network Bridge:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : MAC Bridge Miniport
Physical Address. . . . . . . . . : 02-1E-8C-29-B7-04
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.106(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, May 15, 2008 11:19:12 PM
Lease Expires . . . . . . . . . . : Friday, May 16, 2008 11:19:12 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Hamachi:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hamachi Network Interface
Physical Address. . . . . . . . . : 7A-79-05-35-39-81
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 5.53.57.129(Preferred)
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Lease Obtained. . . . . . . . . . : Thursday, May 15, 2008 11:19:12 PM
Lease Expires . . . . . . . . . . : Friday, May 15, 2009 11:21:19 PM
Default Gateway . . . . . . . . . : 5.0.0.1
DHCP Server . . . . . . . . . . . : 5.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter aiccu:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Win32 Adapter V9
Physical Address. . . . . . . . . : 00-FF-84-92-49-27
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:4978:f:106::2(Preferred)
Link-local IPv6 Address . . . . . : fe80::f105:981b:787c:f764%17(Preferred)
Default Gateway . . . . . . . . . : 2001:4978:f:106::1
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter Local Area Connection* 9:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 10:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{B5E8025A-8D11-475C-8791-8CAA208EF65A}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 16:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{9E46C1AD-0663-4675-8832-B6D993CB9C31}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Vista x64 DNS Problem
I tried using the registry hack to disable Teredo & 6to4 but didn't help.
What kind of "hack" is that? You should not have to touch the registry for most things you do on Windows anyway.
To disable 6to4, Teredo and ISATAP:
netsh int ipv6 6to4 set state disabled
netsh int ipv6 set teredo disable
netsh int ipv6 isatap set state disabled
And then it might require a reboot for those interfaces to actually disappear, some actually never disappear, but they won't get an address. According to your output they are all in "Media Disconnected" state, thus that should be fine.
Your real problem seems to be this "Himachi" interface, which is yet another tunneling protocol. It seems to have a default gateway set, thus it is not unlikely that you are routing packets over that. You do realize that Himachi is using stolen address space do you? 5/8 is not allocated to them and thus not for them to be used.
What kind of interface is that "MAC Bridge Miniport" ? Is it some kind of strange Bridge, a DSL thing or just real Ethernet?
Lastly, you seem to have a DNS server at 192.168.1.1, is this DNS server IPv6 capable? That is, can you actually query it correctly for AAAA addresses without it not peeping up on them?
Try start-> run "nslookup", then type "set q=aaaa" and then "www.ipv6.sixxs.net", "www.ipv4.sixxs.net" and "www.sixxs.net", to see if those answers get answered quickly, if at all.
Also note that it might not be your DNS server which has issues with IPv6 (DD-WRT mostly works from what I know), but it might quite well be one if that DNS servers upstream DNS servers, aka the ones that it will ask again) giving problems.
Vista x64 DNS Problem
Shadow Hawkins on Friday, 16 May 2008 18:50:32
I undid the regitry hack and did the netsh commands. I'm going to reboot in a second.
The dns server is fine.
www.ipv6.sixxs.net Server: DD-WRT
Address: 192.168.1.1
Name: noc.ipv6.sixxs.net
Address: 2001:838:1:1:210:dcff:fe20:7c7c
Aliases: www.ipv6.sixxs.net
MAC Bridge Miniport = Network Bridge, I have 2 Ethernet ports that I bridged.
Vista x64 DNS Problem
Shadow Hawkins on Friday, 16 May 2008 20:12:56
It had no effect.
I'm wondering about the following:
"If the host has at least one IPv6 address assigned that is not a link-local or Teredo address, the DNS Client service sends a DNS query for A records and then a separate DNS query to the same DNS server for AAAA records. If an A record query times out or has an error (other than name not found), the corresponding AAAA record query is not sent."
There is a link local entry on the adapter.
Vista x64 DNS Problem
Shadow Hawkins on Saturday, 17 May 2008 06:38:33
I had the exact same problem on my Vista SP1 (32-bit) machine and the latest aiccu console client (2008.03.15)with the tap901 driver.
The issue is that Microsoft has some pretty strange "by design" parameters (which I see as a bug ) on when to use AAAA DNS requests:
http://technet.microsoft.com/en-us/library/bb727035.aspx
"The DNS Client service in Windows Vista has been designed to minimize the impact on DNS servers when performing DNS name queries through the following behavior:
If the host has only link-local or Teredo IPv6 addresses assigned, the DNS Client service sends a single query for A records.
If the host has at least one IPv6 address assigned that is not a link-local or Teredo address, the DNS Client service sends a DNS query for A records and then a separate DNS query to the same DNS server for AAAA records. If an A record query times out or has an error (other than name not found), the corresponding AAAA record query is not sent."
What this basically means is that unless the stack "sees" a non link-local ipv6 address on a network adapter (apparently something in the tap901 driver or aiccu config does not qualify the virtual tunnel network adapter)
In any case, I found this snippet in a blog (which worked for me):
http://yorickdowne.wordpress.com/2008/04/05/ipv6-at-home-part-2-tunnel-brokers-windows-ayiya-tunnel/
"Vista-specific twist: As with Teredo, Vista refuses to resolve ipv6 addresses, because your physical interface only has a link-local address. Thereâs a discussion of this in part 1 - Iâll just give you the quick-and-dirty instructions here: Open up the Properties of your LAN or WiFi interface, and change it to have a static IPv6 address. Use the 192.168.1.2 equivalent of 2002:81a8:102:: with a netmask of 48. Do not configure a default gateway for this address."
Good Luck, and I will post when/if I find a more elegant solution (or get MS support to open a new kb or qfe)
--Dave H
=:)
Vista x64 DNS Problem
![[no]](/s/countries/no.gif) Shadow Hawkins on Thursday, 22 May 2008 21:39:28
Thanks for posting this, Dave, it worked great for me! :)
Vista x64 DNS Problem
Shadow Hawkins on Saturday, 24 May 2008 18:58:39
Works like a dream for me as well.
Vista x64 DNS Problem
If you are running a "Virus Checker", de-install it for a test, they unfortunately sometimes go like "hey what is this, I don't understand it *throw away*" where that 'this' was your IPv6 DNS/HTTP/etc..
Disabling them is generally not good enough for those clueless products. Though there is an argument for them to block unknown protocols, but doing so silently and not being able to choose the no-block option is not the correct way.
|
![[ch]](/s/countries/ch.gif)
on Friday, 16 May 2008 09:03:05
Posting is only allowed when you are