| Previous | Next |
| DNS_ERROR_RECORD_ONLY_AT_ZONE_ROOT | DNS_ERROR_SECONDARY_DATA |
DNS_ERROR_RECORD_ALREADY_EXISTS
The exact DNS record is already present
DNS groups records into RRsets by owner name, type, and class. A server can legitimately hold several values in one RRset, such as multiple A or MX records, but adding a duplicate value does not create a second distinct piece of DNS data. Windows DNS management can reject an add when the same record is already represented in the zone.
Enumerate the complete RRset and compare normalized record data, not only the owner name. For structured types such as MX, SRV, or SOA, compare all relevant fields. If the operation was meant to replace data, use the supported update or remove-and-add semantics rather than issuing another create. RFC 2136 also distinguishes RRset existence from name existence in update prerequisites.
What to inspect
- Read all records of the same owner name and type from the authoritative zone.
- Compare the proposed RDATA with existing values using type-aware formatting.
- Use an update workflow when changing an existing record instead of retrying the duplicate add.
References
- IETF RFC 2136: DNS dynamic update prerequisites and update processing
- IETF RFC 1035: DNS resource records, SOA, and server implementation
- Microsoft: Get-DnsServerResourceRecord
Looking for a different code? Search another status or error code.