Am 22.02.2021 um 12:14 schrieb Łukasz Posadowski mail@lukaszposadowski.pl:
If not, I would guess that systemd-resolved is starting up before network interfaces. Is systemd-resolved unit configured with "Wants=*", or "Require=*"?
Indeed: L. Poettering wrote „… Moreover the interface names are resolved the moment resolved parses the configuration file, i.e. likely before the network iface actually showed up, thus be parsing will fail in the typical case.
So far we have no mechanism to declare a DNS server in our configuration ahead of time. the usual workflow is that either resolved picks the DNS configuration automatically up from networkd, or that "resolvectl dns" is invoked by some external tool (e.g. NetworkManager) that tells systemd about the DNS servers to use the moment the ifaces appear.“
From nmcli output I guess, libvirt doesn’t use NetworkManager to create virbr0:
[...]# nmcli dev DEVICE TYPE STATE CONNECTION br2s0 bridge verbunden BR2s0 virbr0 bridge connected (externally) virbr0 enp2s0 ethernet verbunden System enp2s0 vnet0 tun connected (externally) vnet0. vnet…
Anyway, systemd-resolved does not work smoothly with libvirt. But libvirt is Federa Server's recommended virtualisation tool.
What does this imply for the switch to systemd-resolved for Fedora Server? Does it really make sense?