From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: [RFC] unbound: Increase timeout value for unknown dns-server Date: Mon, 25 Jan 2021 19:23:25 +0000 Message-ID: <01083479-A167-47E6-8B06-7E7BD3F3D3C6@ipfire.org> In-Reply-To: <1f0960e2-cddf-e0e8-bbfa-94eeebe5c69f@gmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8855072201085008330==" List-Id: --===============8855072201085008330== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello everyone, So what does that leave us with? Should we drop the patch because it does not change anything and the correct = solution would be using TCP as underlying protocol? -Michael > On 19 Jan 2021, at 06:22, Paul Simmons wrote: >=20 > On 1/16/21 2:13 AM, Tapani Tarvainen wrote: >> On Fri, Jan 15, 2021 at 09:02:08PM -0600, Paul Simmons (mbatranch(a)gmail.= com) wrote: >>=20 >>>>> echo 'unknown-server-time-limit: 1128' >/etc/unbound/local.d/timeouts >>> I've found that UDP doesn't work at all. TCP with "timeout" mod never >>> fails. >> You might also try if UDP works with >>=20 >> delay-close: 1500 >>=20 >> instead of or in addition to the unknown-server-time-limit. >>=20 > Howdy! >=20 > I tried UDP with both mods ('unknown-server-time-limit: 1128' && 'delay-clo= se: 1500'). Unfortunately, I experienced intermittent resolution errors. >=20 > Am now using TCP... no apparent errors, but resolution is SssLllOooWww, ju= st as before. > (total.recursion.time.avg=3D4.433958 total.recursion.time.median=3D3.65429 = total.num.recursivereplies=3D1515) >=20 > Thank you for your efforts. Latency on "HughesNot" is insurmountable, but = (barely) beats no connectivity. I hope to try Starlink, if/when it becomes a= vailable for my latitude (30.9 North). >=20 > Paul >=20 > --=20 > It is hard for an empty bag to stand upright. -- Benjamin Franklin, 1757 >=20 --===============8855072201085008330==--