1 Zář
2014
1 Zář
'14
15:38
Hi Jan,
On 29 Aug 2014, at 09:26 , Jan Kadlec <jan.kadlec(a)nic.cz> wrote:
Excellent.
I think it depends on how one modifies his zone.
Correct. That's why I said "most" cases. So I think we're in complete
agreement here.
On 20 Aug
2014, at 13:13 , Jan Kadlec <jan.kadlec(a)nic.cz> wrote:
Eg. this is not an error and should not be flagged as such.
You're definitely right that this should not be treated as error (and this goes to
any error during IXFR I suppose), because indeed there are cases when AXFR-style IXFR
response is valid, Knot sends such responses as well. Our reasoning here was that this
should happen rarely when things are set up properly, and, more importantly, we did not
want to bloat the IXFR processing code. Nevertheless, we will fix this in the upcoming
update. It's been a while since I had to configure Bind,
but I think you have to explicitly enable IXFR (ixfr-from-differences option and journal)
or it will just send AXFRs for all requests.
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. So it seems for the manual zone file change + rndc
reload combo you still need ixfr-from-differences enabled, but I'll admit I
haven't tested this. I did not know BIND can create IXFRs from diffs between AXFRs,
that's an interesting feature we might add to Knot.
I would love to see that in Knot. That would be really great.
Regards,
Johan