| Previous | Next |
| DNS_ERROR_NO_CREATE_CACHE_DATA | DNS_WARNING_PTR_CREATE_FAILED |
DNS_ERROR_NAME_DOES_NOT_EXIST
The owner name is missing from the selected DNS data set
DNS distinguishes a nonexistent name from an existing name that lacks one requested RR type. RFC 2136 makes this distinction explicit in dynamic-update prerequisites, and RFC 1034 models each namespace node as a set of resource information that can be empty or populated. Windows management operations can likewise fail because the node itself cannot be found.
Confirm the zone and owner name separately, then enumerate all record types at that owner. A typo in the relative name, the wrong zone, a delegated subtree, DNAME redirection, or a deleted AD-integrated dnsNode can all make an apparently familiar FQDN absent in the data set being modified. Do not create the name blindly until the intended authoritative boundary is confirmed.
What to inspect
- Verify the exact FQDN and the zone passed to the management operation.
- Enumerate the owner across all RR types instead of querying only the intended type.
- Check delegation, DNAME, and AD-integrated tombstone state before recreating a missing node.
References
- IETF RFC 2136: DNS dynamic update prerequisites and update processing
- IETF RFC 1034: DNS namespace, zones, authority, and delegation
- MS-DNSP: dnsRecord storage format for directory-integrated zones
Looking for a different code? Search another status or error code.