Register now or log in to join your professional community.
According to me, functioning of a AD revolves around DNS. AD provides centralized management of its resources. Group Policies are used to manage the AD security. Domain controller will always checks DNS entries to find its resources. When we add a computer to domain, it adds an entry to DNS server so without configuring DNS we just cant install AD. AD replication also uses DNS database for finding its replication partner.
Good one
Only if the domain controller IP is set as the primary DNS for client computer we can join it to Domain. The reason for this explains the relationship between DNS and ADDS.
Active Directory relies on a properly configured and functional DNS Infrastructure. If you have an Active Directory problem, chances are that you have a DNS problem. The first thing you should check is DNS. The second thing you should check is DNS. The third thing you should check is DNS.
When you install Active Directory and the DNS Server role on your first Domain Controller in the domain, it automatically creates two forward lookup zones for your domain. If we stick to the example above, you'll have a zone for ad.example.com and _msdcs.ad.example.com.
Please feel free if you need further explanations in this regard.
Active Directory relies on a properly configured and functional DNS Infrastructure
Active Directory is dependent on DNS as a domain controller location mechanism and uses DNS domain naming conventions in the architecture of Active Directory domains. There are three components in the dependency of Active Directory on DNS:
Active Directory required DNS (Domain Name System) to work, DNS server can be separate server
