From: Paul Simmons <mbatranch@gmail.com>
To: development@lists.ipfire.org
Subject: request for info: unbound via https / tls
Date: Wed, 04 Apr 2018 12:38:30 -0500 [thread overview]
Message-ID: <1522863510.21126.19.camel@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
For Core119, I'm currently using a patch to /etc/init.d/unbound:
https://gitlab.com/snippets/1706804
because my (only available) ISP mangles port 53 traffic, effectively
disabling DNS outside of my private firewall.
I wonder if configuring unbound so that forward requests use DNSSEC
over HTTPS or TLS would be a better (and more secure) solution? Also
see:
https://forum.ipfire.org/viewtopic.php?f=27&t=20575#p115342
https://forum.ipfire.org/viewtopic.php?f=50&t=20574
Comments and test configurations are welcome!
Paul
next reply other threads:[~2018-04-04 17:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 17:38 Paul Simmons [this message]
2018-04-05 9:43 ` Michael Tremer
2018-04-05 13:28 ` Paul Simmons
2018-04-05 14:31 ` 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=1522863510.21126.19.camel@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