RFC 1995:Incremental Zone Transfer in DNS
RFC-Ref

IXFR


Click on the red underlined text to get to the source

... Incremental transfer (IXFR) as proposed is a more efficient mechanism, as it transfers only the changed portion(s) of a zone. ...
... In this document, a secondary name server which requests IXFR is called an IXFR client ...
... name server which requests IXFR is called an IXFR client and a primary or secondary name server which ...
... client and a primary or secondary name server which responds to the request is called an IXFR server. ...


... If an IXFR client, which likely has an older version of a zone, ...
... thinks it needs new information about the zone (typically through SOA refresh timeout or the NOTIFY mechanism), it sends an IXFR message containing the SOA serial number of its, presumably outdated, copy of ...
... An IXFR server should keep record of the newest version of the zone and the differences between that copy and several older versions ...
... and the differences between that copy and several older versions. When an IXFR request with an older version number is received, the IXFR ...
... IXFR request with an older version number is received, the IXFR server needs to send only the differences required to make that version current. Alternatively, the server may choose to transfer ...
... When a zone has been updated, it should be saved in stable storage before the new version is used to respond to IXFR (or AXFR) queries. ...
... If an IXFR query with the same or newer version number than that of ...
... query may be by either UDP or TCP. If an IXFR query is via UDP ...
... query is via UDP, the IXFR server may attempt to reply using UDP if the entire response can be contained in a single DNS packet ...
... Thus, a client should first make an IXFR query using UDP. If the ...
... client, everything is done. Otherwise, a TCP IXFR query should be tried. ...
... checksum value of zero should ignore the result and try a TCP IXFR instead. ...
... The query type value of IXFR assigned by IANA is 251. ...


... The IXFR query packet format is the same as that of a normal DNS query ...
... packet format is the same as that of a normal DNS query, but with the query type being IXFR and the authority section containing the SOA record of client ...


... AXFR response except the query type is IXFR. ...
... newest last. Thus, the differential sequences are the history of changes made since the version known by the IXFR client up to the server's current version ...
... An IXFR client, should only replace an older version with a newer ...


... An IXFR server can not be required to hold all previous versions forever and may delete ...
... forever and may delete them anytime. In general, there is a trade-off between the size of storage space and the possibility of using IXFR. ...
... Information about older versions should be purged if the total length of an IXFR response would be longer than that of an AXFR response. Given that the purpose of IXFR ...
... IXFR response would be longer than that of an AXFR response. Given that the purpose of IXFR is to reduce AXFR overhead, this ...


... An IXFR server may optionally condense multiple difference sequences into a single difference sequence, thus, dropping information on intermediate versions ...
... But, this feature may not be so useful if an IXFR client has access to two IXFR ...
... IXFR client has access to two IXFR servers: A and B, with inconsistent condensation results. The current version of the IXFR ...
... IXFR servers: A and B, with inconsistent condensation results. The current version of the IXFR client, received from server A, may be unknown to server B. In such a case, server B can not provide ...
... For interoperability, IXFR servers, including those without the condensation feature, should not flag an error even if it receives a client ...
... condensation feature, should not flag an error even if it receives a client's IXFR request with a unknown version number and should, instead, attempt to perform a full zone transfer. ...


... The following IXFR query ...
... Question | QNAME=JAIN.AD.JP., QCLASS=IN, QTYPE=IXFR | +---------------------------------------------------+ Answer | <empty> | ...
... Question | QNAME=JAIN.AD.JP., QCLASS=IN, QTYPE=IXFR | +---------------------------------------------------+ Answer | JAIN.AD ...
... Question | QNAME=JAIN.AD.JP., QCLASS=IN, QTYPE=IXFR | +---------------------------------------------------+ Answer | JAIN.AD ...
... Question | QNAME=JAIN.AD.JP., QCLASS=IN, QTYPE=IXFR | +---------------------------------------------------+ Answer | JAIN.AD ...
... Question | QNAME=JAIN.AD.JP., QCLASS=IN, QTYPE=IXFR | +---------------------------------------------------+ Answer | JAIN.AD ...


... The original idea of IXFR was conceived by Anant Kumar, Steve Hotz and Jon Postel. ...



Google
Web
RFC-Ref