You are here

AREDN DNS not resolving on Windows 10 machines with dual NICS

2 posts / 0 new
Last post
ve6vh
ve6vh's picture
AREDN DNS not resolving on Windows 10 machines with dual NICS

Hello All,
I have two WIndows 10 machines with dual NIC's, one on my external LAN and the other on the mesh network. After a recent update I found that I could not resolve DNS addresses on the mesh NIC any more. The problem turns out to be that all DNS requests were being routed to the external LAN, instead of the AREDN node, despite having the DNS server address and suffix set up correctly.

The culprit turned out to be a windows 10 feature called "Smart Name Resolution", which uses the fastest DNS server to respond for all lookups,  The incorrect assumption is that both NICs access the same DNS database and can resolve all addresses, where in our case they are distinct and apart from each other. The solution is to turn it off.

Invoke the registry editor and modify the following:

In the key: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\DNSClient
Add a DWORD value with name "DisableSmartNameResolution" with value of 1. 

Also, in the key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters
Add a DWORD value with name "DisableParallelAandAAAA" with value of 1 if it does not exist, if so, just change it.

The first entry will disable the smart lookup and revert to determining the correct NIC by the DNS suffix, the second will disable IPV6 lookup. If you really need it, you can probably leave it on, but I have tried it on two different machines with success on both.

73, De VE6VH
 

 

K6AH
K6AH's picture
Windows 10 machines with dual NICS

Well done, Martin.  Thanks

Andre, K6AH

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer