Windows 10 DNS issues - anyone else had this?

[DGardiner]

Ive recently been having issues with a couple of windows 10 machines not being able to connect to the proxy, after having a bit of a dig around it turns out they're reading the DNS answer and not using the local ip in the response as expected and instead jumping to an ip in a different subnet which they can't access.

 

I've had a dig around and the closest i can find is: https://social.technet.microsoft.com/Forums/en-US/d24f06e8-51e0-4812-a605-4a0da038d580/dns-subnet-prioritization-does-not-work-on-windows-10?forum=win10itpronetworking

 

The NSLOOKUP responses are as expected with the local address being listed first but the windows 10 machines are reading the second entry every time, I've disabled round robin on the server just to be sure - not sure what else to try? google fu seems to be largely giving answers for registry hacking server 2003

> smoothwallServer: 10.1.1.3

Address: 10.1.1.3#53

Name: smoothwall.x.local

Address: 10.1.1.254

Name: smoothwall.x.local

Address: 10.1.2.254

Name: smoothwall.x.local

Address: 10.1.3.254

Name: smoothwall.x.local

Address: 10.1.4.253

[JamesHartley]

Hi - just wondering if you ever got this to work?

We are being told that smoothwall connect is not windows 10 compatible???

Best regards

James

[DGardiner]

Nah, i ended up having to edit the computers DNS servers to point at the onsite

[JamesHartley]

So is smoothwall connect windows 10 compatible? I'm getting conflicting reports.

[Michael]

This sounds like a rogue DNS server/router or possibly a VLAN issue.

[DGardiner]

This sounds like a rogue DNS server/router or possibly a VLAN issue.

 

 

I checked, the DNS server reply was not being read in order, with windows 10 just deciding to jump to the 2nd option. this only happened after a few months of them being in place, i did read online that reinstalling can fix the issue but people had it come back up again a few months in.

 

i just manually set the DNS servers since i only have a handful of win10 machines and only 2 were displaying this.

[Michael]

The only time any version of Windows does this, is if it can't resolve DNS Server 1, hence it tries to resolve to DNS Server 2 and so on.

 

I've not had this issue at any sites, so I can only presume there's a gremlin in your network somewhere.

 

If you manually configure a client to force it to communicate with DNS Server 1 (and it fails), I'd suggest this is where you investigate first.