|
[windows 7x64,ayiya] dns resolve problems
![[de]](/s/countries/de.gif) Shadow Hawkins on Wednesday, 19 January 2011 23:48:58
Evening gents,
I've been trying to fix some DNS related issues on my setup all day long and couldn't find any working solution.
Problem description:
ipv6 traffic works when specifying IPs instead of hostnames, this manifests quite everywhere except when forcing ipv6 use(like ping -6). using hostnames like ipv6.google.com does not resolve to a ipv6 address in webbrowsers/ping/whatever
Setup:
Im using AYIYA(it works flawlessly for routing traffic/everything), my router has a built in DNS forward(using Opendns servers), i tried to use opendns as dns server on my pc but it didnt work.
e.g.:
C:\Users\bogie>ping -6 ipv6.google.com
Pinging ipv6.l.google.com [2a00:1450:8001::63] with 32 bytes of data:
Reply from 2a00:1450:8001::63: time=36ms
Reply from 2a00:1450:8001::63: time=41ms
Reply from 2a00:1450:8001::63: time=38ms
Reply from 2a00:1450:8001::63: time=36ms
Ping statistics for 2a00:1450:8001::63:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 41ms, Average = 37ms
C:\Users\bogie>ping ipv6.google.com
Ping request could not find host ipv6.google.com. Please check the name and try
again.
C:\Users\bogie>
nslookup
C:\Users\bogie>nslookup ipv6.google.com
Server: netconnect.box
Address: 192.168.0.1
Non-authoritative answer:
Name: ipv6.google.com.localdomain
Address: 67.215.77.132
nslookup type=AAAA
C:\Users\bogie>nslookup -type=AAAA ipv6.google.com
Server: netconnect.box
Address: 192.168.0.1
Non-authoritative answer:
Name: ipv6.l.google.com
Address: 2a00:1450:8001::93
Aliases: ipv6.google.com
nslookup with opendns set directly
C:\Users\bogie>nslookup ipv6.google.com
Server: resolver1.opendns.com
Address: 208.67.222.222
Non-authoritative answer:
Name: ipv6.google.com.localdomain
Address: 67.215.77.132
C:\Users\bogie>
ipconfig /all
C:\Users\bogie>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : keksbox
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : localdomain
Ethernet adapter Local Area Connection 5:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Win32 Adapter V9 #4
Physical Address. . . . . . . . . : 00-FF-4A-CA-54-23
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter aiccu:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Win32 Adapter V9 #3
Physical Address. . . . . . . . . : 00-FF-86-AE-C5-EA
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:4dd0:ff00:4c1::2(Preferred)
Link-local IPv6 Address . . . . . : fe80::cd87:3ee4:c226:1768%15(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.23.104(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 2001:4dd0:ff00:4c1::1
DHCPv6 IAID . . . . . . . . . . . : 318832518
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-C7-AD-BE-00-26-18-6A-42-2A
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 Local Area Connection:
Connection-specific DNS Suffix . : localdomain
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 00-26-18-6A-42-2A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.0.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Mittwoch, 19. Januar 2011 16:16:32
Lease Expires . . . . . . . . . . : Mittwoch, 26. Januar 2011 23:37:19
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 208.67.222.222
208.67.220.220
NetBIOS over Tcpip. . . . . . . . : Enabled
prefixpolicies
netsh interface ipv6>show prefixp
Querying active state...
Precedence Label Prefix
---------- ----- --------------------------------
50 0 ::1/128
40 1 ::/0
30 1 2001::/32
30 2 2002::/16
20 3 ::/96
10 4 ::ffff:0:0/96
5 5 3ffe:831f::/32
route
netsh interface ipv6>show route
Publish Type Met Prefix Idx Gateway/Interface Name
------- -------- --- ------------------------ --- ------------------------
Yes Manual 256 ::/0 15 2001:4dd0:ff00:4c1::1
No Manual 256 ::1/128 1 Loopback Pseudo-Interface
1
No Manual 256 2001:4dd0:ff00:4c1::/64 15 aiccu
No Manual 256 2001:4dd0:ff00:4c1::2/128 15 aiccu
No Manual 256 fe80::/64 16 Local Area Connection 5
No Manual 256 fe80::/64 15 aiccu
No Manual 256 fe80::4197:f291:999e:48f0/128 16 Local Area Connectio
n 5
No Manual 256 fe80::cd87:3ee4:c226:1768/128 15 aiccu
No Manual 256 ff00::/8 1 Loopback Pseudo-Interface
1
No Manual 256 ff00::/8 16 Local Area Connection 5
No Manual 256 ff00::/8 15 aiccu
[windows 7x64,ayiya] dns resolve problems
Shadow Hawkins on Thursday, 20 January 2011 01:38:21
After consulting google a bit more I found a solution:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Dnscache\Parameters
add a DWORD value:
AddrConfigControl = 0
[windows 7x64,ayiya] dns resolve problems
Shadow Hawkins on Tuesday, 15 February 2011 22:23:19
Thanks a lot for this hint!
[windows 7x64,ayiya] dns resolve problems
Shadow Hawkins on Wednesday, 16 February 2011 10:13:17
After reading the setup hints again and again I finally found the source of the problem. According to the documentation you've to add a dummy address to your lan/wlan interface.
[bold]It didn't work, because I disabled IPv6 on the lan/wlan interface. Assure it's enabled![/bold] Otherwise you get an Element not found. error.
Remember that in order to access an IPv6 host by name as opposed to IP address, a DNS lookup has to be performed for the appropriate AAAA record. Unfortunately on Windows 7 (and Vista too), if the PC has only link-local or Teredo IPv6 addresses assigned, the DNS client service sends a single query for A records i.e. no AAAA lookup. In order to get the DNS client to send AAAA
queries, we have to assign a dummy IPv6 address to the lan/wlan
interface, e.g. by entering the following from a command window:
Source: IPv6 at home Part 4 by 2010, David Hyams
netsh ipv6 add address "Local Area Connection" 2002:81a8:102::
This is the command given in the documentation and presumably
the one used by most SixXS users. If like me youre interested to know where this magic number 2002:81a8:102:: comes from, the answer is simple. The 2002 prefix is reserved for use by 6to4 networks, and the next 32 bits are the IPv4 address encoded in hexadecimal.
|
Posting is only allowed when you are