I just setup a WS2019 lab, which has two DCs with integrated DNS. I have forward and reverse lookup zones for both of my networks. The domain is "lab.local". If I run nslookup queries on either DC, using the short name or FQDN, I get the expected DNS results. However, what I can't explain is what happens on a non-domain joined Windows 10 computer, or a Mac.
Both the non-domain joined Win10 PC and Mac are pointed to the lab.local DNS server IP addresses. If on the PC/Mac I execute 'nslookup addc01.lab.local' I get:
C:\Users\DS>nslookup addc01.lab.local
Server: UnKnown
Address: 172.26.13.10
*** UnKnown can't find addc01.lab.local: Non-existent domain
But as I mentioned earlier, running that same FQDN nslookup on either DC gives me the proper result. If I 'force' nslookup to query my lab DCs, I still get the same failed result:
C:\Users\DS>nslookup addc01.lab.local 172.26.13.10
Server: UnKnown
Address: 172.26.13.10
*** UnKnown can't find addc01.lab.local: No response from server
and running that from a lab DC:
C:\Users\Administrator>nslookup addc01.lab.local 172.26.13.10
Server: ADDC01.lab.local
Address: 172.26.13.10
Name: addc01.lab.local
Address: 172.26.13.10
I've setup dozens of lab DCs like these before, and never had such inconsistent DNS resolution for non-domain joined computers. Any ideas?
I should mention the PC/Mac are on a different LAN network from the DCs (10.13.2.x). I provisioned a dummy WS2019 VM on the same network as the DCs (not domain joined), and the nslookup queries DO behave as I would expect (i.e they work).
