Package: unbound
Version: 1.13.1-1

After upgrading to bullseye from buster (unbound v1.9.0-2+deb10u2), unbound fails to start via systemd, but starts and runs fine when daemon is started directly.

There is an upstream fix (to unbound, not systemd) for this issue:

https://github.com/NLnetLabs/unbound/pull/351

The original bug report from arch package maintainer:

https://github.com/NLnetLabs/unbound/issues/350


Can we get this fix applied to unbound in bullseye?


Under systemd, the error is:

Oct 14 10:56:35 systemd[1]: Starting Unbound DNS server...

Oct 14 10:56:36 unbound[93822]: [1634234196] unbound[93822:0] error: failed to list interfaces: getifaddrs: Address family not supported by protocol

Oct 14 10:56:36 unbound[93822]: [1634234196] unbound[93822:0] fatal error: could not open ports

Oct 14 10:56:36 systemd[1]: unbound.service: Main process exited, code=exited, status=1/FAILURE

  • Bug#996494: unbound in bullseye fails to start under systemd -... Grant Chesy

Reply via email to