ACapo

New Member
Joined
Dec 20, 2022
Messages
6
We recently started having a problem where if the Domain Controller is not listed first in the "DNS Server addresses, in order of use". The computer will not join the Domain? It is supposed to go to the next server on the list if the first one is not a domain controller. Does anyone have any idea what could cause this? I believe it is causing other issues . I know the workaround is to put the Domain Controller first. But we have never had to do that before.
 


Last edited:
DNS is used to locate srv records for ldap, so if you only have one internal DNS server and it is the DC then yes it would need to be first. Best practice is to have two DCs and two DNS servers
 


DNS is used to locate srv records for ldap, so if you only have one internal DNS server and it is the DC then yes it would need to be first. Best practice is to have two DCs and two DNS servers
We have had our DNS servers listed first before the domain controllers and it never mattered.
 


Are you joining by the domain NetBIOS name or fqdn? That can impact how it resolves to your domain controller as well
 


Solution
The Domain Controller is .230 The other 2 are DNS servers . If .230 is listed first the computer will join the Domain. The order has never mattered in the past and in theory it should not matter.

1672142740309.webp
 


Attachments

  • 1672142615518.webp
    1672142615518.webp
    9.3 KB · Views: 46
Microsoft admitted today that this is caused by KB5019966 . They are still working on a fix.
 


Back
Top