Re: [knot-dns-users] 1.5.0 - 1.5.1 bind IXFR problems

Hi, On 20 Aug 2014, at 13:13 , Jan Kadlec <jan.kadlec(a)nic.cz> wrote: Note that according to protocol the sender is allowed to respond with an AXFR if is so chooses. This is obviously needed, because the sender can not know in advance how much history it needs to keep (i.e. when a slave requests an IXFR it could be two versions behind or two thousand versions behind). Hence the sender keeps as much history as it feels like / has memory for / is configured to / whatever, and if an IXFR request is for a larger delta then an AXFR will be sent. Eg. this is not an error and should not be flagged as such. That is not correct. BIND9 will use IXFRs automatically in most cases. The ixfr-from-differences is only needed in cases like: PM -- S1 -- S2 Where "PM" (for whatever reason) only provides AXFR (to S1) and S1 then only will provide AXFR to S2 *unless* configured to do "ixfr-from-differences", in which case S1 will compute all the IXFR diffs needed. Regards, Johan