On Sun, 2021-02-21 at 23:03 +0100, Peter Boy wrote:
I'm testing update my servers from F32 to F33. Situation is: Fedora Server running several Fedora VMs. VMs and host are using libvirt default network via virbr0 for internal private data exchange. A second public bridge provides external connectivity. On virbr0 the DNS service is activated so host and VMs can find each other via name instead IPs.
In F32 I used NetworkManagers dnsmasq plugin to forward internal request (names ending .lan) to libvirt dnsmasq on virbr0 / 192.169.122.1 and everything else to our public DNS.
With F33 I'm to use systemd-resolved which is dns-split capable. The F33 VMs, which have 2 fixed interfaces eht0 (public) and eth1 (private), everything works out of the box without a hitch.
On the F33 Server I had to add two entries to /etc/systemd/resolved.conf: DNS=192.168.122.1%virbr0#example.lan ## (.lan = private domain) Domains=example.lan ## search domain, appended to names w/o a dot
After a reboot it only works after I restart systemd-resolved. Otherwise it fails to resolve internal names / addresses.
My "trusted search engine" showed some discussion but no solution (at least I couldn't identify one).
Can it be, in any rate, connected with https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/... ?
This bug (I don't know if it's fixed yet) hit me on my local dns server, too, but I didn't split dns resolvers for multiple interfaces.
If not, I would guess that systemd-resolved is starting up before network interfaces. Is systemd-resolved unit configured with "Wants=*", or "Require=*"?