Hi guys,

Is anyone else aware of the Unbound and PF race condition that exists when 
FQDNs are used in pf.conf with a local Unbound server?

The issue occurs when pf starts before unbound, but where pf fails to start as 
it cannot resolve some DNS names.. and so unbound also fails to work when it is 
started later in the boot because pf failed to start..

The only solution I’ve found so far is to add some commands to /etc/rc.local 
(run end of boot) to temporarily disable (the failed) pf, restart unbound, and 
restart pf again now unbound is working.

Just wondering if anyone knows of a cleaner workaround? PS; Using an external 
DNS server in resolv.conf is not an option in this scenario.

Cheers, Andy.



Sent from a teeny tiny keyboard, so please excuse typos

Reply via email to