From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [Fwd: Re: request for info: unbound via https / tls]
Date: Tue, 11 Dec 2018 21:09:39 +0100 [thread overview]
Message-ID: <5eeac2fe88cc4a956a4ef0ca680e2c08f2a222d6.camel@ipfire.org> (raw)
In-Reply-To: <dc899921b0fcb812bb8a215eb7c71d073fb904a2.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2274 bytes --]
Hi Paul,
Am Montag, den 10.12.2018, 20:01 -0600 schrieb Paul Simmons:
>
> Greetings, Erik.
>
> I am VERY pleased that you are pursuing DoT.
>
Your welcome, like that feature too.
> I have a test environment prepared, and hope to test your changes on
> top of Core125 in the next few days.
>
Great. There are meanwhile two branches here.
The first one is the sysconfig "USE_FORWARDER=0" one which is fully
working and in my opinion also easier/faster to test DoT/unbound for,
let´s say, best practice configuration. Current state can be found
under the already linked Gitlab address.
The second one incl. now the WUI (have stolen/missused dnsforward.cgi
for this ;) but also DoT integration in the already existing
/etc/unbound/forward.conf . In there, i patched now the already
existing 'write_forward_conf' function like Michael suggested -->
@@ -192,6 +195,27 @@
(
config_header
+ # Add DNS-over-TLS forwarder configuration
+
+ if [ -n "/var/ipfire/dnsforward/tlsconfig" ]; then
+ echo "# DNS-over-TLS configuration block"
+ echo "server:"
+ echo " tls-cert-bundle: /etc/ssl/certs/ca-bundle.crt"
+ echo
+ echo "forward-zone:"
+ echo " name: \".\""
+ echo " forward-tls-upstream: yes"
+ fi
+
+ local enabled domain ip port remark
+ while IFS="," read -r enabled domain ip port remark; do
+ # Line must be enabled
+ [ "${enabled}" = "on" ] || continue
+ echo " forward-addr: ${ip}@${port}#${domain}"
+ done < /var/ipfire/dnsforward/tlsconfig
+
+ # DNS Forwarding
+
local insecure_zones="${INSECURE_ZONES}"
local enabled zone server remark
as a first one, this one is currently highly experimental but do works
until now and might be a possible way further.?.
> I started this thread because my (one and only available) ISP mangles
> DNS on port 53, preventing DNSSEC with IPFire. I want to use my
> IPFire
> machine without applying https://gitlab.com/snippets/1706804 on each
> update.
>
Please check in general if DoT works for your use case.
> Please continue with your pursuits and development. I will schedule
> down time to test.
>
Let´s see what we can all stick together in here :-) . Great that you
test all that too.
> Thanks, and best regards,
> Paul
>
Thank you too.
Best,
Erik
prev parent reply other threads:[~2018-12-11 20:09 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
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 [this message]
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=5eeac2fe88cc4a956a4ef0ca680e2c08f2a222d6.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