Le 05/03/2026 à 03:47, Vahid Shaik a écrit :
Hi all,
Hello,
Please take into consideration that I am far from competent for anything
network related.
[...]
1. Setting DNS= and FallbackDNS= in /etc/systemd/resolved.conf — works
temporarily but reverts after reboot on one of my machines
ArchLinux Wiki advise to create a
/etc/systemd/resolved.conf.d/dns_servers.conf file to indicate custom DNSes:
https://wiki.archlinux.org/title/Systemd-resolved#Manually
2. Symlinking /etc/resolv.conf to /run/systemd/resolve/resolv.conf —
gives me the "upstream" servers but breaks .local resolution
From what I understand (wrongly?), that the other way around:
"[...]systemd-resolved maintains the /run/systemd/resolve/resolv.conf
file for compatibility with traditional Linux programs. This file may be
symlinked from /etc/resolv.conf and is always kept up-to-date,
containing information about all known DNS servers.[...]"
https://www.freedesktop.org/software/systemd/man/latest/systemd-resolved.service.html#/etc/resolv.conf
3. Disabling systemd-resolved entirely — works but feels like fighting
the system
Why? I don't know why but there seem to be a general misconception that
systemd-resolved is the default for headless machines in the Debian
ecosystem.
Paragraph 5.2.4 of Bookworm Release Notes states: "[...]Note that
systemd-resolved was not, and still is not, the default DNS resolver in
Debian[...]"
https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html#systemd-resolved
