Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Currently libvirtd runs dnsmasq without setting domain or giving possibility to specify domain search list. This makes DHCP NAT networking unfriendly as host "appserver" won't get resolved, one needs to use FQDN "appserver.a.example.com". In many customer environments there are scripts, applications, and services which depend on properly specified domain search list.
Killing the libvirtd instance started by dnsmasq and running the same command manually but also using a proper configuration file solves this issue. It would be very helpful if either the configuration file could be specified in the network XML file or the related options could be added to XML directly.
The following dnsmasq options would be most needed:
expand-hosts
domain=a.example.com
dhcp-option=119,"a.example.com b.example.com example.com"
Version-Release number of selected component (if applicable):
RHEL 6.0 RC 1
Note that this option:
domain=a.example.com
is added to the dnsmasq configuration whenever the line:
<domain name='a.example.com'/>
is put in the network definition XML. This feature has been present since libvirt version 0.4.5, so it is already in RHEL6.0.
the "expand-hosts' option has also been present since libvirt 0.9.3, so it will be in the next RHEL release.
That leaves only:
dhcp-option=119,"a.example.com b.example.com example.com"
to be implemented.