What does Windows error code 9716 (DNS_WARNING_DOMAIN_UNDELETED) mean?

Previous	Next
DNS_WARNING_PTR_CREATE_FAILED	DNS_ERROR_DS_UNAVAILABLE

DNS_WARNING_DOMAIN_UNDELETED

DNS domain was undeleted.

DNS_WARNING_DOMAIN_UNDELETED is Windows status 9716 (0x000025F4) associated with deletion of DNS data where the domain node remains because other data still exists. The system meaning is “this condition” Preserve the value at the API boundary because subsequent cleanup or logging calls can overwrite the last-error state.

Operational meaning

The key question is whether the caller recognizes that requested records may be removed even though the containing domain node is retained. The value describes deletion of DNS data where the domain node remains because other data still exists; it does not prove that the whole domain, DNS service, network, servicing stack, application package, or operating system has failed.

Likely impact: Treating the warning as total failure can cause duplicate cleanup; treating it as full deletion can leave stale data. Record the scope that was actually tested instead of escalating from one rejected object or phase to a system-wide outage.

Where the result appears

• This result can appear while processing deletion of DNS data where the domain node remains because other data still exists.
• This result can appear while a DNS Server API request that validates a zone, record, property, or server setting.
• This result can appear while a dynamic update, zone transfer, WINS integration, or reverse-record workflow.
• It can appear while a management script or DNS console operation translated to a Win32 DNS status.

Typical causes

• child nodes or other record sets remain.
• directory-integrated metadata keeps the node.
• the delete targeted only one record set.
• replication exposes surviving data.

Diagnostic sequence

1. capture it immediately after the failing or status-returning call and record whether the API uses Win32, DNS_STATUS, HRESULT conversion, or callback semantics.
2. identify the exact target involved in deletion of DNS data where the domain node remains because other data still exists, including stable GUIDs, DNs, zone names, package identities, file hashes, policy names, or process identifiers as applicable.
3. prove the state boundary: the caller recognizes that requested records may be removed even though the containing domain node is retained.
4. collect requested delete scope and remaining record sets and children before restarting services, deleting objects, rebuilding packages, or changing policy.
5. correlate zone storage type with the DNS Server event log, DNS analytical logging when enabled, packet capture, zone metadata, server configuration, and the exact DNS API request.
6. determine whether the result is a failure, warning, informational completion, continuation request, or marker constant before choosing retry behavior.
7. after changing one responsible condition, repeat the same smallest operation and verify both success and absence of unintended partial effects.

Evidence to preserve

• collect requested delete scope.
• collect remaining record sets and children.
• collect zone storage type.
• collect AD replication metadata.
• collect post-delete authoritative query.

Correlate this evidence with the DNS Server event log, DNS analytical logging when enabled, packet capture, zone metadata, server configuration, and the exact DNS API request. Preserve raw identifiers and the first detailed diagnostic: translating everything to 9716 can hide whether the cause was validation, topology, authorization, replication, policy, file I/O, packaging, or an intentional continuation state.

Recovery and retry

The recovery objective for it is to verify which records were deleted, inventory the surviving node, and remove additional data only when ownership and dependencies are known.

Retry only after the recorded boundary changes and prior completion is known. Read-only discovery for it can usually be repeated with bounded backoff; directory mutations, DNS updates, policy installation, servicing actions, and PRI writes require a state check first. Backoff for it cannot repair malformed input, unsupported structure, identity collision, missing authority, or incompatible package metadata.

Telemetry and support fields

• record warning_domain_undeleted_operation — producing API, command, callback, or servicing phase.
• record warning_domain_undeleted_target — stable object, zone, policy, package, file, or account identity.
• record warning_domain_undeleted_state_before and warning_domain_undeleted_requested_state.
• record warning_domain_undeleted_first_status — earliest component-specific code before translation.
• record warning_domain_undeleted_server, warning_domain_undeleted_process, UTC timestamp, and correlation ID.

A support bundle for it should include decimal 9716, hexadecimal 0x000025F4, the smallest reproducible request, target identity, effective configuration, and evidence from the owning Windows component. When documenting it, remove secrets from exported logs but keep SIDs, GUIDs, package-family names, record types, and hashes when they are needed to distinguish objects.

Difference from nearby results

DNS_ERROR_RECORD_DOES_NOT_EXIST reports no target record; this warning reports a partial structural outcome after deletion This distinction determines whether the correct next step is input correction, topology repair, continuation, policy review, package rebuild, or no error handling at all.

Practical validation scenario

An administrator deletes one record set and expects the DNS node to disappear. Enumerating child and metadata records explains why the domain remains. A negative test should reproduce it with the responsible condition preserved; the recovery test should alter only that condition and confirm the intended final state.

Developer and administrator guidance

Developers should model it explicitly in the result domain instead of collapsing every nonzero value into “failed.” Administrators should capture evidence before destructive remediation and use the component that owns deletion of DNS data where the domain node remains because other data still exists. Monitoring for it should suppress range markers and classify warning, informational, cancellation, and continuation values separately from terminal failures.

References

• Microsoft: exact Win32 system error range — official context relevant to it.
• Microsoft: DNS server troubleshooting — official context relevant to it.
• Microsoft: DNS logging and diagnostics — official context relevant to it.

---

Looking for a different code? Search another status or error code.