Study guide

10.2 DNS Records, Aging & Scavenging and the GlobalNames Zone

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.2 DNS Records, Aging & Scavenging and the GlobalNames Zone

Key Takeaways Explain This Topic AI

Active Directory publishes its locator data as SRV records under _msdcs; losing those records breaks domain join, logon, and replication even when A records resolve normally.

Aging and scavenging must be enabled at both the DNS server and the zone before any stale record is ever removed.

A record becomes eligible for scavenging only after the No-Refresh interval plus the Refresh interval have both elapsed, which is 14 days at the 7-day plus 7-day defaults.

The scavenging period controls how often the server actually runs the cleanup pass, so worst-case removal time is No-Refresh plus Refresh plus one scavenging period.

The GlobalNames Zone resolves single-label names forest-wide using CNAME aliases and is the supported modern replacement for WINS.

Last updated: August 2026

  • DNS Records, Aging & Scavenging and the GlobalNames Zone
  • 1. DNS Record Management & AD DS Service Location (SRV Records)

Active Directory relies on Service Location (SRV) records (RFC 2782) to allow domain-joined workstations, member servers, and applications to locate domain controllers, Kerberos Key Distribution Centers (KDCs), Global Catalogs, and LDAP services. +-----------------------------------------------------------------------------+

  • | SRV RECORD FORMAT & STRUCTURE |
  • | |
  • | _Service._Proto.Name TTL Class SRV Priority Weight Port Target |
  • | ------------------------------------------------------------------------- |
  • | _ldap._tcp.dc._msdcs 600 IN SRV 0 100 389 dc01...|
  • | | | | | | | | |
  • | | | +-- Subdomain / Scope | | | +Host|
  • | | +------- Transport Protocol (TCP/UDP)| | +Port |
  • | +-------------- Service Name | +Load Balancing |
  • | +Preference (Lower First) |
  • +-----------------------------------------------------------------------------+

Critical AD DS SRV Records:

_ldap._tcp.dc._msdcs.<DomainName> : Enables clients to locate domain controllers running LDAP directory services on TCP port 389.

_kerberos._tcp.<DomainName> : Identifies KDC authentication servers running on TCP port 88.

_gc._tcp.<ForestRootName> : Locates Global Catalog servers across the forest on TCP port 3268.

