Robert Heller <[email protected]> wrote: > At Thu, 05 Mar 2026 17:24:07 +0100 Jan Claeys <[email protected]> wrote: > > > > > On Wed, 2026-03-04 at 22:43 -0500, Robert Heller wrote: > > > If systemd-resolved is installed and running, you completely lose > > > control of /etc/resolv.conf -- editing /etc/resolv.conf is not > > > effectual at all. > > > > That's not (entirely) true, systemd-resolved can work with resolv.conf > > as explained in the systemd-resolved.service(8) manpage under the > > '/ETC/RESOLV.CONF' header. > > > > Yes, there is another file that is used by systemd-resolved. systemd-resolved > launches a "DNS" handler (a simple caching server, like DNS Masq or something > like that), which will forward to either what network manager picks up via > DHCP, and handles DNS for VMs and mDNS, and yes there is some file under > someplace where other DNS servers can be listed. All very clever, but if you > are running your own DNS server(s) (ie running full bind9), it is easier and > simplier to just stop and disable systemd-resolved and manually manage > /etc/resolv.conf. Oh, network manager will mess with /etc/resolv.conf when > systemd-resolved is absent. There might be config somewhere for network > manager to deal with that. (On machines where I am running bind9, I set up > the Ethernet with a static IP in /etc/network/interfaces, which keeps network > manager at bay. > My approach, when I want to manage local DNS etc. is to disable systemd-resolved completely and use dnsmasq instead.
-- Chris Green ยท
