From: Paul Simmons <mbatranch@gmail.com>
To: development@lists.ipfire.org
Subject: Re: [RFC] unbound: Increase timeout value for unknown dns-server
Date: Wed, 06 Jan 2021 06:02:41 -0600 [thread overview]
Message-ID: <29ea1ac3-a966-23d6-62b1-a6ebdc216716@gmail.com> (raw)
In-Reply-To: <20210106101742.6561-1-jonatan.schlag@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1398 bytes --]
On 1/6/21 4:17 AM, Jonatan Schlag wrote:
> When unbound has no information about a DNS-server
> a timeout of 376 msec is assumed. This works well in a lot of situations,
> but they mention in their documentation that this could be way too low.
> They recommend a timeout of 1126 msec for satellite connections
> (https://nlnetlabs.nl/documentation/unbound/unbound.conf).
> Settings this value to 1126 msec should make the first queries to an
> unknown server, more useful.
> They do not timeout and so these queries do not need to be sent again.
>
> On a stable link, this behaviour should not have negative implications.
> As the first result of queries arrive the timeout value gets updated,
> and the high value of 1126 msec gets set to something useful.
>
> Signed-off-by: Jonatan Schlag <jonatan.schlag(a)ipfire.org>
> ---
> config/unbound/unbound.conf | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/config/unbound/unbound.conf b/config/unbound/unbound.conf
> index f78aaae8c..02f093015 100644
> --- a/config/unbound/unbound.conf
> +++ b/config/unbound/unbound.conf
> @@ -62,6 +62,7 @@ server:
>
> # Timeout behaviour
> infra-keep-probing: yes
> + unknown-server-time-limit: 1128
>
> # Bootstrap root servers
> root-hints: "/etc/unbound/root.hints"
This sounds promising to me, as I have many DNS lookup timeouts (ISP is
HughesNot, er, HughesNet).
+1
Paul
next prev parent reply other threads:[~2021-01-06 12:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 10:17 Jonatan Schlag
2021-01-06 12:02 ` Paul Simmons [this message]
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
[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
[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
2021-01-11 11:10 ` Michael Tremer
2021-01-12 4:37 ` 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=29ea1ac3-a966-23d6-62b1-a6ebdc216716@gmail.com \
--to=mbatranch@gmail.com \
--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