Open rootwyrm opened 4 years ago
@ralphdolmans Are you interested in help with implementing this? :) I'm more than happy to submit a pull request. :)
I stumbled across this in our production environment, and I do agree that this error message should be displayed even with verbosity level set to 1. Would have saved me a bunch of head scratching if that would have been the case. :)
Found this one due to a frustrating configuration error (I had a typo I kept missing.) But it definitely pointed to a bug. If the SOA is invalid for an RPZ, Unbound will silently fail to transfer the zone, even if forced. Which will leave you scratching your head for a few hours until you turn the verbosity way up.
The problem here is that these errors do not appear until you turn the verbosity up above I believe 4 or 5.
An SOA probe failure resulting in no AXFR/IXFR should be considered a major operational error - particularly in the RPZ context - and should be logged at
verbosity: 1
since the failure will prevent the RPZ from working at all on an initial AXFR. Leaving any environment that doesn't check for the existence of the zone file unaware that their RPZ is non-functioning.Found this on Unbound 1.10.1;