I work as a remote contractor with Contract Company A contracted to Employer B. Employer B has a VPN with various authentication that I use to log into their network.
When I'm working from home and not on the VPN, my DNS server is 18.104.22.168. When I connect to the VPN, my DNS server becomes B's DNS server for both Employer B's intranet names and for internet domain names.
Contract Company A maintains an office that I can go into and work from. When I connect to their network and I'm not on the VPN, I'm connected to A's DNS server for all addresses. When I log on to the VPN, my computer continues to use A's DNS instead of switching over to B.
So when I am on network A VPNed into network B, there are intranet sites on B that I cannot reach from my browser. When I do an nslookup on a couple of different intranet sites, they both point to some address that appears to be external to either network. When I do an nslookup and specify the DNS server to use the VPN's DNS server, they resolve correctly.
How do I change the order in which these resolve, and what governs this? When I was first encountering this problem, I asked both IT departments, and neither had any answer, so I ended up installing Cygwin and figuring out nslookup myself so that I could characterize this problem. Can I fix this locally on my laptop, and if so, how? Or do I need one of these IT departments to change something to fix this, and if so, which one?
Thanks for any help in sorting this out that you can provide.
Notes added in response to comment:
This isn't about round robin load balancing -- both on my home LAN and on my work LAN, which DNS server is used is always consistent.
Where do I adjust the setting for Split Tunneling? And why would it be different depending on which LAN I connect to the VPN through?
I don't have more than one NIC. I have a LAN connection and a VPN.
I am sending short names in all cases. Whenever I have network B's DNS server selected as the default or I specifically point nslooklup at that DNS server, it is expanded correctly. On network A's DNS, it is not expanded.