Klaus Darilion <klaus.mailingli...@pernau.at> wrote: > > I wonder how Bind as master handles IXFR when the requested IXFR would > be much than the AXFR. (For example: if you change the NSEC3 salt). > > Are there some mechanisms to detect such a situation and trigger a > fallback to AXFR or will Bind always perform IXFR?
No. It's only relatively recently that BIND has been able to keep track of the zone size (which is used for the max-records safety limit) and the IXFR code has not been taught how to use this information to fall back to AXFR when that would make sense. > PS: AFAIK the max journal size is 2 GB. Not since 9.12 :-) I fixed it so that the default journal size limit is 2x the zone size. The journal is reduced to half size when it is compacted, so this limit is enough to support IXFR in any case where it might be beneficial, but it also supports oversize IXFRs. > In my case, the IXFR due to NSEC3 salt changes is around 2.5GB. So > actually I am surprised that such big updates can be handled as IXFR. Yes, that is curious. Are you sure it isn't actually doing an IXFR-flavoured AXFR of the whole zone, rather than a delta? Tony. -- f.anthony.n.finch <d...@dotat.at> http://dotat.at/ Gibraltar Point to North Foreland: Northerly or northwesterly 3 or 4, occasionally 5 at first, becoming variable for a time in Thames estuary. Smooth or slight. Thundery showers at first, fog patches for a time later in north. Moderate or good, occasionally very poor for a time later in north. _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
