Red Hat Bugzilla – Bug 508965
Disabling DHCP also turns off DNS forwarding for a libvirt network
Last modified: 2010-03-16 13:21:38 EDT
Description of problem:
Disabling libvirt-controlled DHCP (/network/ip/dhcp) also prevents DNS forwarding from being available to the relevant libvirt-controlled network.
This could be resolved by running dnsmasq with the --no-dhcp-
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a libvirt network without /network/ip/dhcp defined.
2. Start a guest in that network.
3. Attempt to resolve names through DNS through the host's IP on that network (/network/ip/@address)
DNS service should be available via the IP defined in the network XML at /network/ip/@address, just as it is with DHCP running.
No DNS redirection is available.
dnsmasq has a --no-dhcp-interface= argument which can be used to implement this functionality.
This was addressed in the 0.7.0 release in the following commit
author: Daniel P. Berrange <firstname.lastname@example.org>
Thu, 30 Jul 2009 13:52:31 +0000 (14:52 +0100)
Allow dnsmasq to provide DNS without DHCP
* src/network_driver.c: Always start dnsmasq to allow it to provide
DNS, even if no DHCP ranges are enabled