On 5/24/2024 10:49 AM, Robert Heller wrote:
Normally, with systemd-resolved running /etc/resolv.conf is NOT an editable file, but a symlink to a file under systemd-resolved control, and usually systemd-resolved is running its own caching only name server (dmasq?) that is caching 8.8.8.8 -- eg none of the local network machines are DNS resolved (which is fine on an ad-hoc LAN). At least that is what happens by default under Ubuntu. I found it easier to just stop and disable systemd-resolved and then manually edit /etc/resolv.conf to reference the local Bind9 name server when I set up a LAN with a local Bind9 name server.
Whether it's managed or not, CUPS is going to consult it when it uses the resolver APIs in glibc. So you should be able to cat it to see what the resolver APIs will use.
I haven't yet used systemd-resolved so I haven't studied its config in detail. It looks like the config is in /etc/systemd/resolved.conf*:
https://wiki.archlinux.org/title/systemd-resolved
[Sorry about the typo on /etc/resolv.conf. Thunderbird insisted on spellchecking and I didn't notice it.]