Why log a failed transfer successfully?
Anand Buddhdev
anandb at ripe.net
Thu Apr 2 08:01:33 UTC 2015
I'm parsing BIND logs to extract the XFR size in bytes of a zone, and
was just bitten by this sequence:
02-Apr-2015 04:27:10.393 xfer-in: transfer of './IN' from
2001:67c:2e8:5::c100:c6#53: failed to connect: timed out
02-Apr-2015 04:27:10.393 xfer-in: transfer of './IN' from
2001:67c:2e8:5::c100:c6#53: Transfer completed: 0 messages, 0 records, 0
bytes, 62.999 secs (0 bytes/s
ec)
So BIND wasn't even able to connect to the master, but subsequently
logged "Transfer completed".
Is there any logic to this that I'm missing?
Regards,
Anand
More information about the bind-users
mailing list