Unbound won't start on system boot

[Robert Moskowitz]

On 6/12/25 12:09 PM, Colin Watson wrote:
> On Thu, Jun 12, 2025 at 11:00:44AM -0400, Robert Moskowitz via 
> ubuntu-users wrote:
>> I am still fighting with local resolution.  That is a separate 
>> question.  But
>>
>> On reboot, unbound fails to start, but restarts just fine later. One 
>> google dig found:
>>
>> "The problem seems to relate to "nss-lookup", and I suspect that the 
>> network interface is not available fast enough"
>>
>> So put in your /etc/crontab
>>
>> @reboot     /bin/systemctl restart unbound
>>
>> !!!  that seems rather heavy-handed!
>
> 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?