Unbound won't start on system boot

[Colin Watson]

On Thu, Jun 12, 2025 at 12:15:03PM -0400, Robert Moskowitz via ubuntu-users wrote:
>On 6/12/25 12:09 PM, Colin Watson wrote:
>>Quite!  If you need to force it to only start after some other unit 
>>has come up, a much more sensible approach would be to use 
>>"systemctl edit unbound.service" to create a drop-in unit (basically 
>>a local override) that adds an After= directive to the [Unit] 
>>section.  Or whatever else of that kind that you need.
>
>Oh, yes.  But I haven't done that for years!  When we were fighting 
>with chrony on systems without a rtc, and you had to tell chrony to 
>wait until the network was up.  Well that is kind of like what is 
>happening here.
>
>So please point me to what I need to add to the service?
>
>After what?

I don't know what network interface you might need to wait for, or even 
if the suggestion you found about it needing a particular network 
interface to be up was correct, so it's hard to give a specific answer.  
I was hoping that my suggestion above might help you work it out for 
yourself using "man systemd.unit" and such.

"man systemd.special" might also help, since there are some special 
targets you can use to wait for things in a more coarse-grained way.

-- 
Colin Watson (he/him)                              [cjwatson at ubuntu.com]