From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [Fwd: Re: request for info: unbound via https / tls]
Date: Mon, 10 Dec 2018 12:30:03 +0100 [thread overview]
Message-ID: <c89c5ec867fee52a4db303d8052655fc12b1bce2.camel@ipfire.org> (raw)
In-Reply-To: <16BD8EAB-1985-486B-B6F4-766C3093EE38@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2453 bytes --]
Hi Michael,
Am Montag, den 10.12.2018, 00:21 +0000 schrieb Michael Tremer:
> I did not understand what the news is here,
the main news for me was that i´ ve build knot (kdig) and a deeper look
into the whole DNS-over-TLS subject and a debugging in general of DoT
is now better possible. The next news was that i wrote a script which
checks the configured DoT servers via kdig for a better overview which
servers are reliable.
Since i do not use Quad9 nor Cloudflair which are currently the only
one to my knowledge that are not outlined as not experimental) -->
https://dnsprivacy.org/wiki/display/DP/DNS+Privacy+Public+Resolvers
public resolvers i wanted to check what´s going on with all the experimental ones -->
https://dnsprivacy.org/wiki/display/DP/DNS+Privacy+Test+Servers#DNSPrivacyTestServers-DoTservers
therefor this step was important for me and i decided to share it here with you.
Have update also the DoT configuration file to now 12 DNS test servers which worked now since
~ 2 weeks without problems. Needed also to throw some others out which causes problems
since some certificate where not trustworthy or DNSSEC validation doesn´t worked.
May you ask yourself why on earth 12 DNS servers ? Well, another testing field for me is
not only encryption in that topic but also randomization -->
https://www.monperrus.net/martin/randomization-encryption-dns-requests -->
https://www.ctrl.blog/entry/kresd-random-dns-forwarding
which unbound offers via 'rrset-roundrobin: yes' as a default value on
IPFire but along my testings i could figure out that it only works with DoT not with
regular DNS, for reference test see here -->
https://forum.ipfire.org/viewtopic.php?f=6&t=21866#p120276
This are currently my main news, but there is more which i wrote in the
forum but also on Gitlab in the README.
> but please try to keep the conversation on the list when it has
> started there. I do not regularly read the forums.
Yes i know and will do this too but as ever i try to invite the
community also via forum to go for testings/sharing_information which,
also as usual, do not works very well.
Best,
Erik
>
> -Michael
>
> > On 9 Dec 2018, at 20:08, ummeegge <ummeegge(a)ipfire.org> wrote:
> >
> > Hi all,
> > some news in this topic can be found in here -->
> > https://forum.ipfire.org/viewtopic.php?f=50&p=120997#p120997
> >
> > Best,
> >
> > Erik
> >
>
>
next prev parent reply other threads:[~2018-12-10 11:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1525184928.3530.13.camel@gmail.com>
2018-05-01 14:33 ` Paul Simmons
2018-05-01 14:40 ` Peter Müller
2018-05-01 17:16 ` Paul Simmons
2018-05-03 16:03 ` Michael Tremer
2018-12-02 19:10 ` ummeegge
2018-12-02 20:23 ` Paul Simmons
2018-12-04 14:01 ` ummeegge
2018-12-04 16:19 ` Peter Müller
2018-12-05 7:35 ` ummeegge
2018-12-09 20:08 ` ummeegge
2018-12-10 0:21 ` Michael Tremer
2018-12-10 11:30 ` ummeegge [this message]
2018-12-10 0:21 ` Michael Tremer
2018-12-10 12:14 ` ummeegge
2018-12-10 12:32 ` ummeegge
2018-12-10 13:26 ` Michael Tremer
2018-12-10 14:37 ` ummeegge
2018-12-11 19:22 ` Michael Tremer
2018-12-11 19:43 ` ummeegge
2018-12-11 19:54 ` Michael Tremer
2018-12-12 13:42 ` ummeegge
2018-12-12 15:25 ` Michael Tremer
2018-12-12 17:44 ` ummeegge
2018-12-13 6:52 ` ummeegge
2018-12-13 16:26 ` Michael Tremer
2018-12-10 13:37 ` Michael Tremer
2018-12-11 2:01 ` Paul Simmons
2018-12-11 20:09 ` ummeegge
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=c89c5ec867fee52a4db303d8052655fc12b1bce2.camel@ipfire.org \
--to=ummeegge@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