Unbound and Redis

[Dynamic5912]

Does Unbound install via DietPi with the requirements/dependencies for utilising Redis?

I understand that Unbound has to be installed with cachedb and some other dependencies to work with Redis.

Thanks!

[Joulinar]

We install the default Debian package, which doesn't support Redis.

[Dynamic5912]

How can I manually (or otherwise) upgrade Unbound to the latest release?

And would upgrading also add the additional components?

I note that Unbound provides info on downloading and compiling your own installer for the latest release - but I'm not savvy/comfortable enough to do that myself..

[Joulinar]

How can I manually (or otherwise) upgrade Unbound to the latest release?

I guess that would mean switching from Debian Bookworm to the bleeding-edge Debian Trixi.

[MichaIng]

You would need to compile it yourself from source then. These instructions for Ubuntu should work on Debian as well: https://unbound.docs.nlnetlabs.nl/en/latest/getting-started/installation.html#id1

An alternative would be to upgrade the whole distribution to Debian Trixie. But it is still very volatile, might go through further larger package transitions, which by times means to manually resolve conflicts, remove obsolete packages and install their newer counter parts (like removing PHP 8.2 once PHP 8.3 is available in the repo and such). Security-wise and regarding bugs, Debian Trixie/testing is actually quite stable, comparable to any other rolling-release distribution or the non-LTS Ubuntu versions, but amount and kind of package upgrades requires more attention (also like on rolling-release distros like Arch Linux), hence some experience or mood to tinker 😉.

[Dynamic5912]

Thanks I'll give that a try.

Do you know if installing/updating Unbound in-situ over an existing installation will change any existing configurations or override .conf files?

[MichaIng]

The configuration files should remain. Ours is anyway installed to /etc/unbound/unbound.conf.d/dietpi.conf, hence no pach where any default config could be installed to. The only thing I am not entirely sure about is whether the sudo make install step installs a new systemd unit over the existing one, respectively to /etc/systemd/system/unbound.service to use the new binary or not. The DEB package installation remains mostly untouched with e.g. /usr/bin/unbound while make install installs it to /usr/local/bin/unbound, where it takes priority. But the systemd service defines the absolute executable path.

You can check whether /usr/local/bin/unbound is used via e.g.

systemctl cat unbound

after compiling+install has finished.