unbound did not start automatically after reboot

FritzS - gmx fritzs at gmx.net
Wed Sep 9 07:58:22 PDT 2015

> Am 09.09.2015 um 16:29 schrieb Mihai Moldovan <ionic at macports.org>:
> On 08.09.2015 05:03 PM, FritzS - gmx wrote:
>> I use only one volume. My guess the startup of the ethernet port coming to late or the application firewall Little Snitch unblocking the DNS ports to late at startup.
>> My suggestion - unbound should start after network connection is OK and Little Snitch is running up.
> The ethernet device should be available right from the start. I doubt that's a
> problem.
> Deactivate Little Snitch to see whether this works or still fails?

Yes, LittleSnitch blocked unbond shortly in the startup time, so it could not start correctly.

I need a little delay for starting unbound or a requirement entry for a running LittleSnitch in the unbound plist.

Please can you give me some suggestions?

> I've taken a look at unbound last week and didn't see anything obvious that
> would cause startup to fail.

More information about the macports-users mailing list