DNS resolver not starting
-
Hi all!
I have some problems starting DNS resolver on reboot.
In logs:rc.bootup: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1523547507] unbound[60178:0] error: can't bind socket: Can't assign requested address for 2001:xxxx:xxx:xxx::1 [1523547507] unbound[60178:0] fatal error: could not open ports'
After boot is complete, I can start it just fine manually.
Maybe unbound tries to start itself a little too early?2001:xxxx:xxx:xxx::1 is IP of my LAN iface and it`s static.
Thanks!
-
Anyone?
Tried all suggestions I found here on forums but none of them work.. -
Ive had this in the past when Ive manually configured interfaces in the resolver config that included IPv6-Link Local.. I believe its been fixed but occasionally if the ISP connection gets flaky unbound will not start or will stop for me here. Seems finicky..
I always start though by changing settings until I find the one that is causing it not to start. Right now all seems happy here.
I have "Transparent" and the first 4 boxes selected in the config..
-
For me it starts every time.
Just not after reboot of pfsense.
10 reboots 7 times not started 3 times started… -
Yep- was the same here when I had the ipv6 link included.. Just would not start on reboot. I could hit the start button in services and it would always start up..
Testing meant I had to reboot constantly.
-
I think this could be resolved simply with setting unbound to start a little later…
-
Do you use PPPoE on WAN ?
DNS-Resolver can not handle listening on %pppoe, if select "WAN" on Outgoing Network Interfaces.I use only "localhost" for Outgoing Network Interfaces. Odd, but it works ;)
-
@hda:
Do you use PPPoE on WAN ?
DNS-Resolver can not handle listening on %pppoe, if select "WAN" on Outgoing Network Interfaces.I use only "localhost" for Outgoing Network Interfaces. Odd, but it works ;)
What if an Interface (e.g. OPT) has a specific VPN (e.g. PIA) as the gateway, how do you set the incoming and outgoing Network interfaces in DNS Resolver?
-
I think this could be resolved simply with setting unbound to start a little later…
The term is "race condition". If it's what you think it is, which is also what I was thinking, it's not an issue of making it start arbitrarily later, but it should start after the interface is ready. The kludge of starting later may work in an arbitrary test case, but there will always be another case where the interface still isn't ready and Unbound will start too soon.
But I do agree with you from a practical aspect. I was not being critical of your answer, just making sure you had the vocabulary and clarifying the fundamental issue in case it wasn't completely concrete. Having the correct vocabulary not only helps with communication, but it helps with thinking. The brain actually uses the same structures for words to encode memory and thought. Thoughts are very much limited by our words.
