shell-things/etc/resolv.conf

35 lines
1.5 KiB
Plaintext
Raw Normal View History

# notes on resolv.conf, actual DNS resolvers in resolv.csv (not a system
# config file)
# Local resolver (Unbound?)
#nameserver 127.0.0.1
2019-05-16 14:28:15 +02:00
#nameserver ::1
# dnscrypt-proxy directly (Debian/systemd)
#nameserver 127.0.2.1
2020-07-20 22:11:55 +02:00
# trust-ad option is required from glibc2.31+ to tell everything to trust
# AD/DNSSEC in case there is a localhost DNS server that validates it
options edns0 single-request-reopen #trust-ad
2019-05-16 14:28:15 +02:00
# I am not entirely sure local is valid to use here. And this has a bad
# habit of flooding nameserver with names I don't want it to know about
# and in some cases there are _fun_ A/AAA responses to nonexistant domains.
# !!! The systemd-resolved file to avoid search domains is
# /usr/lib/systemd/resolv.conf
2019-05-16 14:28:15 +02:00
#search mikaela.internal local mikaela.info
# note and remember missing DNSSEC
# use.opendns.com http://208.69.38.205/
# system.opendns.com http://208.69.38.170/
# systemd-resolved symlink files:
# !!! /run/systemd/resolve/stub-resolv.conf !!! /usr/lib/systemd/resolv.conf /run/systemd/resolve/resolv.conf
2020-07-23 21:59:53 +02:00
# !!! /run/systemd/resolve/stub-resolv.conf !!! contains search domains and doesn't seem to be
# overwritable and somehow works with Mullvad
# https://github.com/mullvad/mullvadvpn-app/issues/1952
2020-07-23 22:27:37 +02:00
# /usr/lib/systemd/resolv.conf doesn't contain search domains, can
# get overwritten and "broken"
# /run/systemd/resolve/resolv.conf contains uplink resolvers and domains
# SHOULDN'T BE USED!