IXFR file getting deleted/ max-ixfr-log-size option

Danny Mayer mayer at gis.net
Mon Dec 3 01:43:44 UTC 2001

At 03:23 PM 11/29/01, Richard Caissie (EUD) wrote:
>The max-ixfr-log-size option is documented as being slated for a future 
>release.  In the
>code the default max-ixfr-log-size is 20.  There is a problem where the 
>ixfr maintenance
>event is executed before the notify is sent.  At 20 bytes the ixfr 
>maintenance often cleans
>up the file before it can be used in an IXFR forcing an AXFR.  If the 
>updates come every 5
>minutes or so, then it is possible that an IXFR will never occur.
>Are there any plans on either getting a better default, or documenting the 
>option as working?
>I tested it with 8.2.4 and it does seem to work.

max-ixfr-log-size has been made obsolete in BIND 9 and replaced with
max-journal-size which performs a similar function. I suggest you upgrade
to BIND 9.2.0.


More information about the bind-workers mailing list