shell-things/etc/resolv.conf

29 lines
1.0 KiB
Plaintext
Raw Normal View History

2023-12-26 09:51:30 +01:00
# Don't do this, just run this instead:
# sudo ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
2023-12-26 09:51:30 +01:00
# Problem: unbound is slow to start and everything complains of failing DNS,
# and systemd-resolved often gets itself stuck with DNSSEC.
# https://github.com/systemd/systemd/issues/10579 & https://github.com/systemd/systemd/issues/9867
# Solution that I dislike: use both unbound & systemd-resolved! When one
# breaks, maybe the other still works! Funnily /etc/resolv.conf is still
# restricted to three nameservers.
2023-12-26 09:51:30 +01:00
# unbound
nameserver ::1
nameserver 127.0.0.1
2023-12-26 09:51:30 +01:00
# systemd-resolved
nameserver 127.0.0.53
2023-12-26 09:51:30 +01:00
# randomly utilize both, extended DNS, trust DNSSEC from both
options rotate edns0 trust-ad
2023-12-26 09:51:30 +01:00
# no sending local domain to upstream whenever NXDOMAIN happens
search .
# Attempt to mDNS everything?
#search .local
2020-07-23 21:59:53 +02:00
2023-12-26 09:51:30 +01:00
# PS. Remove empty lines and comments if this ends up in /etc/resolv.conf
# PPS. The traditional spell is:
# sudo chattr -i /etc/resolv.conf;sudo nvim /etc/resolv.conf;sudo chattr +i /etc/resolv.conf