I am a somewhat experienced sys admin, who has built a number of DCs among other servers before, and never have I ever had trouble getting simple DNS lookups working.. Thanks in advance for any help.
I did a clean install of Server 2019, essentials first before trying another clean install using standard.
I have an entirely clean slate, no other roles or applications installed at this point.
I have not installed AD DS or attempted to promote to a DC yet, am only trying to get DNS working.
I have two intel i210 adatpers, one disabled during testing, the other with a static IP. The DNS which is pointing to that same static IP address.
I install DNS, I create a forward lookup zone with nothing fancy, set as a "primary zone", dyanmic updates disabled.
After rebooting for good measure, open cmd, and try pinging google.com.. "could not find host"
nslookup returns "server: localhost, 127.0.0.1"
nslookup 22.214.171.124 returns "server: localhost, 127.0.0.1, dns request time out, request to localhost timed-out"
Strange part is I can ping a hostname from another server on the internal network and that resolves with the correct IP address.
Cheecking the DNS application logs, I see errors 408, 407 and 404. 408 seemingly being the most telling:
408: The DNS server could not open socket for address 192.168. 1.10. Verify that this is a valid IP address for the server computer. If it is NOT valid use the Interfaces dialog under Server Properties in the DNS Manager to remove it from the list of IP interfaces.
The static IP address I have configured on the adapter IS most certianly valid, correct subnet, no other device using that IP address (of which I have tried several now, and is not actually .1.10).
Googling the error suggests that this problem is purely due to NAT being installed and active on the same interface.. Again, I have a completley clean slate, no other roles or anything installed besides drivers.
I have tried using both adapters, with the same result. I have also tried pairing the two togeather in a team, and attempting to configure the virtual NIC for use with DNS and same exact result.
I have also tried performing a new install of the DNS role following the exact same steps above, on my home server which is a cheap mini PC based on a Celeron N5105 and a realtek NIC - worked perfectly right out of the box, the first time, no mucking around. Took me 5 minutes to deploy, and was able to ping any external website address after adding a forward lookup zone and pointing the DNS back at itself...
I have read that using a faulty or off-brand NIC as the interface for DNS might cause this? But if both i210s are producing the same issue - and my cheapo home unit with a realtek NIC works great - then what the heck is the problem here??