> Am 10.09.2021 um 17:22 schrieb Daniel P. Berrangé <berrange@xxxxxxxxxx>: > > On Fri, Sep 10, 2021 at 04:57:56PM +0200, Peter Boy wrote: >> (a) === Installing libvirt-nss. (Daniel Berrange) === >> >> I did the following >> >> 1. dnf install libvirt-nss >> >> 2. Modified following the libvirt documentation and the docs included with the files /etc/authselect/user-nsswitch.conf and edited the hosts item to "hosts: files myhostname libvirt resolve [!UNAVAIL=return] dns“ >> >> 3. executed: authselect apply-changes >> >> 4. reboot >> >> Neither using standard DNS without systems-resolved activated nor using systemd-resolved could resolve the internal names of the VM > > I think you possibly mis-interpret what the libvirt-nss module is going > to be doing here. Unfortunately, I was swamped and it took a while to do the test installations. Indeed, in the head of the action I overlooked that DNS clients use DNS of course. > Finally, libvirt-nss provides two modules. > > - "libvirt" does lookups against the hostname configured by > the guest OS when acquiring its DHCP lease. This hostname > is either set by the guest OS admin, or can be the hostname > in the libvirt network XML config (virsh net-dumpxml default) > if you're using fixed host<->ip<->mac mappings. > > - "libvirt_guest" does lookups against the guest name known > to libvirt in the host. (ie name reported by 'virsh list‘) . > > . . . . > Personally I always use the "libvirt_guest" NSS module, so get > host lookups using the libvirt guest name, but either NSS module > is valid based on your desired outcome. Thanks for all the information. Specifically libvirt_guest was very helpful. After all everything you detailed worked fine in my test installations and the libvirt_guest / nss part is currently a workaround for some inconsistency with resolvectl to handle a single, non FQN hostname. Many thanks Peter By the way you may remember CCM and Aplaws you were working on about a decade ago. It’s still alive and in use. I lead the project for several years and we are working on a transition to JEE 8/9 retaining the outstanding architectural features as structured content and strong categorisation (mirror: https://github.com/libreccm). So your work at that time did not vanish. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
