auth: master: misleading axfr error message when disable-axfr is enabled

[terrorobe]

When running a master with disable-axfr you get the following messages:

master: AXFR of domain 'slave.test' failed: not authoritative

slave: Unable to AXFR zone 'slave.test' from remote '62.178.148.62' (resolver): AXFR chunk with a non-zero rcode 9

Code: https://github.com/PowerDNS/pdns/blob/20010d040efcd3d578c16af4681a30b2c749d665/pdns/tcpreceiver.cc#L554

[terrorobe]

This makes things a bit more readable on the slave, but on the master I'd still like to see the !canDoAXFR(q) split away from the SOA check and read something like "...not authorized to send to..."

[Habbie]

reopened

[pieterlexis]

Fixed in 8090f5a2e8