Thanks for filing this bug and helping us make Ubuntu better.
I checked unbound Noble version and we only diverge from debian in that we don't build with hiredis on i386. Therefore, the behaviour has to be the same.
Reading the unbound/changelog, since version 1.5.7-2, we can see:
* debian/resolvconf: No longer use RESOLVCONF_FORWARDERS from
/etc/default/unbound
Also, from the unbound.NEWS:
>>
unbound (1.5.7-2) unstable; urgency=medium
The unbound package no longer ships an /etc/default/unbound conffile.
If modified, it will be renamed to /etc/default/unbound.dpkg-bak after
upgrading.
The /etc/default/unbound file, if it exists, will still be read and the
behavior of the package can be modified, but the defaults have been changed
to make it unnecessary for most users to need an /etc/default/unbound
file.
The following variables are still supported by the /etc/default/unbound
file, if it exists:
[...]
RESOLVCONF
This variable now must be explicitly set to "false" to disable the
unbound package's resolvconf provider. Otherwise, it defaults to
enabled if unset.
In previous versions, this variable had to be explicitly set to "true"
to enable the resolvconf provider, but the /etc/default/unbound file
shipped with it explicitly enabled.
<<
So I suspect you can create and write your own /etc/default/unbound file with RESOLVCONF=false for the purpose you're looking for.
Due to this looks like a local configuration issue rather than a bug in the software itself, I'm marking this "Invalid" because it doesn't appear to be a bug, but if I'm wrong, please change it back to "New" and add some more info to point me in the right direction. Use this link as a guide: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
Hi Chris,
Thanks for filing this bug and helping us make Ubuntu better.
I checked unbound Noble version and we only diverge from debian in that we don't build with hiredis on i386. Therefore, the behaviour has to be the same.
Reading the unbound/changelog, since version 1.5.7-2, we can see:
* debian/ unbound. maintscript: Remove conffile /etc/default/ unbound
plus
* debian/resolvconf: No longer use RESOLVCONF_ FORWARDERS from default/ unbound
/etc/
Also, from the unbound.NEWS:
>>
unbound (1.5.7-2) unstable; urgency=medium
The unbound package no longer ships an /etc/default/ unbound conffile. unbound. dpkg-bak after
If modified, it will be renamed to /etc/default/
upgrading.
The /etc/default/ unbound file, if it exists, will still be read and the unbound
behavior of the package can be modified, but the defaults have been changed
to make it unnecessary for most users to need an /etc/default/
file.
The following variables are still supported by the /etc/default/ unbound
file, if it exists:
[...]
RESOLVCONF
This variable now must be explicitly set to "false" to disable the
unbound package's resolvconf provider. Otherwise, it defaults to
enabled if unset.
In previous versions, this variable had to be explicitly set to "true" unbound file
to enable the resolvconf provider, but the /etc/default/
shipped with it explicitly enabled.
<<
So I suspect you can create and write your own /etc/default/ unbound file with RESOLVCONF=false for the purpose you're looking for.
Due to this looks like a local configuration issue rather than a bug in the software itself, I'm marking this "Invalid" because it doesn't appear to be a bug, but if I'm wrong, please change it back to "New" and add some more info to point me in the right direction. Use this link as a guide: http:// www.chiark. greenend. org.uk/ ~sgtatham/ bugs.html
If you need help configuring, you can get community support in the Ubuntu channels on libera.chat, or in http:// www.ubuntu. com/support/ community