Unbound has problems when a zone goes from unsigned to signed?

Unbound
1

I had to restart my Unbound resolver to get something else than
SERVFAIL (BIND had no issues) for 192.in-addr.arpa. I vaguely remember
a problem with Unbound when a zone goes from unsigned to signed. Is it
still true?

Unbound 1.3.0 on Debian/Linux, no forwarder, using dlv.isc.org.

2

Hi Stephane,

I am sorry, how would that SERVFAIL be caused, can you give me debug
verbose logs of this?

I do not remember the problem you think of, what is that?
Is it the report that you later retracted about unbound troubles with
NSEC3 and DLV, which turned out to be really one of your BIND servers?

Best regards,
   Wouter