WIP: Add DNS over TLS support #7343
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add DNS over TLS support using Unbound as a local resolver. This includes new options on both server and client side. * `--dns-over-tls`: enable DNS over TLS support. This option is present on both client and server. It deploys Unbound and configures BIND on the server to receive DoT requests. * `--dot-forwarder`: the upstream DNS server with DoT support. It must be specified in the format `1.2.3.4#dns.server.test` * `--dns-over-tls-key` and `--dns-over-tls-cert`: in case user prefers to have the DoT certificate in BIND generated by themselves. If these are empty, IPA CA is used instead to request a new certificate.
Add design page for Encrypted DNS traffic support. Fixes: TBD Signed-off-by: Francisco Trivino <[email protected]>
f-trivino
reviewed
May 23, 2024
| @@ -0,0 +1,7 @@ | |||
| server: | |||
| tls-cert-bundle: $TLS_CERT_BUNDLE_PATH | |||
| interface: 127.0.0.55 | |||
There was a problem hiding this comment.
perhaps we could use 127.0.0.53 as the port is 53?
There was a problem hiding this comment.
127.0.0.53 is used already by systemd-resolved.
• Additionally, systemd-resolved provides a local DNS stub listener on the IP addresses 127.0.0.53 and 127.0.0.54 on the local loopback interface. Programs issuing DNS requests directly, bypassing any local API may
be directed to this stub, in order to connect them to systemd-resolved. Note however that it is strongly recommended that local programs use the glibc NSS or bus APIs instead (as described above), as various
network resolution concepts (such as link-local addressing, or LLMNR Unicode domains) cannot be mapped to the unicast DNS protocol.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add DNS over TLS support using Unbound as a local resolver. This includes new options on both server and client side.
--dns-over-tls: enable DNS over TLS support. This option is present on both client and server. It deploys Unbound and configures BIND on the server to receive DoT requests.--dot-forwarder: the upstream DNS server with DoT support. It must be specified in the format1.2.3.4#dns.server.test--dns-over-tls-keyand--dns-over-tls-cert: in case user prefers to have the DoT certificate in BIND generated by themselves. If these are empty, IPA CA is used instead to request a new certificate.