| Previous | Next |
| DNS_ERROR_CNAME_COLLISION | DNS_ERROR_RECORD_ALREADY_EXISTS |
DNS_ERROR_RECORD_ONLY_AT_ZONE_ROOT
The record type has zone-apex placement semantics
Some DNS data describes the zone itself rather than an arbitrary host name. The clearest example is SOA, which RFC 1035 defines as authority information for the zone and which is located at the zone apex. Windows DNS validates record placement and can reject a zone-structural RR when its owner name is a descendant node.
Compare the requested owner FQDN with the exact zone name and inspect the record type. If the intent is to configure zone authority or policy, use the apex and the zone management interface. Do not move unrelated host data to the apex merely to satisfy the error: first confirm that the selected RR type is actually the one the application intended to create.
What to inspect
- Resolve the hosted zone name and compare it byte-for-byte with the requested owner FQDN after normalization.
- Inspect the RR type and its placement rules in the DNS specification or Windows DNS API.
- Correct the owner name or record type rather than duplicating zone-structural data under a child label.
References
- IETF RFC 1035: DNS resource records, SOA, and server implementation
- IETF RFC 1034: DNS namespace, zones, authority, and delegation
- Microsoft: Get-DnsServerResourceRecord
Looking for a different code? Search another status or error code.