Package: unbound Version: 1.9.0-2+deb10u2 When starting unbound and binding to a specific interface using the `interface` keyword, unbound can fail if the interface is not configured correctly on boot.
Changing the systemd unit to use the `network-online.target` instead of the `network.target` remedies the situation. Once the interface is online, unbound succeeds in binding to the interface and starts correctly. There is also another bug report (for the Ubuntu package) where another reason for switching to using `network-online.target` is given: https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1923733 That bug report suggests reporting the bug against the Debian package as they use the Debian package unmodified, but I cannot find a corresponding bug report. -- Marcus Furlong
