Forum Discussion
Windows 10 can't see active directory domain on Windows Server 2016
Also needs unchecked on any domain members.
Thanks for replying :)
I changed the DNS on the server to be its fixed IP address and the second DNS to point to 8.8.8.8. I then changed the second DNS on the client to be 8.8.8.8.
I then ran the DCDiag and got an error 81 saying the host **server could not be resolve to an IP address. Then it bugged out!
Yes, that's not going to work. All domain members must use domain DNS exclusively. Members use domain DNS so they can find and logon to domain. Internet queries are passed along by default to root hint servers in a top-level-down fashion. You can optionally add public DNS addresses as forwarders.
(please don't forget to mark Best Response if helpful)
Sorry I misread what you said - should I remove the secondary DNS? I didn't have them in to start with.
Correct, domain controller and problem member both have the static ip address of DC listed for DNS and no others such as router or public DNS. If problems persist please the mentioned files up on OneDrive.
Hi
I'd love to send you the files, but - I can't run DCDiag as it bugs out with an 81 error... :(
I've uploaded the server's ipconfig and the workstation's ipconfig and the repadmin.Very much appreciate your help - thanks :)
