Study guide
11.1 DHCP Server Role, the DORA Lifecycle & Active Directory Authorization
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
11.1 DHCP Server Role, the DORA Lifecycle & Active Directory Authorization
Key Takeaways Explain This Topic AI
DHCP leases are negotiated by the four-step DORA exchange (Discover, Offer, Request, Acknowledge) over UDP port 67 to the server and UDP port 68 back to the client.
A client attempts renewal unicast at 50% of the lease (T1) and rebinding broadcast at 87.5% (T2), which is why a short lease multiplies server load.
A domain-joined Windows Server DHCP server must be authorized in Active Directory with Add-DhcpServerInDC or it shuts the service down and logs Event ID 1046.
Authorization is the built-in rogue-DHCP defence for Windows servers, but it cannot stop a non-Windows rogue server, which requires DHCP snooping on the switch fabric.
Because DHCP Discover is a broadcast, clients on a different subnet need a relay agent or an IP helper address on the router to reach a centralized DHCP server.
Last updated: August 2026
DHCP Server Role, the DORA Lifecycle & Active Directory Authorization
Dynamic Host Configuration Protocol (DHCP) on Windows Server automates the assignment of IPv4 and IPv6 network parameters—including IP addresses, default gateways, subnet masks, Domain Name System (DNS) servers, and vendor-specific options—to network clients. This section covers the two foundations of that infrastructure: the four-step DORA lease lifecycle with its renewal timers, and the Active Directory authorization rules that stop rogue servers from answering. Scopes, the option inheritance hierarchy, reservations, and cross-subnet relay routing are covered in section 11.2; high availability in section 11.3; and diagnosing addressing failures across on-premises and Azure in section 11.5.
1. DHCP Architecture & The DORA Process
The fundamental IPv4 address acquisition protocol consists of four sequential broadcast/unicast message exchanges termed DORA (Discover, Offer, Request, Acknowledge). Windows Server DHCP services operate over UDP port 67 (DHCP Server) and UDP port 68 (DHCP Client) . +-----------------------------------------------------------------------------+
- | THE DHCP DORA LEASE LIFECYCLE |
- | |
- | [DHCP CLIENT (0.0.0.0:68)] [DHCP SERVER (10.10.1.10:67)]|
- | | | |
- | | -------- 1. DHCPDISCOVER (Broadcast) --------> | |
- | | Src: 0.0.0.0:68 Dst: 255.255.255.255:67 | (Allocates |
- | | Payload: Client MAC (00-15-5D-01-02-03) | IP lease) |
- | | | |
- | | <------- 2. DHCPOFFER (Unicast/Broadcast) ---- | |
- | | Src: 10.10.1.10:67 Dst: 10.10.1.100:68 | |
- | | Offered IP: 10.10.1.100, Subnet: /24 | |
- | | | |
- | | -------- 3. DHCPREQUEST (Broadcast) ---------> | |
- | | Src: 0.0.0.0:68 Dst: 255.255.255.255:67 | (Confirms |
- | | Server ID: 10.10.1.10, Requested: .100 | selection) |
- | | | |
- | | <------- 4. DHCPACK (Unicast/Broadcast) ------ | |
- | | Src: 10.10.1.10:67 Dst: 10.10.1.100:68 | (Commits to |
- | | Includes Options: Router, DNS, Domain Name | database) |
- | v v |
- +-----------------------------------------------------------------------------+
The Four Phases of DORA:
DHCPDISCOVER (Client to Network): The client initializes its network stack without an IP address ( 0.0.0.0 ) and broadcasts a DHCPDISCOVER frame to 255.255.255.255 across UDP port 67. The payload embeds the client's hardware (MAC) address and requested parameters (Option 55 - Parameter Request List).
DHCPOFFER (Server to Client): Every DHCP server receiving the broadcast checks its active scopes. If an available IP exists, the server temporarily reserves that IP and transmits a DHCPOFFER message containing the offered IP, subnet mask, lease duration, and the server's own IP identifier.
DHCPREQUEST (Client to Network): The client selects one offer (typically the first received) and broadcasts a DHCPREQUEST message. Broadcasting this message is critical: it notifies the chosen DHCP server that its offer was accepted, while simultaneously signaling all other responding DHCP servers to release their reserved provisional offers back into their available pools.
DHCPACK (Server to Client): The selected server validates the request, commits the lease binding to its local Jet database ( dhcp.mdb ), and sends a DHCPACK frame containing the definitive IP configuration and all associated DHCP options (such as default gateway, DNS servers, and domain suffixes). If the address is no longer available, the server returns a DHCPNAK , forcing the client to restart the Discover process.
Lease Renewal Timers (T1 and T2):
T1 Timer (Renewal - 50% of Lease Duration): At exactly 50% elapsed lease time (e.g., Day 4 of an 8-day lease), the client sends a unicast DHCPREQUEST directly to the original leasing server. If the server is online, it responds with a unicast DHCPACK , resetting the lease timer.
T2 Timer (Rebinding - 87.5% of Lease Duration): If the original server fails to respond by 87.5% of the lease (e.g., Day 7 of an 8-day lease), the client enters the Rebinding state and broadcasts a DHCPREQUEST to any reachable DHCP server on the network.
Lease Expiration (100% of Lease Duration): If no DHCPACK is received when the lease expires, the client immediately drops the IP address, flushes its network stack, assigns itself an Automatic Private IP Addressing (APIPA) address ( 169.254.0.0/16 ), and restarts the DHCPDISCOVER cycle.
2. Active Directory Authorization & Rogue DHCP Prevention
To prevent rogue or misconfigured DHCP servers from issuing invalid IP parameters—which can cause denial-of-service or man-in-the-middle attacks—Windows Server enforces Active Directory authorization for domain-joined DHCP servers. +-----------------------------------------------------------------------------+
- | ACTIVE DIRECTORY DHCP AUTHORIZATION WORKFLOW |
- | |
- | [DHCP Server Service Starts] |
- | | |
- | v |
- | [Queries AD DS Configuration Partition: CN=NetServices] |
- | | |
- | +--------+--------+ |
- | | | |
- | (Listed in AD DS?) (NOT Listed in AD DS?) |
- | | | |
- | v v |
- | [AUTHORIZED] [UNAUTHORIZED: ROGUE STATE] |
- | - Services - DHCP Server Service Shuts Down Automatically |
- | client leases - Logs Event ID 1046 in System Event Log |
- | - Event ID 1044 - Refuses to service client DHCPDISCOVER packets |
- +-----------------------------------------------------------------------------+
Authorization Rules and Mechanics:
Directory Storage: Authorized DHCP servers are registered in the Active Directory Configuration partition under:
CN=NetServices,CN=Services,CN=Configuration,DC=contoso,DC=com
Administrative Privilege: Authorizing a DHCP server requires membership in the Enterprise Admins group (or delegated write permissions to the NetServices container).
Operating States:
Domain-Joined DHCP Server: On service startup, the server broadcasts a DHCPINFORM query and checks the AD DS NetServices container. If its IP/FQDN is listed, it initializes (Event ID 1044). If not listed, it logs Event ID 1046 and halts the DHCP Server service immediately.
Standalone (Non-Domain) DHCP Server: If a standalone DHCP server boots onto a subnet where a domain exists and detects an authorized domain DHCP server, the standalone server shuts down automatically. If no domain is detected, it operates independently in a workgroup. # Authorize a domain-joined DHCP Server in Active Directory
Add-DhcpServerInDC -DnsName 'dhcp01.corp.contoso.com' -IPAddress 10.10.1.10
- # Query all authorized DHCP servers across the AD DS Forest
- Get-DhcpServerInDC
- # Remove authorization for a decommissioned server
- Remove-DhcpServerInDC -DnsName 'dhcp-old.corp.contoso.com'