Unbound service failed on boot in CentOS
mehmed.kahric at vlatacom.com
Fri May 27 07:33:43 UTC 2016
No, because interface with address 192.168.1.7 bring up couple seconds
after Unbound service start. In the moment of starting Unbound service
interface with this address is not up yet.
On Thu, May 26, 2016 19:17, Sonic wrote:
> On Thu, May 26, 2016 at 12:21 PM, Mehmed Kahric via Unbound-users
> <unbound-users at unbound.net> wrote:
>> If I set interface to 0.0.0.0 service start fine.
> Maybe something else already bound to port 53 (NSD, Bind, etc.) on
> interface 192.168.1.7 (assuming you have that interface address)?
More information about the Unbound-users