Feature Request: More verbose logging of XFR details

[klaus-nicat]

Hi! I am using NSD as secondary. While debugging XFRs. from logs it is not possible to find out what kind of XFR was performed:

• IXFR?
• IXFR with fallback to AXFR?
• AXFR-style IXFR (Primary server does not have journal)
• AXFR?

So it would be great if NSD logs what kind of request was tried, and what finally was performed. At the moment I get this info reading the logs from the primary (Bind9) - but this is a workaround and only possible if I have access to the Primary too.

[johanix]

Speaking of more verbose logging of XFRs: I recently had the problem that NSD (as the secondary) refused to transfer a zone from my code (as the primary). I'm fully aware that it was my code that was at fault, but even with verbosity turned to 25 the only thing NSD said was "bad xfr". Inspection of the zone via "dig ... axfr" worked fine, but revealed nothing strange, and another server implementation (Knot-DNS) accepted the zone witout complaints.

Here is a vote for a bit more detail than "bad xfr"... :-)

Cheers, Johan