From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: DNS over TLS performance and query randomisation across multiple forwarders
Date: Wed, 19 Feb 2020 21:17:00 +0000 [thread overview]
Message-ID: <a647c20e-dffb-8a0c-c994-fd6225ae5dfe@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 803 bytes --]
Hello *,
while DNS over TLS is operational in upcoming Core Update 140/141, we
already discovered some performance issues due to missing TLS connection
reuse and similar optimisations.
Further, Unbound performs some measurements to determine response times
of given forwarders and submits all queries to the fastest one - which
obviously is a bad thing with a view to DNS privacy.
Stubby (https://dnsprivacy.org/wiki/display/DP/About+Stubby), which is
also written by NLnet Labs, aims to fix both issues.
Personally, I do not like the idea of putting another software before
Unbound in case the user decides to enable DNS over TLS. However, to discuss
this matter and further steps, mentioning it did sound reasonable to me. :-)
Thoughts/comments/opinions?
Thanks, and best regards,
Peter Müller
next reply other threads:[~2020-02-19 21:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 21:17 Peter Müller [this message]
2020-02-20 14:37 ` Michael Tremer
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=a647c20e-dffb-8a0c-c994-fd6225ae5dfe@ipfire.org \
--to=peter.mueller@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