mirror of
https://gitea.blesmrt.net/mikaela/shell-things.git
synced 2025-06-15 19:47:20 +02:00
systemd-resolved additional config files
Quickstart
This is also done by
../../systemd-resolv.conf-restore.bash
which takes into
account more circumstances…
sudo systemctl enable --now systemd-resolved.service
sudo ln -rsf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
# After changing configuration
sudo systemctl restart systemd-resolved
…but ../../systemd-resolv.conf-generate.bash
is
better. Although ../../resolv.conf-generate.bash
is the best this repository has to offer.
General commentary
- DNSOverTLS became supported in systemd v239, strict mode (true) in
v243 (big improvements in v244).
- TODO: find out when SNI became supported, I have just spotted it in the fine manual in 2020-06-??.
- Domains has to be
.~
for them to override DHCP. See https://www.internetsociety.org/blog/2018/12/dns-privacy-in-linux-systemd without which I wouldn’t have got this right. - DNSSEC may not work if the system is down for a long time and not
updated. Thus
allow-downgrade
may be better for non-tech people, even with the potential downgrade attack. There are also captive portals, affectingDNSOverTLS
. Both taketrue
orfalse
or their own special option, for DNSSEC theallow-downgrade
, for DNSOverTLSopportunistic
.- Then again when was any system that outdated to not have working
DNSSEC?
- TODO: return to this configuration should that actually happen?
- I am actually running Unbound simultaneously with
resolv.conf
pointing to both withoptions rotate edns0 trust-ad
which might workaround that potential issue.
- Then again when was any system that outdated to not have working
DNSSEC?
- DNS server priority is the one they are specified in. The first working one will be used when it won’t work anymore and then the next is used as long as it works and then it’s back to the beginning.
Other links I have found important and my files are based on:
- https://wiki.archlinux.org/index.php/Systemd-resolved
- Also provides the serious issues systemd-resolved+DNSSEC issues, https://github.com/systemd/systemd/issues/10579 & https://github.com/systemd/systemd/issues/9867
- request for strict DoT: https://github.com/systemd/systemd/issues/10755
- vulnerable to MITM: https://github.com/systemd/systemd/issues/9397