I've got a strange problem with one of the machines in our organization. Namely, it's using the wrong DNS server when trying to resolve names.
The DNS configuration is pretty straightforward - we have two internal DNS servers, and the DHCP assigns the public Google DNS servers as backup.
In total, a DHCP client receives the following DNS servers, in order:
- Internal DNS #1
- Internal DNS #2
This configuration works for everyone... except one Windows 10 machine, which seems to be using the Google DNS rather than the internal DNS. That machine has internet access, of course, but cannot access our internal resources. It's also worth noting that the machine can ping both the DNS servers and our internal IPs just fine, so this doesn't appear to be a connectivity problem.
Stranger still, IF that machine connects via WiFi (the DHCP remains the same, there's just an AP in the way), then the correct, internal, DNS is used.
There are no custom IPv4 settings on that machine, and I'm not aware of Windows using any other kind of DNS priority system beyond the order in which the servers are listed.
What could be wrong here?
EDIT: Some additional information:
- All machines are connected to a local DC
- The machine in question, when running
nslookupwill show the default DNS server being used as
nslookup <internalDNSname> <internal DNS IP>on the target machine works and produces the expected result, so the machine in question can communicate with our DNS servers just fine
- If I remove the public Google DNS servers from the DHCP configuration and refresh the connection on the target machine everything works fine and internal DNS servers are used. If I re-add the Google DNS servers, the machine will start using those once more.