Package: unbound Version: 1.9.0-2 Severity: normal Dear Maintainer,
after upgrading unbound from 1.8.1-1 to 1.9.0-2, I noticed that reloading unbound via systemctl (or unbound-control reload) does not work anymore. Unbound complains that remote-control is not enabled. I looked at the changes from the two versions and found that up until version 1.8.1-1, Debian shipped a patch changing the default for cfg->remote_control_enable from 0 to 1 in util/config_file.c, meaning the remote control interface is enabled by default. This patch was dropped in 1.9.0-2, but the change was not documented. This also constitutes a regression since the systemd unit file shipped with unbound relies on unbound-control to reload the unbound configuration. As the remote control interface defaults to disabled now, reloading fails. Please consider adding said patch again or remove the ExecReload command from the systemd unit file and update the changelog to indicate the change of the default behavior. Note: I'm using a local backport of 1.9.0-2 on Debian Stretch, which is a mere backport of Testing without any additional changes. But looking a the source code and the observations I described above, I don't think that matters here. Thanks!
