Skip to content
AdminKit

Zone transfer (AXFR)

What is Zone transfer (AXFR)?

A zone transfer (AXFR) is the DNS mechanism a secondary nameserver uses to copy an entire zone's records in one bulk request, meant only for legitimate replication between a domain's own servers. A server misconfigured to answer AXFR for anyone leaks every record at once. AdminKit's DNS lookup tool checks individual records the safe way.

By AdminKit team, Netbase JSC · Updated

A zone transfer (AXFR), defined in RFC 5936, is the DNS mechanism a secondary nameserver uses to copy an entire zone’s records in one bulk request from the primary authoritative server, rather than querying one record at a time the way ordinary resolution works. AXFR and IXFR are registered as QTYPE values 252 and 251 respectively in IANA’s DNS Parameters registry. It exists for legitimate nameserver replication, but an authoritative server misconfigured to answer AXFR requests from any client, not just its designated secondaries, hands an attacker the domain’s complete record set in a single query — every subdomain, mail server, and internal-sounding hostname at once, information otherwise only discoverable by guessing. Modern DNS providers restrict AXFR to an explicit allow-list of secondary IPs by default; a domain owner can confirm their own setup doesn’t permit open transfers rather than assuming it’s locked down — the same restriction NIST’s DNS deployment guide recommends for limiting who can pull a full zone. PowerDNS Authoritative Server is one example of a restrictive default: its allow-axfr-ips setting lets only 127.0.0.0/8 and ::1 perform AXFR without TSIG unless the operator widens it, and its documentation warns that a transfer authorized with a TSIG key is not checked against that list. A ZONEMD record addresses a related but separate concern — not who’s allowed to request a transfer, but whether the zone a recipient received actually matches what the primary published. A primary nameserver normally triggers that transfer right after a change using DNS NOTIFY, rather than waiting for the secondary’s next scheduled poll of the zone’s SOA serial. A secondary doesn’t have to pull the entire zone on every change, either: IXFR, defined in RFC 1995, requests only the records that changed since its last known serial, falling back to a full AXFR only when the primary can’t reconstruct that incremental diff.

AdminKit groups zone transfer (AXFR) under its DNS cluster — browse the AdminKit glossary index for other related terms.

Frequently asked questions

Is it a security risk if a nameserver allows AXFR from anyone?

Yes -- a server misconfigured to answer AXFR requests from any client, not just its designated secondaries, hands an attacker the domain's complete record set in a single query, information otherwise only discoverable by guessing.

What's the difference between AXFR and IXFR?

AXFR copies an entire zone's records in one bulk request every time, while IXFR (RFC 1995) requests only the records that changed since the secondary's last known serial, falling back to a full AXFR only when the primary can't reconstruct that incremental diff.

Do modern DNS providers leave AXFR open by default?

No -- modern DNS providers restrict AXFR to an explicit allow-list of secondary IPs by default, though a domain owner should confirm their own setup doesn't permit open transfers rather than assume it.

How does a secondary nameserver know when to request a zone transfer?

A primary nameserver normally triggers it right after a change using DNS NOTIFY, rather than the secondary waiting for its next scheduled poll of the zone's SOA serial.