Skip to main content

Allowing Nonsecure Dynamic Updates Lets Any Host Hijack an AD-Integrated DNS Zone

High severityActive Directory About 20 minutes to fix

Overview

An AD-integrated DNS zone left on Nonsecure and secure dynamic updates accepts unauthenticated record writes from any reachable host, letting rogue devices silently hijack names used by domain controllers and services.

At a glance

Symptom
A workstation joined to the domain registers a DNS host record with the same name as an existing server, and clients begin intermittently resolving…
Likely cause
Windows DNS zones support three dynamic update modes: None, Secure only (Kerberos/SSPI-authenticated updates via GSS-TSIG, effective only on AD-integrated zones), and Nonsecure and secure.
Impact
Any host that can reach UDP/TCP 53 on an authoritative name server for the zone can register or overwrite records for names it does not own, including names…
Verification signal
Validation confirms the zone now rejects unauthenticated updates while legitimate domain-joined clients continue to register and update their own records without manual intervention.Re-run Get-DnsServerZone -Name '' | Select-Object…
Safe correction
The correction is to change the zone's dynamic update setting from Nonsecure and secure to Secure only, which is a state-changing configuration change and must go through a…
Rollback or recovery
If the change to Secure only breaks a legitimate workflow (commonly a non-Windows appliance or a script-based registration process that cannot perform secure dynamic updates), revert the zone's…

Symptom

A workstation joined to the domain registers a DNS host record with the same name as an existing server, and clients begin intermittently resolving that name to the wrong IP address. Helpdesk tickets describe authentication failures, LDAP timeouts against what should be a domain controller, and application connection errors that come and go depending on which client cached which address. Nothing in the DNS console shows an obvious error: the zone loads, replicates and serves answers normally.

False Assumption

The team assumes that because the zone is Active Directory-integrated and replicates only between domain controllers, record writes are implicitly restricted to authenticated, authorised sources. Domain membership and zone replication scope are the boundaries everyone can see, so nobody looks at the update mechanism itself. Nobody separately checked the zone’s Dynamic Updates setting, because years earlier an administrator had configured the zone as Nonsecure and secure (AD-integrated zones default to secure updates only), and that setting was never revisited.

Root Cause

Windows DNS zones support three dynamic update modes: None, Secure only (Kerberos/SSPI-authenticated updates via GSS-TSIG, effective only on AD-integrated zones), and Nonsecure and secure. The last mode accepts secure updates when offered but will also accept plain, unauthenticated RFC 2136 dynamic updates from any host that can reach the DNS server on UDP/TCP 53, regardless of domain membership. Any device on the reachable network segment can send an unauthenticated update packet, and the server accepts it: the zone permits secure updates alongside nonsecure ones, but it does not require the update to be secure. In this mode, unauthenticated clients can create new records and overwrite records that were created by nonsecure update or that have open ACLs. Records registered securely are normally protected by their ACLs, unless they are stale, were deleted and can be re-created, or have lax permissions.

Impact

Any host that can reach UDP/TCP 53 on an authoritative name server for the zone can register or overwrite records for names it does not own, including names resembling domain controllers, file servers or line-of-business hosts, without ever authenticating to the domain. Name resolution stops being trustworthy, and that carries through to authentication (Kerberos SPN resolution), certificate issuance workflows that trust DNS for identity, and any client that resolves a service name before connecting. The damage reaches every client that queries the affected zone, not only the directly targeted record, and nothing flags it until someone notices resolution behaving unpredictably.

Diagnosis

Check the affected zone’s dynamic update setting first, before looking for any other cause. On the DNS server, open the DNS Manager console, right-click the zone, choose Properties, and read the value of the Dynamic updates dropdown on the General tab; the PowerShell equivalent in step 1 below is read-only and does not alter server state.

  1. Run Get-DnsServerZone -Name '<zonename>' | Select-Object ZoneName,DynamicUpdate,ZoneType,IsDsIntegrated on the authoritative DNS server to confirm the zone is AD-integrated and read its current DynamicUpdate value, which is one of None, NonsecureAndSecure or Secure.
  2. Run Get-DnsServerResourceRecord -ZoneName '<zonename>' -Name '<suspect-hostname>' to list every record registered under the contested name, including timestamp and record data, to see whether more than one host has claimed the name.
  3. Cross-reference the record’s owning host against DHCP lease logs or the asset inventory to identify whether the registering device is a managed, domain-joined system or an unexpected host.

Correction

