Public bug reported:
In debugging bug #1694156, I found that ultimately my problem was
triggered by a hard-coded /etc/resolvconf/resolv.conf.d/tail I had set
once upon a time pointing to my libvirt dnsmasq server. It should not
be necessary to manually edit /etc/resolvconf/resolv.conf.d/tail to
register dnsmasq; instead, on a system where systemd-resolved is
running, libvirt should use the DBUS protocol to register its dnsmasq
with systemd-resolved, specifying both SetLinkDNS and SetLinkDomains.
This would enable properly-scoped DNS lookups for only the hosts on the
libvirt bridge, avoiding any possibility of DNS loops and avoiding the
need for manual configuration.
To do this properly, libvirt does need to declare a link domain
(SetLinkDomains) that doesn't conflict with other public DNS, or other
non-authoritative DNS that may be configured on the system. I would
suggest using just 'libvirt.' as a TLD, by default.
For example implementation, please see ./src/dns-manager/nm-dns-systemd-
resolved.c:send_updates() in the network-manager source.
** Affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694161
Title:
libvirt should register its dnsmasq with systemd-resolved, and set a
suitable domain for lookups (e.g. 'libvirt.')
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1694161/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
