Why isn't Silverblue/Kinoite 35 using systemd-resolved?

Ask Fedora
1

I seem to understand that systemd-resolved has been enable a couple releases ago, but it doesn’t seem to be enabled on my freshly installed Kinoite:

[sph@fedora sph]$ cat /etc/resolv.conf 
# Generated by NetworkManager
search fritz.box
nameserver 192.168.178.1
[sph@fedora sph]$ ll /run/systemd/resolve/stub-resolv.conf 
-rw-r--r--. 1 systemd-resolve systemd-resolve 928 Nov 13 09:50 /run/systemd/resolve/stub-resolv.conf
[sph@fedora sph]$ ll /etc/resolv.conf 
-rw-r--r--. 1 root root 109 Nov 13 09:50 /etc/resolv.conf
2

Don’t you just use resolvectl to view what resolved is doing/does?

3

It’s a bug, [BUG] Silverblue uses systemd-resolved in foreign mode by default instead of stub mode · Issue #192 · fedora-silverblue/issue-tracker · GitHub

4

FYI, this is also an issue if you install from the everything ISO.

As a side note re-installing systemd-resolved resulted in,
Failed to connect to bus: Invalid argument

This may be related to: 2020415 – Error in /usr/lib/systemd/systemd-update-helper: undefined variable "unit"