I'm currently restructuring my network because it's become overcrowded. We used to have a flat network, but now we've divided it into various subnets, including a default, wireless, and one for network devices. Here's how it's set up: I have a Unifi gateway at 192.168.0.1 and two Windows Servers at 192.168.0.2 and 192.168.0.4. The default workstation network is 192.168.0.0/24 and the wireless network is at 192.168.10.0/24. Right now, DHCP and DNS are both managed by the Windows Server. The issue arises when DNS requests for internal records, like server-1.net.local, come from the default subnet (192.168.0.0/24); they work just fine. However, when I try to resolve these records from other local subnets, the server returns 'nonexistent domain'. The requests are reaching the Domain Controller, but it fails to return results. I've checked the DNS logs, but there's nothing useful there. I suspect this problem is related to the server misidentifying the origin of the request, but I can't figure out how to fix it. Any guidance would be greatly appreciated!
3 Answers
Running a debug mode nslookup from a problematic client could provide insights. If it seems like a routing issue, that might be worth investigating.
There's a chance you have a query resolution policy that's blocking certain subnets. Try using the command `Get-DnsServerQueryResolutionPolicy` to check on that.
You might want to search for 'split brain DNS' for Windows Server. That could help with how your DNS is handling requests from different subnets.

Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures