Why does the Windows client need to use the domain controller’s IP address as its DNS server before joining `condorid.local`?

A domain join depends on the client finding the services associated with the Active Directory domain. DNS provides the name-resolution information used to locate those services. In the lab, the domain controller is also the DNS server, so configuring the client to use the DC’s IP directs domain queries to the correct DNS service. This is a name-resolution requirement, not merely a requirement that the client and server have IP connectivity. **Key takeaway:** Correct DNS configuration is a prerequisite for reliable domain discovery and joining.\n\n**Glossary:** **Domain discovery**: Finding the services associated with a domain. **Active Directory**: Microsoft’s directory service. **Resolver**: The client-side function or server that sends DNS queries.