| Previous | Next |
| DNS_ERROR_INVAILD_VIRTUALIZATION_INSTANCE_NAME | DNS_ERROR_ZONESCOPE_ALREADY_EXISTS |
DNS_ERROR_DEFAULT_VIRTUALIZATION_INSTANCE
The default virtualization instance is not a normal tenant container
Windows DNS exposes a default virtualization instance that is functionally equivalent to the standard non-virtualized DNS server context. Microsoft PowerShell documentation shows the default instance represented by a period and lists it alongside named virtualization instances. The default container is foundational server state rather than a user-created instance with an ordinary lifecycle.
Check whether automation accidentally resolved an empty, default, or period identifier when it intended a named instance. Manage zones in the default instance through ordinary zone operations, and create a separate named virtualization instance when tenant isolation is required. Do not attempt to delete and recreate the default instance as a way to reset DNS Server configuration.
What to inspect
- Enumerate virtualization instances and identify the entry whose friendly name is Default.
- Trace how the management client selected the instance identifier.
- Use zone operations for the default context or provision a distinct named instance for isolated zone trees.
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.