I need a sanity check here...
I have a local site with AD integrated DNS - Everything works.
I have a remote site that needs to use the local DNS servers. VPN works, remote DHCP is setting the DNS on the clients as the local servers. Clients int he remote site can ping the local dns servers. when I do a nslookup, the "server" is unknown but the IP address is correct. I can resolve google.com or any other external addresses, however I can't resolve anything in my zones. I have tried "host" and "host.domain.com" but both fail with "non existent domain. What am I missing here?
Thanks in advance
UPDATE, I did a pcap on a client in the remote network. It looks like the local dns servers are treating this as a external lookup and forwarding it to cloudflare (as expected for a external lookup).
The destination server is correct on the query (local address), the query is correctly appending the domain name but the SOA is coming back from cloudflare.
Why is the local DNS forwarding this request?
UPDATE2 it looks like this same issue is happening on all zones that are local to the dns server. Instead of returning a IP from the hosted zone, it is forwarding the request like any other internet queuey.
UPDATE3. I have no idea what is going on here. I changed the remote subnet from 10.30.10.0 to 10.40.10.0 and everything is now working. Why does the DNS server treat 10.30.10.0 differently then any other subnet? (I have other subnets on the local side too, all work fine)