On Thu, 20 Jan 2022 19:20:22 -0600 Thomas Cameron wrote: > But this is the behavior Linux has used for years and years. If you set > your hostname to localhost.localdomain, say via a kickstart script or a > golden image you use to spin up dozens of instances, previous versions > of Fedora would find the hostname via DNS and assign it at boot. I never once had that happen. And I installed hundreds of virtual machines with different releases for different distros for testing at work. What I have had happen is if I installed the name in DNS prior to installing the VM, and if I installed a fixed MAC->IP mapping in the DHCP server, then installed the VM using the expected MAC for the virtual interface, the machine at install time would find the name and use it instead of localhost.localdomain. In practice though, I found it much simpler (though not all that simple given the 47,321 pages of named docs) to set up dynamic DNS along with the DHCP server, then specify the hostname of the virtual machine at install and let the DHCP/DNS combo install that name in the DNS server for the virtual machine subnet at boot. Especially once I got more than 256 virtual machines, and they had to share IP addrs on the subnet (couldn't have more than 10 or so actually running at once). _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-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/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
