Unbound fatal error: could not open ports, then unbound is down.
-
Hi,
I found this in the system log, Unbound fatal error: could not open ports, then unbound stopped working. Only occurred under the combination of IPv6 and pfBlockerNG DNSBL. What was happened:
when the IP changes, it tries to stop/start Unbound… But unbound takes a little more time to do that with DNSBL enabled... So it fails to start ....
I was told that its not a package issue, but something in pfSense code.
-
This is crazy now. It happened at every day exactly same time, and each time I have to re-start the unbound service manually, otherwise no internet.
The workaround was either disable IPv6 or disable DNSBL, which isn't good at all.
-
I can also report the same problem, unbound doesn't restart correctly after the IPv6 renew happens. I've been using Watchdog to keep it running but there is still a small cap between the restart which wreaks havoc on some of my scripts using the network.
-
I can also report the same problem, unbound doesn't restart correctly after the IPv6 renew happens. I've been using Watchdog to keep it running but there is still a small cap between the restart which wreaks havoc on some of my scripts using the network.
Did you have a solution for this?
-
Hi,
I found this in the system log, Unbound fatal error: could not open ports, then unbound stopped working. Only occurred under the combination of IPv6 and pfBlockerNG DNSBL. What was happened:
when the IP changes, it tries to stop/start Unbound… But unbound takes a little more time to do that with DNSBL enabled... So it fails to start ....
I was told that its not a package issue, but something in pfSense code.
I experienced a similar issue last night with my HE.NET IPv6 Tunnel. I am running on the latest dev (2.3.2-DEVELOPMENT (amd64) built on Mon Jul 18 23:27:23 CDT 2016 FreeBSD 10.3-RELEASE-p5)
