I would like to fix a problem in my LAN (Windows 10 Pro clients on
192.168.140.x subnet). I have a Windows 2008 R2 Server (
192.168.140.9) that's mainly used as DHCP server and DNS conditional forwarder (non authoritative). Clients PCs need resolution for both public internet hostnames as also a set of private ones (of hosts located on a remote LAN:
192.168.200.x) for all PC in my local LAN.
The private hostnames should only be solved by DNS servers on the remote LAN itself.
I've configured the DHCP server to assign DNS servers in this order:
18.104.22.168 22.214.171.124 192.168.140.9 192.168.200.8 192.168.200.31
192.168.140.9 is my own server acting as DNS. The last two addresses are DNS servers for the remote LAN (but I would like to remove these last two options since they are redundant).
My DNS server is configured as a conditional forwarder of the hostnames located in the remote LAN (trough
Using nslookup I can clearly see that everything works (if I set the correct DNS server) but Windows seems unable to solve names in the private side and thus many applications fails to locate private servers (NAS, mail server, intranet web server etc). The only way I can arrange DNS order so it works is to set the two private side DNS servers as first in list:
192.168.200.8 192.168.200.31 126.96.36.199 188.8.131.52 192.168.140.9
This something I would like to avoid because I don't want remote DNS to be charged of resolving internet names.
How can I fix this? I cannot change clients network configuration other than changing DHCP / DNS configuration options (of my own server) and of course I cannot change the remote server DNS behaviour.