From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rymes To: development@lists.ipfire.org Subject: Re: Long delays restarting unbound if Red is down Date: Thu, 13 Dec 2018 11:36:45 -0500 Message-ID: <94190F08-05FC-41C1-B68D-6D8CEE8195DC@rymes.com> In-Reply-To: <33D5B8AF-7366-46FE-9460-DE4219297128@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7734928458660085504==" List-Id: --===============7734928458660085504== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable That=E2=80=99s precisely the problem, Michael. Everything works fine, until s= omething (like an internet outage) prevents you from reaching the DNS servers= . Then, when you reboot the router as part of a troubleshooting process, it t= akes forever while unbound flails about. In this instance, we were replacing a failed router, and someone had misconfi= gured the red interface settings, so we were modifying those settings in setu= p. 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 figur= e out what we were doing wrong. Shouldn=E2=80=99t it have a reasonably short timeout for when the DNS servers= are unavailable? Tom > On Dec 13, 2018, at 11:19 AM, Michael Tremer = wrote: >=20 > Hi Tom, >=20 > the script is usually quite fast when it can reach the DNS servers. >=20 > If it can=E2=80=99t it is waiting quite long and runs into a timeout. >=20 > Is there a reason why it cannot reach the DNS servers? It should be able to= or you should not have functioning DNS. >=20 > -Michael >=20 >> On 12 Dec 2018, at 15:31, Tom Rymes wrote: >>=20 >> Last night we were fighting with a router that had a non-functioning red i= nterface. 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 f= ailed to contact the defined name servers.=20 >>=20 >> Is there a way to make the startup script time out more quickly when thing= s are not functioning? >>=20 >> Tom >=20 --===============7734928458660085504==--