From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Long delays restarting unbound if Red is down Date: Thu, 13 Dec 2018 16:18:53 +0000 Message-ID: <33D5B8AF-7366-46FE-9460-DE4219297128@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8395585130274629724==" List-Id: --===============8395585130274629724== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Tom, the script is usually quite fast when it can reach the DNS servers. If it can=E2=80=99t 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 o= r you should not have functioning DNS. -Michael > 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 in= terface. 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 fa= iled to contact the defined name servers.=20 >=20 > Is there a way to make the startup script time out more quickly when things= are not functioning? >=20 > Tom --===============8395585130274629724==--