Change the zone’s dynamic update setting from Nonsecure and secure to Secure only. Because this changes server configuration, it must go through a controlled maintenance path rather than being applied ad hoc. Before changing anything, capture the current setting and record inventory as a baseline, apply the change in a maintenance window, and confirm client update behaviour afterwards. An administrator makes the change by hand, in DNS Manager or an equivalent authenticated management session. No command in this article performs it, because the change must be preceded by a documented approval and baseline capture step that a generic command cannot guarantee. Work in this order: (1) capture baseline zone settings and record state using the read-only diagnosis commands above, (2) during an approved change window, set the zone’s Dynamic updates value to Secure only using DNS Manager (Zone Properties > General > Dynamic updates), (3) confirm no legitimate nonsecure-update-dependent workflow exists (for example, non-Windows devices or scripts relying on unauthenticated RFC 2136 updates), and (4) validate using the steps below.

Validation

Once the change is in, the zone should reject unauthenticated updates while legitimate domain-joined clients keep registering and updating their own records without manual intervention.

  1. Re-run Get-DnsServerZone -Name '<zonename>' | Select-Object ZoneName,DynamicUpdate and confirm the value now reads Secure.
  2. From a domain-joined test client, run ipconfig /registerdns and confirm the client’s own record still registers successfully via secure dynamic update, evidenced by a refreshed timestamp in Get-DnsServerResourceRecord for that host, or by a corresponding update entry in the DNS server’s logs. Note that static records have no timestamp.
  3. From a non-domain-joined test host on the same segment, attempt an unauthenticated dynamic update against the same zone using a testing tool (for example nsupdate in non-secure mode) and confirm the server returns a refused response and no record is created or altered.

The change has worked when legitimate secure updates succeed, unauthenticated updates are refused, and no unexplained record changes appear in the zone during a 24–48 hour monitoring window following the change.

Rollback

If the change to Secure only breaks a legitimate workflow (commonly a non-Windows appliance or a script-based registration process that cannot perform secure dynamic updates), use DNS Manager (Zone Properties > General > Dynamic updates) to set the zone’s Dynamic updates value back to the exact prior value recorded during the baseline capture step. After reverting, re-run the diagnosis commands to confirm the setting matches the pre-change baseline, and open a tracked follow-up to migrate the dependent workflow to an authenticated update path (for example, a scheduled task running under a domain identity, or a proxy service that performs secure updates on the device’s behalf) before attempting the hardening change again. A rollback with no remediation plan behind it restores the original exposure, so don’t leave the zone that way indefinitely.

Prevention

Review the DNS dynamic update mode on every AD-integrated zone as a security control, rather than treating it as a default set once at installation. Include the zone’s DynamicUpdate value in periodic configuration drift checks alongside other identity-adjacent controls referenced in benchmark-aligned hardening guidance, and require an explicit, documented exception with compensating controls (such as network segmentation restricting which hosts can reach port 53) for any zone that cannot move to Secure only. New zones created for AD-integrated DNS should default to Secure only at creation time, and any relaxation should need named approval rather than slipping in unnoticed from a wizard default.

Read-only check

Check your environment (read-only)

Show the dynamic update mode of every zone on a Windows DNS server

Based on vendor documentation; not run by KBY in a test tenant

What it shows: Each zone on the DNS server, whether it is Active Directory-integrated, and how it accepts dynamic updates.

PowerShell
# Replace <dns-server> with a DNS server name, or omit -ComputerName to query the local server.
Get-DnsServerZone -ComputerName <dns-server> |
  Select-Object ZoneName, ZoneType, IsDsIntegrated, DynamicUpdate

How to read the result

  • DynamicUpdate is one of None, Secure or NonsecureAndSecure.
  • NonsecureAndSecure means the zone accepts updates that are not authenticated. That is the setting this trap describes.
  • Secure is only available on Active Directory-integrated zones (IsDsIntegrated is True). A file-backed zone cannot be set to Secure.

You need

  • DnsServer PowerShell module.
  • An account that can read the DNS server's configuration.

Vendor documentation used

The check only reads configuration. Plan any change it points to through your normal change process.

3

Apply the safer control

Before you change production

Confirm the affected scope, export the current configuration, and test the replacement control in a non-production environment first.

Fix commands and configuration

Nonsecure and secure
None
Secure only
4

When to escalate

Validation and rollback are covered in the sections above.

Escalate

Escalate when the blast radius is uncertain, the control cannot be tested safely, or remediation requires an outage or security exception.

The KBY Brief

Fixed? Get the next one before it hits you: The KBY Brief

Practical fixes for the systems you run, by email about twice a week. Unsubscribe at any time.

About this page

Credited to

Dates

Published

Last updated

Corrections

  • : Corrected during a review of published articles. Details

Was this useful?

Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.

After remediation

Further reading stays below the corrective workflow and is selected by platform, category and shared technical keywords.

Discover more

Connected KBY resources