Fix Domain Controller Time: Configure NTP Server Properly

A sysadmin in a server room checks his wristwatch against the wall clock, a laptop on the equipment cart behind him.
AI-generated illustration

Updated November 14, 2026 with AI assistance. Vendor references are linked below. Command examples require review for your environment.

Identify the time-source role

In a typical Active Directory forest, configure the forest-root PDC emulator to use approved external time sources. Other domain controllers and member computers normally use the domain hierarchy. Check virtualization host time integration and organizational policy before changing this design.

netdom query fsmo
w32tm /query /source
w32tm /query /status
w32tm /query /configuration

Understand peer flags

For a manual peer, 0x8 selects client mode. 0x1 selects SpecialInterval; it does not mean client mode. A combined flag such as 0x9 requests both. Select flags and polling settings from the intended server configuration and Microsoft’s documentation rather than assuming one flag fits every peer.

External configuration belongs on the appropriate PDC

Run the following elevated command-prompt example only on the confirmed forest-root PDC emulator, after replacing the peers with approved NTP servers. It changes that computer’s time configuration.

w32tm /config /manualpeerlist:"ntp1.example.net,0x8 ntp2.example.net,0x8" /syncfromflags:manual /reliable:yes /update
w32tm /resync /rediscover
w32tm /query /peers
w32tm /query /source

Verify the hierarchy

For ordinary domain members, the expected synchronization type is normally NT5DS. If a machine was manually overridden, determine whether policy or a local setting should restore the domain hierarchy; do not copy the PDC command to every server. Check UDP 123 reachability, DNS and Windows Time events, then verify source, offset and successful synchronization. A resync failure needs diagnosis rather than repeated configuration changes.

Sources