| Previous | Next |
| DNS_ERROR_ZONE_ALREADY_EXISTS | DNS_ERROR_INVALID_ZONE_TYPE |
DNS_ERROR_AUTOZONE_ALREADY_EXISTS
An auto-created DNS zone already occupies this server slot
Windows DNS has a concept of auto-created zones that is distinct from ordinary administrator-created primary and secondary zones. MS-DNSP product behavior documents automatic reverse zones such as 0.in-addr.arpa, 127.in-addr.arpa, and 255.in-addr.arpa as a recursion-avoidance optimization, and management operations treat zones marked AutoCreated specially.
Enumerate the zone and check its auto-created state before attempting another create operation. If the application is trying to provision a normal zone with the same name, inspect why it selected a reserved or automatically managed namespace. Deleting an automatic zone just to make a create call succeed can change resolver behavior and is not equivalent to replacing an ordinary hosted zone.
What to inspect
- Inspect zone name, zone type, and the auto-created flag returned by DNS Server management APIs.
- Trace the provisioning input that chose the automatic zone name.
- Do not convert an auto-created zone into an application-managed zone without understanding the server behavior it provides.
References
- MS-DNSP: DNS Server management operations
- Microsoft: Get-DnsServerZone and zone state properties
- IETF RFC 1034: DNS namespace, zones, authority, and delegation
Looking for a different code? Search another status or error code.