On 2022-11-15, Courtney <taeki...@gmail.com> wrote: > I had a similar issue going from 7.1 -> 7.2 (though looking back, I > think the issue is > I made my config change and never rebooted until I upgraded to 7.1).
Different issue I think. > However, my issue was not so much unbound waiting for an interface, but > rather I wanted to allow listening on IPv6 and thus added my router's IPv6 > address to be an interface. Since the IP didn't exist (since I had to > wait for > dhcpcd to get the delegation) I had to change my order of operations since > unbound would start before dhcpcd. unbound is an early boot script, so > setting the order with rcctl doesn't work. My solution was to disable > unbound. > > rcctl disable unbound > > Then add it to /etc/rc.local: > > rcctl -f start unbound > > Now unbound starts last when everything else is done. It might be simpler to use interface-automatic and listen on :: and 0.0.0.0 rather than waiting (also more robust as it should still work on v4 in case for some reason you don't get the v6 prefix delegation)
