Hello, unbound actually fails to startup on both bookwork and trixie, when installing without recommends:
This is on a fresh bookworm install after a "apt-get install unbound": Oct 21 08:26:44 debian-4gb-hel1-1 systemd[1]: Starting unbound.service - Unbound DNS server... Oct 21 08:26:44 debian-4gb-hel1-1 unbound[1032]: [1032:0] notice: init module 0: subnetcache Oct 21 08:26:44 debian-4gb-hel1-1 unbound[1032]: [1032:0] notice: init module 1: validator Oct 21 08:26:44 debian-4gb-hel1-1 unbound[1032]: [1032:0] error: unable to open /var/lib/unbound/root.key for reading: No such file or directory Oct 21 08:26:44 debian-4gb-hel1-1 unbound[1032]: [1032:0] error: error reading auto-trust-anchor-file: /var/lib/unbound/root.key Oct 21 08:26:44 debian-4gb-hel1-1 unbound[1032]: [1032:0] error: validator: error in trustanchors config Oct 21 08:26:44 debian-4gb-hel1-1 unbound[1032]: [1032:0] error: validator: could not apply configuration settings. Oct 21 08:26:44 debian-4gb-hel1-1 unbound[1032]: [1032:0] error: module init for module validator failed Oct 21 08:26:44 debian-4gb-hel1-1 unbound[1032]: [1032:0] fatal error: failed to setup modules Oct 21 08:26:44 debian-4gb-hel1-1 systemd[1]: unbound.service: Main process exited, code=exited, status=1/FAILURE Oct 21 08:26:44 debian-4gb-hel1-1 systemd[1]: unbound.service: Failed with result 'exit-code'. Oct 21 08:26:44 debian-4gb-hel1-1 systemd[1]: Failed to start unbound.service - Unbound DNS server. Oct 21 08:26:44 debian-4gb-hel1-1 systemd[1]: unbound.service: Scheduled restart job, restart counter is at 5. Oct 21 08:26:44 debian-4gb-hel1-1 systemd[1]: Stopped unbound.service - Unbound DNS server. Oct 21 08:26:44 debian-4gb-hel1-1 systemd[1]: unbound.service: Start request repeated too quickly. Oct 21 08:26:44 debian-4gb-hel1-1 systemd[1]: unbound.service: Failed with result 'exit-code'. Oct 21 08:26:44 debian-4gb-hel1-1 systemd[1]: Failed to start unbound.service - Unbound DNS server. This is on a fresh trixie install after a "apt-get install unbound": Oct 21 08:41:38 debian-4gb-hel1-1 systemd[1]: Starting unbound.service - Unbound DNS server... Oct 21 08:41:38 debian-4gb-hel1-1 unbound[1405]: [1405:0] notice: init module 0: validator Oct 21 08:41:38 debian-4gb-hel1-1 unbound[1405]: [1405:0] error: unable to open /var/lib/unbound/root.key for reading: No such file or directory Oct 21 08:41:38 debian-4gb-hel1-1 unbound[1405]: [1405:0] error: error reading auto-trust-anchor-file: /var/lib/unbound/root.key Oct 21 08:41:38 debian-4gb-hel1-1 unbound[1405]: [1405:0] error: validator: error in trustanchors config Oct 21 08:41:38 debian-4gb-hel1-1 unbound[1405]: [1405:0] error: validator: could not apply configuration settings. Oct 21 08:41:38 debian-4gb-hel1-1 unbound[1405]: [1405:0] error: module init for module validator failed Oct 21 08:41:38 debian-4gb-hel1-1 unbound[1405]: [1405:0] fatal error: failed to init modules Oct 21 08:41:38 debian-4gb-hel1-1 systemd[1]: unbound.service: Main process exited, code=exited, status=1/FAILURE Oct 21 08:41:39 debian-4gb-hel1-1 systemd[1]: unbound.service: Failed with result 'exit-code'. Oct 21 08:41:39 debian-4gb-hel1-1 systemd[1]: Failed to start unbound.service - Unbound DNS server. Oct 21 08:41:39 debian-4gb-hel1-1 systemd[1]: unbound.service: Scheduled restart job, restart counter is at 5. Oct 21 08:41:39 debian-4gb-hel1-1 systemd[1]: unbound.service: Start request repeated too quickly. Oct 21 08:41:39 debian-4gb-hel1-1 systemd[1]: unbound.service: Failed with result 'exit-code'. Oct 21 08:41:39 debian-4gb-hel1-1 systemd[1]: Failed to start unbound.service - Unbound DNS server. So for this reason alone I think dns-root-data should be a strong dependency. I do agree that when dns-root-data data is only *copied* *during install*,it is less useful for future updates. It would need symbolic links and maybe restart triggers instead. I don't know what the best way to achieve this is. Regards, Lukas
