public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [RFC] unbound: Increase timeout value for unknown dns-server
Date: Mon, 25 Jan 2021 20:50:14 +0000	[thread overview]
Message-ID: <8D509537-653C-402D-8A6D-4318756443F7@ipfire.org> (raw)
In-Reply-To: <12e9159f-727e-b8d1-a8a8-a22715dbad69@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2127 bytes --]

Hi,

> On 25 Jan 2021, at 20:29, Paul Simmons <mbatranch(a)gmail.com> wrote:
> 
> On 1/25/21 1:23 PM, Michael Tremer wrote:
>> 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 <mbatranch(a)gmail.com> wrote:
>>> 
>>> 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:
>>>> 
>>>>>>> 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
>>>> 
>>>> delay-close: 1500
>>>> 
>>>> instead of or in addition to the unknown-server-time-limit.
>>>> 
>>> Howdy!
>>> 
>>> I tried UDP with both mods ('unknown-server-time-limit: 1128' && 'delay-close: 1500').  Unfortunately, I experienced intermittent resolution errors.
>>> 
>>> Am now using TCP...  no apparent errors, but resolution is SssLllOooWww, just as before.
>>> (total.recursion.time.avg=4.433958 total.recursion.time.median=3.65429 total.num.recursivereplies=1515)
>>> 
>>> Thank you for your efforts.  Latency on "HughesNot" is insurmountable, but (barely) beats no connectivity.  I hope to try Starlink, if/when it becomes available for my latitude (30.9 North).
>>> 
>>> Paul
>>> 
>>> -- 
>>> It is hard for an empty bag to stand upright.  -- Benjamin Franklin, 1757
>>> 
> I haven't studied the metrics from unbound, so can't say if the modified timeouts help to avoid retransmissions.
> 
> As of this moment, TCP works, albeit slowly.  If you'd rather drop the patch, I'm okay with that.

Yes, TCP should always work and it will be much faster with Core Update 154 since the connections remain open.

We can always come back to this thread if there is any reason in the future.

> Thanks for all the effort!

Thank you very much for your testing, too!

Best,
-Michael

> Paul

  reply	other threads:[~2021-01-25 20:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20E5B302-A896-4BD2-BAD1-9D6A50831514@ipfire.org>
2021-01-09 15:04 ` Michael Tremer
2021-01-09 18:57   ` Paul Simmons
2021-01-10 14:07     ` Tapani Tarvainen
2021-01-12  5:07       ` Paul Simmons
2021-01-16  3:02         ` Paul Simmons
2021-01-16  8:13           ` Tapani Tarvainen
2021-01-19  6:22             ` Paul Simmons
2021-01-25 19:23               ` Michael Tremer
2021-01-25 20:29                 ` Paul Simmons
2021-01-25 20:50                   ` Michael Tremer [this message]
2021-01-11 11:10     ` Michael Tremer
2021-01-12  4:37       ` Paul Simmons
     [not found] <5BE69EAB-BD90-4999-97AE-8A89479AD080@gmail.com>
2021-01-07 11:27 ` Michael Tremer
2021-01-07 14:35   ` Tapani Tarvainen
2021-01-07 14:54     ` Michael Tremer
2021-01-06 10:17 Jonatan Schlag
2021-01-06 12:02 ` Paul Simmons
2021-01-06 15:14   ` Michael Tremer
2021-01-06 16:19     ` Tapani Tarvainen
2021-01-06 18:01       ` Michael Tremer
2021-01-08  8:25     ` Paul Simmons

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8D509537-653C-402D-8A6D-4318756443F7@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox