| Previous | Next |
| DNS_ERROR_VIRTUALIZATION_INSTANCE_ALREADY_EXISTS | DNS_ERROR_VIRTUALIZATION_TREE_LOCKED |
DNS_ERROR_VIRTUALIZATION_INSTANCE_DOES_NOT_EXIST
The management request refers to a missing virtualization instance
Windows DNS virtualization instances create separate logical containers for zones and zone scopes. MS-DNSP requires delete and update operations to first locate the named instance and returns an error when it is absent. The default instance is represented separately from named tenant-style instances, so an omitted or mistyped identifier can select the wrong management context.
Enumerate instances on the exact DNS server that received the request and compare the identifier supplied by the client. Do not infer existence from a zone with the same name on another virtualization instance: identical zone names can be hosted in different instances. If automation persists instance IDs, verify that it has not reused an identifier from another DNS server.
What to inspect
- Run instance enumeration on the target DNS server, not a peer server.
- Compare the exact virtualization instance ID and the default instance representation.
- Check automation inventory for stale or server-specific instance identifiers.
References
- Microsoft: DNS Server virtualization instances
- MS-DNSP: DNS Server management operations
- Microsoft: Get-DnsServerZone and zone state properties
Looking for a different code? Search another status or error code.