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 13:32:04 +0100 [thread overview]
Message-ID: <a79ff914e3244e5a5425e0083e9ecfbe44c285fe.camel@ipfire.org> (raw)
In-Reply-To: <d69e046565e67ec198962be291cf4577484cd401.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 601 bytes --]
A question,
what happens with DoT on Lightningwirelabs -->
https://www.lightningwirelabs.com/2018/05/03/dns-over-tls-now-available-on-our-resolvers ?
I get there an
$ kdig -d @81.3.27.54 +tls-ca=/etc/ssl/certs/ca-bundle.crt +tls-host="ns1.lightningwirelabs.com" google.com;
;; DEBUG: Querying for owner(google.com.), class(1), type(1), server(81.3.27.54), port(853), protocol(TCP)
;; DEBUG: TLS, imported 128 certificates from '/etc/ssl/certs/ca-bundle.crt'
;; WARNING: can't connect to 81.3.27.54(a)853(TCP)
;; WARNING: failed to query server 81.3.27.54(a)853(TCP)
.
Best,
Erik
next prev parent reply other threads:[~2018-12-10 12:32 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
2018-12-10 0:21 ` Michael Tremer
2018-12-10 12:14 ` ummeegge
2018-12-10 12:32 ` ummeegge [this message]
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=a79ff914e3244e5a5425e0083e9ecfbe44c285fe.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