Correlation between NOTIFY-Source and AXFR-Source

[Klaus Darilion]

Hello!

I always was quite sure that Bind will request XFR from the Primary that sent the NOTIFY.

config:
    masters {
        X.X.X.4;
        X.X.X.20;
    };

Bind Version 9.11.5.P4+dfsg-5.1+deb10u8

But I just saw this in the logs that the first NOTIFY is received from .20, but AXFR is performed from .4:

15:31:17.715 general: info: zone versicherung/IN: notify from X.X.X.20#39334: serial 1678375865
15:31:17.716 general: info: zone versicherung/IN: Transfer started.
15:31:17.716 xfer-in: info: transfer of 'versicherung/IN' from X.X.X.4#53: connected using X.X.X.113#43555 TSIG rcode0-distribution
15:31:17.720 general: info: zone versicherung/IN: transferred serial 1678375865: TSIG 'rcode0-distribution'
15:31:17.720 xfer-in: info: transfer of 'versicherung/IN' from X.X.X.4#53: Transfer status: success
15:31:17.720 xfer-in: info: transfer of 'versicherung/IN' from X.X.X.4#53: Transfer completed: 1 messages, 82 records, 14703 bytes, 0.004 secs (3675750 bytes/sec)
15:31:20.001 notify: info: client @0x7fdb840c94a0 X.X.X.4#49990/key rcode0-distribution: received notify for zone 'versicherung': TSIG 'rcode0-distribution'
15:31:20.001 general: info: zone versicherung/IN: notify from X.X.X.4#49990: zone is up to date

Is there really no correlation between the notification source and the XFR source?

Thanks
Klaus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20230309/3dac95ae/attachment.htm>