Eager to master hybrid server management? Discover how to administer Windows Server Hybrid Core Infrastructure on Azure, setting your path towards the Microsoft Certified: Azure Hybrid Infrastructure Administrator Associate certification!
Gauge your current knowledge
Gauge your current knowledge
Active Directory Domain Services (AD DS) relies on a well-designed site topology to work properly. When the topology is configured incorrectly, problems occur: volumes may fail to create, authentication becomes slow, and users may be blocked from accessing resources they need. The site topology defines how domain controllers (DCs) are placed, how IP subnets connect to sites, and how replication flows between locations.
A solid AD DS site topology starts with planning where domain controllers sit in your network. You map IP subnets to site objects so that traffic stays efficient and doesn't cross unnecessary network boundaries. The goal is to place DCs where they can respond quickly to authentication requests, LDAP queries, and Kerberos ticket operations. DNS infrastructure must support these DCs, because every authentication request first queries DNS to find a available domain controller.
Reliable connectivity between Azure NetApp Files, domain controllers, and storage clients is essential. Assign multiple DCs to each AD DS site so that if one fails, others can take over. Subnets within a site should have less than 10 milliseconds of latency between them. Avoid blocking communication between Azure NetApp Files and DCs with user-defined routes or firewall rules, because blocked ports break the connection that allows authentication and file access to work.
Azure NetApp Files depends on DNS to find domain controllers. Every four hours, it queries DNS SRV records to verify which DCs are available. If DNS records are stale or missing, the service cannot locate controllers and authentication fails. You must keep DNS records updated by removing entries for decommissioned DCs and adding records for new ones. For reverse lookups, which support LDAP and Kerberos functions, create a reverse lookup zone so that PTR records can be resolved properly.
Two main tools help manage AD DS site topology. Active Directory Sites and Services lets you map IP subnets to sites and configure site link costs and replication schedules to control how traffic flows between locations. Azure AD Connect Health monitors replication health and DC performance, sending alerts when problems arise. Using both tools together ensures consistent authentication performance and helps catch replication issues before they affect users.
StudyCerts
StudyCerts