| Previous | Next |
| DNS_INFO_AXFR_COMPLETE | DNS_INFO_ADDED_LOCAL_WINS |
DNS_ERROR_AXFR
The authoritative full-zone transfer did not complete
AXFR is the DNS protocol mechanism for transferring an entire zone between authoritative servers or to an authorized transfer client. RFC 5936 defines an AXFR session as an AXFR query followed by a sequence of response messages and specifies TCP transport. A Windows DNS AXFR error therefore belongs to zone-transfer processing, not ordinary recursive query resolution.
Check the transfer client, the server selected as source, TCP connectivity, zone-transfer policy, and the zone SOA/serial state. Confirm that the source is authoritative for the exact zone and that the request is permitted. If a secondary is failing to refresh, compare AXFR with IXFR behavior and DNS Server transfer events; changing client resolver settings will not repair the authoritative transfer path.
What to inspect
- Test TCP connectivity to the authoritative transfer source and verify the exact zone name.
- Review transfer permissions and the source server DNS logs or events.
- Inspect SOA and secondary refresh state, then determine whether full AXFR or incremental transfer was attempted.
References
- IETF RFC 5936: authoritative zone transfer with AXFR
- Microsoft: DNS zone types and zone transfer behavior
- Microsoft: Add-DnsServerSecondaryZone and required master servers
Looking for a different code? Search another status or error code.