_kpasswd._tcp.<DomainName> : Locates Kerberos password change servers on TCP port 464. # PowerShell: Querying and Creating Critical DNS Resource Records

  • # 1. Retrieve all SRV records for domain controller locator in contoso.com
  • Get-DnsServerResourceRecord -ZoneName 'contoso.com' -RRType SRV |
  • Where-Object { $_.HostName -like '_ldap._tcp*' }
  • # 2. Add an AD-Integrated Primary Forward Lookup Zone in the DomainDNSZones partition
  • Add-DnsServerPrimaryZone `
  • Name 'corp.contoso.com' `
  • ReplicationScope 'Domain' `
  • DynamicUpdate 'Secure'
  • # 3. Create an A record and alias CNAME record
  • Add-DnsServerResourceRecordA -ZoneName 'corp.contoso.com' -Name 'app01' -IPv4Address '10.10.4.50' -CreatePtr

Add-DnsServerResourceRecordCName -ZoneName 'corp.contoso.com' -Name 'fileshare' -HostNameAlias 'app01.corp.contoso.com.'

2. Zone Aging and Scavenging Mechanics

When dynamic updates are enabled, dynamically registered records accumulate over time. When laptops leave the organization, virtual machines are decommissioned, or DHCP leases change, orphaned DNS records remain in the zone. Aging and Scavenging is the automated mechanism that purges stale dynamic records. +-----------------------------------------------------------------------------+

  • | DNS AGING AND SCAVENGING TIMELINE LIFECYCLE |
  • | |
  • | [RECORD CREATED] |
  • | Timestamp: Day 0 |
  • | | |
  • | v |
  • | +-----------------------+ NO-REFRESH INTERVAL (Default: 7 Days) |
  • | | Server IGNORES record | - Dynamic updates with same IP do NOT advance |
  • | | timestamp refreshes | the timestamp. |
  • | +-----------------------+ - Reduces Active Directory replication traffic.|
  • | | |
  • | v Day 7 |
  • | +-----------------------+ REFRESH INTERVAL (Default: 7 Days) |
  • | | Server ACCEPTS record | - Dynamic updates ARE accepted and advance |
  • | | timestamp refreshes | the timestamp back to Day 0. |
  • | +-----------------------+ |
  • | | |
  • | v Day 14 |
  • | [RECORD BECOMES STALE] ---> Record is eligible for Scavenging |
  • | | |
  • | v (Scavenging thread runs every 7 Days) |
  • | [RECORD DELETED] ---> Purged from Active Directory database |
  • +-----------------------------------------------------------------------------+

Scavenging Parameters and Timers:

Record Timestamp: Static records have a timestamp of 0 (never scavenged). Dynamic records receive a timestamp reflecting the date and time of creation or refresh.

No-Refresh Interval (Default: 7 Days):

During this window, the DNS server accepts DNS query traffic and name changes, but suppresses timestamp updates if the IP address has not changed.

Purpose: Prevents massive AD DS replication storms across domain controllers caused by clients repeatedly updating their unchanged timestamps.

Refresh Interval (Default: 7 Days):

During this window, dynamic updates from the client are accepted, and the record timestamp is reset to the current time, restarting the No-Refresh interval.

Stale Threshold Calculation: Stale Threshold = Record Timestamp + No-Refresh Interval + Refresh Interval \text{Stale Threshold} = \text{Record Timestamp} + \text{No-Refresh Interval} + \text{Refresh Interval} Stale Threshold = Record Timestamp + No-Refresh Interval + Refresh Interval With default 7-day intervals, a record becomes stale after 14 days without a refresh.

Scavenging Period (Server-Level Execution):

The recurring interval (default 7 days) at which the DNS server initiates the background scavenging thread to delete stale records.

Important

The Dual-Level Activation Rule: Scavenging will NEVER execute unless it is explicitly enabled at both levels:

Server Level: The DNS server must be designated as a scavenging server.

Zone Level: Aging and scavenging must be enabled on the target zone properties.

If enabled at the zone level but not at the server level, records age but are never deleted. # PowerShell: Enabling Scavenging at Server and Zone Levels

  • # 1. Enable Aging on the target AD-integrated zone
  • Set-DnsServerZoneAging `
  • ZoneName 'corp.contoso.com' `
  • Aging $true `
  • NoRefreshInterval (New-TimeSpan -Days 7) `
  • RefreshInterval (New-TimeSpan -Days 7)
  • # 2. Configure Scavenging at the Server Level
  • Set-DnsServerScavenging `
  • ScavengingState $true `
  • ScavengingInterval (New-TimeSpan -Days 7)
  • # 3. Manually trigger an immediate scavenging cycle
  • Start-DnsServerScavenging -Verbose
  • 3. GlobalNames Zone (GNZ) for Single-Label Name Resolution

Single-label names (e.g., http://payroll or http://intranet ) were traditionally resolved using Windows Internet Name Service (WINS) or NetBIOS broadcasts. WINS is a legacy, non-routable protocol that does not support IPv6 and introduces substantial management overhead.

The GlobalNames Zone (GNZ) provides single-label name resolution across an entire Active Directory forest using standard, routable DNS infrastructure. +-----------------------------------------------------------------------------+

  • | GLOBALNAMES ZONE RESOLUTION SEQUENCE |
  • | |
  • | [Client Browser] ---> Requests single-label name: http://erp |
  • | | |
  • | v |
  • | [Local DNS Server] |
  • | 1. Appends local DNS suffix search list (e.g., erp.corp.contoso.com) |
  • | 2. If local lookup returns NXDOMAIN: |
  • | 3. Checks authoritative GlobalNames Zone: |
  • | - Finds CNAME: erp -> app-prod-01.finance.contoso.com |
  • | 4. Resolves target FQDN and returns IPv4/IPv6 address to Client |
  • +-----------------------------------------------------------------------------+

GlobalNames Deployment Rules:

Create an AD-Integrated forward lookup zone named explicitly GlobalNames .

Store the zone in the ForestDNSZones application partition to ensure all DNS servers in the forest hold a replica.

Enable GlobalNames support on every participating DNS server via PowerShell ( Set-DnsServerGlobalNameZone -Enable $true ).

Populate the zone primarily with CNAME records pointing to the canonical FQDN of target servers.

Loading diagram... Active Directory-Integrated DNS Architecture, Replication & Scavenging Pipeline