| Previous | Next |
| DNS_ERROR_NO_BOOTFILE_IF_DS_ZONE | DNS_ERROR_DNAME_COLLISION |
DNS_ERROR_NODE_IS_DNAME
The owner name is already a DNAME redirection point
A DNAME RR applies to names below its owner and causes synthesized CNAME processing for matching descendants. RFC 6672 gives DNAME subtree semantics that are different from ordinary RRsets. When Windows DNS reports that the node is a DNAME, the requested operation is colliding with that special redirection role rather than simply finding another unrelated record type.
Enumerate all records at the owner and review the DNAME target. If the application intended direct records at this branch, decide whether the DNAME should be removed as a deliberate namespace migration. If the DNAME is correct, move the new data to the authoritative target subtree or another owner. Adding descendants underneath the DNAME will not make them normally visible.
What to inspect
- Read the DNAME owner and target exactly as stored in the zone.
- Check whether the requested record belongs in the redirected target namespace.
- Change the namespace design before removing DNAME from a production branch with dependent names.
References
- IETF RFC 6672: DNAME redirection and occluded descendants
- Microsoft: Get-DnsServerResourceRecord
- IETF RFC 1034: DNS namespace, zones, authority, and delegation
Looking for a different code? Search another status or error code.