Study guide
10.1 Active Directory-Integrated DNS Architecture, Dynamic Updates & Zone Types
Administering Windows Server Hybrid Core Infrastructure AZ-800
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
About Exam AZ-800: Format, Scoring & the September 2026 Retirement
2 Chapter 1: Active Directory Domain Services Architecture & Deployment
1.1 Deploying & Managing Domain Controllers On-Premises 1.2 Domain Controllers in Azure IaaS & Virtualized DC Cloning 1.3 Read-Only Domain Controllers (RODCs) & Password Replication Policies 1.4 Flexible Single Master Operation (FSMO) Roles & Troubleshooting 1.5 Active Directory Sites, Subnets & Site Link Topology 1.6 AD DS Replication: Topology Generation, Convergence & Diagnostics 1.7 Forest and Domain Trust Relationships
3 Chapter 2: AD DS Security Principals, Service Accounts & Domain Join
2.1 Managing Users, Groups & Objects in Multi-Domain and Multi-Forest Environments 2.2 Service Account Types & Group Managed Service Accounts (gMSA) 2.3 Joining Windows Server to AD DS, Microsoft Entra Domain Services & Microsoft Entra ID 2.4 Creating & Managing Users, Groups and Organizational Units at Scale
4 Chapter 3: Hybrid Identity & Microsoft Entra Integration
3.1 Microsoft Entra Connect Sync Architecture, Installation & Filtering 3.2 SourceAnchor, Synchronization Rules & Microsoft Entra Connect Health 3.3 Microsoft Entra Cloud Sync & Disconnected Multi-Forest Topologies 3.4 Hybrid Authentication Methods & Staged Rollout 3.5 Microsoft Entra Domain Services 3.6 Integrating Microsoft Entra ID, AD DS & Entra Domain Services: Choosing an Architecture
5 Chapter 4: Group Policy in AD DS and Hybrid Environments
4.1 Group Policy Architecture & Processing Order (LSDOU) 4.2 Group Policy Filtering, Loopback Processing & Client-Side Extensions 4.3 Group Policy Preferences, Item-Level Targeting & Central Store 4.4 Group Policy in Microsoft Entra Domain Services & Fine-Grained Password Policies
6 Chapter 5: Remote Server Management in Hybrid Environments
5.1 Windows Admin Center (WAC) Deployment On-Premises and in Azure 5.2 PowerShell Remoting, WinRM & the Kerberos Double-Hop Problem 5.3 Just Enough Administration (JEA) for Constrained PowerShell Endpoints 5.4 OpenSSH on Windows Server & PowerShell Remoting over SSH 5.5 Secure RDP Access, Remote Desktop Gateway & Azure Bastion
7 Chapter 6: Hybrid Management with Azure Arc and Azure Services
6.1 Azure Arc-Enabled Servers Architecture & Onboarding 6.2 Azure Machine Configuration & VM Extensions on Arc Servers 6.3 Azure Update Manager: Assessment, Maintenance Configurations & Dynamic Scoping 6.4 Azure Automation for Hybrid Workloads: Runbooks & Hybrid Runbook Workers
8 Chapter 7: Hyper-V Virtualization & Virtual Machine Configuration
7.1 Hyper-V Type 1 Architecture, Installation & Hardware Prerequisites 7.2 VM Generations, Secure Boot, vTPM, Enhanced Session Mode & Direct VM Access 7.3 Compute, Dynamic Memory & Hardware Acceleration 7.4 VM Resource Controls, CPU Groups & Host Compute Partitioning 7.5 Hyper-V Virtual Hard Disks & Checkpoint Management 7.6 Hyper-V Virtual Switches, NIC Teaming & Switch Embedded Teaming (SET) 7.7 Integration Services, Guest Components & Time Synchronization
9 Chapter 8: Hyper-V High Availability, Security & Containers
8.1 Hyper-V Failover Clustering & Cluster Shared Volumes (CSV) 8.2 Hyper-V Replica & Azure Site Recovery (ASR) 8.3 Guarded Fabric & Shielded Virtual Machines 8.4 Windows Server Container Hosts, Isolation Models & Images 8.5 Managing Container Instances & Linux Containers with WSL 8.6 Windows Container Networking & AKS Enabled by Azure Arc 8.7 Managing Container Images, Tags & Azure Container Registry
10 Chapter 9: Azure IaaS Virtual Machine Administration
9.1 Azure VM Sizing, Series Selection & Managed Disk Tiers 9.2 Azure VM Host Caching, Disk Bursting, Ephemeral OS Disks & Disk Operations 9.3 Azure VM High Availability: Availability Sets, Zones & Proximity Placement Groups 9.4 Virtual Machine Scale Sets, Autoscale & Azure Dedicated Hosts 9.5 Azure VM Networking, NSGs & Connectivity
11 Chapter 10: Hybrid DNS Infrastructure & Name Resolution
10.1 Active Directory-Integrated DNS Architecture, Dynamic Updates & Zone Types 10.2 DNS Records, Aging & Scavenging and the GlobalNames Zone 10.3 DNS Forwarding, Conditional Forwarding & Azure DNS Zone Integration 10.4 Hybrid Name Resolution with Azure DNS Private Resolver 10.5 Windows Server DNS Policies & DNSSEC
12 Chapter 11: IP Addressing, DHCP & IPAM Management
11.1 DHCP Server Role, the DORA Lifecycle & Active Directory Authorization 11.2 DHCP Scopes, Option Hierarchy, Reservations & Relay Agents 11.3 DHCP High Availability & Failover Configurations 11.4 IP Address Management (IPAM) Deployment & Auditing 11.5 Resolving IP Address Issues in Hybrid Environments
13 Chapter 12: Hybrid Network Connectivity, Remote Access & Private Access
12.1 Remote Access Role, VPN Protocols & Site-to-Site VPN to Azure 12.2 Network Policy and Access Services (NPAS), RADIUS & Policy Processing 12.3 Azure Network Adapter & Azure Extended Network 12.4 Web Application Proxy & Microsoft Entra Application Proxy 12.5 Microsoft Entra Private Access & Global Secure Access 12.6 Azure Relay & Hybrid Connections
14 Chapter 13: File Services, DFS, SMB & Azure File Sync
13.1 Windows Server File Share Access, NTFS Permissions & Access-Based Enumeration 13.2 File Server Resource Manager: Quotas, File Screens & Storage Reports 13.3 DFS Namespaces (DFS-N) & DFS Replication (DFS-R) 13.4 BranchCache: Distributed Cache and Hosted Cache Modes 13.5 Modern SMB Protocols, SMB Multichannel & SMB over QUIC 13.6 Azure File Shares, Tiers & Hybrid Permissions 13.7 Azure File Sync, Cloud Tiering & Monitoring 13.8 Migrating DFS Namespaces & DFS Replication to Azure File Sync
15 Chapter 14: Windows Server Storage Infrastructure & High Availability
14.1 Disk Partitioning, Volumes & Enterprise File Systems (NTFS vs ReFS) 14.2 Data Deduplication Architecture, Usage Types & Management 14.3 Storage Spaces & Storage Spaces Direct (S2D) 14.4 Storage Replica & Storage Quality of Service 14.5 iSCSI Target Server, IQNs, CHAP Authentication & Multipath I/O
10.1 Active Directory-Integrated DNS Architecture, Dynamic Updates & Zone Types
Key Takeaways Explain This Topic AI
AD-integrated zones replicate through Active Directory itself using multi-master replication, so every DNS server holding the zone can accept writes and there is no single primary to lose.
The DomainDnsZones partition replicates to DNS servers in one domain, while ForestDnsZones replicates to DNS servers in every domain of the forest.
Secure Only dynamic updates enforce the ACL on each DNS record object, so only the computer account that created a record can later overwrite it, which blocks non-Windows hosts from hijacking server names.
A stub zone stores only SOA, NS, and glue A/AAAA records, keeping an authoritative name-server list current for a child or partner domain without transferring the full zone.
A secondary zone holds a complete read-only copy maintained by zone transfer, which is the wrong choice when WAN bandwidth is the constraint.
Last updated: August 2026
Active Directory-Integrated DNS & Zone Management
Domain Name System (DNS) is the foundational name resolution and service discovery mechanism for Active Directory Domain Services (AD DS) and hybrid cloud enterprise environments. In Windows Server environments, DNS can operate as a traditional file-based system or as an Active Directory-Integrated service. Deploying DNS integrated with AD DS transforms DNS zone data into directory objects, enabling multi-master replication, granular security descriptors, and resilient high-availability architectures across hybrid enterprise networks.
1. Active Directory-Integrated DNS Architecture & Directory Partitions
In standard file-based DNS, a primary zone maintains a single read-write master file ( %SystemRoot%\System32\Dns\<zone_name>.dns ), and secondary servers pull read-only copies via full (AXFR) or incremental (IXFR) zone transfers. If the primary DNS server fails, no record additions, modifications, or dynamic client registrations can occur until the primary is restored.
Active Directory-Integrated DNS resolves this single point of failure (SPOF) by storing DNS zone data directly within AD DS directory partitions. Every domain controller running the DNS Server service acts as a writable multi-master peer. +-----------------------------------------------------------------------------+
- | ACTIVE DIRECTORY DIRECTORY PARTITIONS FOR DNS |
- | |
- | [ForestDNSZones Partition] |
- | - Path: DC=ForestDNSZones,DC=contoso,DC=com |
- | - Scope: Replicates to ALL DNS servers running on DCs in the entire forest|
- | - Use Case: Root domain zones, GlobalNames zone, _msdcs forest zone |
- | |
- | [DomainDNSZones Partition] |
- | - Path: DC=DomainDNSZones,DC=corp,DC=contoso,DC=com |
- | - Scope: Replicates to ALL DNS servers running on DCs in the local domain |
- | - Use Case: Domain-specific forward and reverse lookup zones |
- | |
- | [Legacy Domain Partition] |
- | - Path: CN=MicrosoftDNS,CN=System,DC=corp,DC=contoso,DC=com |
- | - Scope: Replicates to ALL domain controllers (including non-DNS servers) |
- | - Use Case: Backward compatibility with Windows 2000 Server deployments |
- +-----------------------------------------------------------------------------+
Key Architectural Advantages of AD DS Integration:
Multi-Master Replication & High Availability:
Dynamic updates from domain clients, DHCP servers, and cluster nodes can be committed to any available writable domain controller.
Directory changes replicate through the standard AD DS replication topology using Remote Procedure Call (RPC over IP) encrypted with Kerberos, eliminating cleartext zone transfer vulnerabilities across wide area networks (WANs).
Granular Access Control Lists (ACLs):
Because records are directory objects (class dnsNode ), administrators can configure Windows Discretionary Access Control Lists (DACLs) per record or per zone.
Application Directory Partitions:
By default, modern AD DS domains isolate DNS data into dedicated Application Partitions ( ForestDNSZones and DomainDNSZones ). This prevents DNS records from replicating to domain controllers that do not host the DNS Server role, reducing global directory database ( NTDS.dit ) bloat and replication overhead.
2. Dynamic Updates & Security Modes
Dynamic DNS (DDNS, RFC 2136) allows client computers and DHCP servers to automatically register and update their resource records (A, AAAA, and PTR) in DNS. Windows Server DNS supports three dynamic update configurations: +-----------------------------------------------------------------------------+
- | DYNAMIC UPDATE MODES COMPARISON |
- | |
- | MODE INTEGRATION REQ. SECURITY LEVEL RISK PROFILE |
- | -------------------+-------------------+----------------+-----------------|
- | None | Any Zone Type | High (Static) | High Admin Load |
- | Nonsecure & Secure | Any Zone Type | Low / Open | Record Hijacking|
- | Secure Only | AD DS-Integrated | Enterprise | Authenticated |
- +-----------------------------------------------------------------------------+
Dynamic Update Mechanics:
None: Dynamic registrations are rejected. All resource records must be created and maintained manually by an administrator. Used strictly in high-security, locked-down DMZ zones.
Nonsecure and Secure: The DNS server accepts registration requests from any client without authentication. Any rogue device on the network can overwrite existing records (such as domain controller A records or gateway hostnames), leading to DNS spoofing and Man-in-the-Middle (MitM) attacks.
Secure Only (Active Directory Required):
The DNS server requires Kerberos authentication via GSS-TSIG (Generic Security Services Algorithm for Secret Key Transaction Signatures).
When a domain-joined client creates an A record, the client's Active Directory computer account becomes the Owner of the dnsNode object in AD DS.
Only the owner, domain administrators, or delegated accounts possess permission to update or overwrite the IP address of that record. Other clients attempting to claim the same FQDN are denied.
DHCP Server Dynamic Updates & Name Protection:
When non-domain-joined devices (e.g., Linux appliances, IoT hardware) obtain IP leases from a Windows DHCP server, the DHCP server can register DNS records on their behalf. To prevent the DHCP server from owning the records under its own machine account (which would allow one non-domain device to overwrite another):
DNS Update Dedicated Service Account: Configure the DHCP server with dedicated Active Directory credentials to perform secure dynamic registrations.
DHCP Name Protection (DHCID): DHCP uses a DHCID resource record (RFC 4701) containing a cryptographic SHA-256 hash of the client's MAC address and Client Identifier (DUID) to lock the DNS record to that physical device, preventing name squatting.
3. DNS Zone Types: Primary, Secondary & Stub Zones
Windows Server DNS supports multiple zone architectures tailored for authority, performance, and cross-forest interoperability.
Zone Type Read/Write Status Replication Mechanism Content Stored
Primary Zone (Standard) Read/Write on one server File copy / IXFR / AXFR Complete zone database (all resource records)
- AD-Integrated Primary Multi-Master Read/Write AD DS Directory Partitions Complete zone database + AD ACLs
- Secondary Zone Read-Only Zone Transfer (AXFR/IXFR) from Master Exact copy of all resource records in the zone
Stub Zone Read-Only Zone Transfer of name server metadata SOA, NS, and Glue A/AAAA records only +-----------------------------------------------------------------------------+
- | STUB ZONE RESOLUTION ARCHITECTURE |
- | |
- | [Branch Office DNS Server] [Headquarters DNS Server] |
- | +--------------------------+ +-----------------------+ |
- | | Stub Zone: corp.hq.local | | Primary Zone: | |
- | | - SOA Record | | corp.hq.local | |
- | | - NS Records | ---(Queries DC)--->| - Full Record Set | |
- | | - Glue A Records (IPs) | | (A, CNAME, SRV, etc)| |
- | +--------------------------+ +-----------------------+ |
- | | |
- | v |
- | (Resolves queries directly by contacting HQ authoritative Name Servers) |
- +-----------------------------------------------------------------------------+
Stub Zones vs. Secondary Zones:
A Secondary Zone replicates every individual record from the master zone. For massive enterprise zones with hundreds of thousands of records, secondary zone replication consumes significant WAN bandwidth and local disk storage.
A Stub Zone replicates only the zone's Start of Authority (SOA) record, Name Server (NS) records, and the glue host (A/AAAA) records needed to resolve those NS hostnames. When a client requests a record (e.g., app01.corp.hq.local ), the local DNS server uses its stub zone to identify the authoritative HQ name servers and queries them directly. If HQ adds or renumbers a DNS server, the stub zone updates automatically.
4. Forward Lookup Zones vs. Reverse Lookup Zones +-----------------------------------------------------------------------------+
- | LOOKUP ZONE TAXONOMY & HIERARCHY |
- | |
- | [FORWARD LOOKUP ZONES] [REVERSE LOOKUP ZONES] |
- | - Function: Name -> IP - Function: IP -> Name |
- | - Key Records: A, AAAA, CNAME - Key Records: PTR |
- | - Example: contoso.com - IPv4 Domain: in-addr.arpa |
- | - IPv6 Domain: ip6.arpa |
- +-----------------------------------------------------------------------------+
Reverse Lookup Zone Addressing:
IPv4 Reverse Zones ( in-addr.arpa ): IPv4 addresses are reversed octet-by-octet. For subnet 192.168.10.0/24 , the reverse lookup zone name is 10.168.192.in-addr.arpa . An A record for 192.168.10.55 corresponds to PTR record 55.10.168.192.in-addr.arpa .
IPv6 Reverse Zones ( ip6.arpa ): IPv6 addresses are expanded into all 32 hexadecimal nibbles, reversed, and delimited by periods under ip6.arpa .
Classless IPv4 Reverse Delegation (RFC 2317): For subnets smaller than a /24 (such as a /28 or /29 ), standard octet boundaries do not align. RFC 2317 uses CNAME records in the parent zone pointing to a delegated child zone containing the specific host PTR records.