That’s precisely the problem, Michael. Everything works fine, until something (like an internet outage) prevents you from reaching the DNS servers. Then, when you reboot the router as part of a troubleshooting process, it takes forever while unbound flails about.
In this instance, we were replacing a failed router, and someone had misconfigured the red interface settings, so we were modifying those settings in setup. It took us a while to figure out what we were doing wrong, so we ended up having to wait over and over again as unbound tried to restart and failed. We were the problem, but unbound made it a real hassle while we worked to figure out what we were doing wrong.
Shouldn’t it have a reasonably short timeout for when the DNS servers are unavailable?
Tom
On Dec 13, 2018, at 11:19 AM, Michael Tremer michael.tremer@ipfire.org wrote:
Hi Tom,
the script is usually quite fast when it can reach the DNS servers.
If it can’t it is waiting quite long and runs into a timeout.
Is there a reason why it cannot reach the DNS servers? It should be able to or you should not have functioning DNS.
-Michael
On 12 Dec 2018, at 15:31, Tom Rymes trymes@rymes.com wrote:
Last night we were fighting with a router that had a non-functioning red interface. It ended up being a misconfiguration on our part, but while we were troubleshooting, we routinely had to wait for very long periods as unbound failed to contact the defined name servers.
Is there a way to make the startup script time out more quickly when things are not functioning?
Tom