Could you please explain this with some (possibly a lot) more detail, benefits, configuration, example, …
I found this article, that explains it in general, what I want to know:
Do I need to use DNS-over-TLS, in order to use this, or can I use this with my current configuration?
If you don't care about security and new features, e.g. latest version, you can follow this guide from the pihole developers. You will NOT be able to use the more recent features, since the version in Raspbian (and probably in Debian) distributions aren't the most recent ones (read old...).
The guides I mentioned, opening this topic, assume a compiled version, never tested if they would work on the version included with Raspbian.
Look at the number of bug fixes, made to unbound, since the release of 1.6 (hit toggle older versions). I would assume the latest version is the better choice.
I was the OP on this post that prompted the detailed instructions on compiling from source.
I care about security. Quite a bit. But I also care about convenience. I don't want to have to uninstall/purge and backup/restore my settings each time there is an update.
What does one need to do to encourage an updated Raspian/Debian package for Unbound?
It seems like this community has a large enough critical mass of Unbound users to encourage one.
Change.org petition anyone? I jest. But only slightly.
Of course you have to sudo apt-get update && sudo DEBIAN_FRONTEND=noninteractive apt-get -yq upgrade to keep your OS current, OR implement auto updating, using webmin (see my manual here, chapter 4, section 11), but this will NOT solve the old versions problem.
Raspbian includes a lot of external software, such as unbound, which is great for testing purposes, but if you're going to run these in a "production" environment, you should use compiled software, whenever possible, that is, if you want current releases.
If you don't mind sharing; what would one need to do to (i) preserve their Unbound configuration and (ii) uninstall/purge completely before following the compiling instructions you provided earlier?
I'm afraid I cannot help you there.
Whenever there is a new release of Raspbian, unbound, pihole, knot-resolver, … I setup a new pihole, using another SD card, thus rotating them (3 of them), so I can always fall back on a working SD card, holding the previous working configuration.
In order to do that, I've setup WAMP on one of my windows computers, holding all the configuration files and scripts, needed to make this as easy as possible, transferring them to the new SD card with wget. Currently 31 scripts to execute, total execution time about an hour.
Don't ask, I cannot share the scripts, as they contain passwords and SSH keys, needed to make it all work. You'll have to make your own, but in the end, this will lead to a fast and error free setup, using the latest software.
example of such a script:
#!/bin/bash
# Make sure only root can run our script
if [ "$(id -u)" != "0" ]; then
echo "This script must be run as root" 1>&2
exit 1
fi
# ntp
sudo apt-get -yq install ntp
file=/etc/ntp.conf
#sudo sed -i 's/debian.pool.ntp.org/europe.pool.ntp.org/g' $file
sudo sed -i 's/.*debian.pool.ntp.org/#&/' $file
sudo sed -i '/You do need to talk to an NTP server/aserver 192.168.xxx.yyy' $file
sudo timedatectl set-timezone Europe/Brussels
sudo /etc/init.d/ntp stop
sudo ntpd -gq
sudo /etc/init.d/ntp start
sudo wget http://192.168.xxx.zzz/raspbian/home/pi/ntpcheck.sh -O /home/pi/ntpcheck.sh
sudo chmod +x /home/pi/ntpcheck.sh
sudo wget http://192.168.xxx.zzz/raspbian/etc/cron.d/ntpcheck -O /etc/cron.d/ntpcheck
Debian has their own release schedule and there really is nothing that will change that. The reason people choose Debian is for this policy. When running on a server you want packages that are stable, tested, used, tested, and stable. (Redundancy intended.) But that doesn't mean that packages are completely frozen in place once they release. If a security issue is found then Debian will release updates with fixes picked and ported. See https://metadata.ftp-master.debian.org/changelogs//main/u/unbound/unbound_1.6.0-3+deb9u2_changelog for unbound and notice all the upstream security fixes that are backported.
New features are not typically a reason for a package update once the release has frozen.
I can't seem to get qname minimization to work when compiling 1.9.2. Never tested it with earlier versions though. When running "dig txt qnamemintest.internet.nl" it says it's not working, it works with Knot. Any ideas?
Too bad Unbound seems stalled in Debian, now with Buster being released soon as well.