Skip to content
AdminKit

IXFR (Incremental Zone Transfer)

What is IXFR (Incremental Zone Transfer)?

IXFR, defined in RFC 1995, lets a secondary nameserver pull only the records that changed since its last transfer, instead of re-pulling the whole zone the way AXFR does. DNS NOTIFY (RFC 1996) is what normally prompts that check. AdminKit's zone-transfer guide covers the full AXFR transfer IXFR is a smaller, cheaper alternative to.

By AdminKit team, Netbase JSC · Updated

IXFR, defined in RFC 1995, lets a secondary nameserver request only the records that changed in a zone since the serial number it already has, instead of pulling every record the way a full AXFR transfer does — both query types are registered values in IANA’s DNS Parameters registry. A secondary sends its current SOA serial in the request; if the primary has kept a journal of changes since that serial, it replies with an ordered list of the specific records removed and added to reach the current version, far cheaper to send and apply on a large zone that only changed a handful of records. If the primary can’t reconstruct that incremental diff — its journal doesn’t go back far enough, or it doesn’t keep one at all — RFC 1995 has it fall back to a full zone transfer instead, so an incremental request always gets a usable answer either way; ISC’s BIND 9 reference manual documents the provide-ixfr and request-ixfr options that control this behavior on the most widely deployed nameserver software. Knot DNS’s configuration reference exposes the same choice through its provide-ixfr option, which when disabled forces the server to answer IXFR queries with AXFR, and by default keeps a zone’s change history in its journal. In practice, DNS NOTIFY, defined in RFC 1996, is what normally prompts a secondary to check its serial in the first place, with IXFR, or AXFR as the fallback, as the transfer that follows.

AdminKit groups iXFR (Incremental Zone Transfer) under its DNS cluster — browse the AdminKit glossary index for other related terms.

Frequently asked questions

What does IXFR transfer that a full AXFR doesn't skip?

Only the records that changed in a zone since the serial number the secondary already has, rather than every record in the zone.

What happens if the primary can't reconstruct an incremental diff?

RFC 1995 has it fall back to a full zone transfer instead, so an incremental request always gets a usable answer either way.

What normally prompts a secondary to check its serial and request IXFR?

DNS NOTIFY, defined in RFC 1996, which the primary sends to tell secondaries a zone has changed.