| Previous | Next |
| DNS_ERROR_RECORD_ALREADY_EXISTS | DNS_ERROR_NO_CREATE_CACHE_DATA |
DNS_ERROR_SECONDARY_DATA
Secondary-zone contents are obtained from a master, not edited locally
A Windows secondary zone is a read-only authoritative copy whose data is transferred from master servers. The zone transfer model exists to keep authoritative servers coherent; local edits to the secondary data would diverge from the copy maintained by AXFR, IXFR, and refresh processing. The correct write location is the writable authority from which the secondary learns the zone.
Confirm the zone type and master-server list. Make the record or SOA change on the primary or another writable source, then allow transfer and refresh to update the secondary. If the server is supposed to accept local writes, the zone may have been created or converted to the wrong type; review the intended topology before changing zone type simply to bypass the error.
What to inspect
- Verify the target zone reports Secondary rather than Primary or AD-integrated storage.
- Identify the configured master servers and make the authoritative change there.
- Check refresh and transfer status if the corrected primary data is not reaching the secondary.
References
- Microsoft: DNS zone types and zone transfer behavior
- Microsoft: Add-DnsServerSecondaryZone and required master servers
- IETF RFC 5936: authoritative zone transfer with AXFR
Looking for a different code? Search another status or error code.