On 11/19/2012 03:27 PM, Gene Czarcinski wrote:
On 11/19/2012 01:06 PM, Laine Stump wrote:
> Here is an open BZ that mentions the idea of adding similar
> functionality for dnsmasq (see comment 8, in particular):
>
>
https://bugzilla.redhat.com/show_bug.cgi?id=824573
I also found Comment 2 where Dave Allan says "The intent is that
people who want a basic setup can configure it thorough libvirt, but
people who want full control of DHCP can turn off the libvirt
configured DHCP server, and libvirt will play nicely with a manually
configured DHCP server."
Really? I was unaware of the ability to disable libvirt's dnsmasq
instance except when no gateway addresses are specified.
You can disable listening on the dhcp port by simply not having a <dhcp>
section in the network definition. The DNS service is always present if
you define an IP address for the network though.
The confusion comes when someone tries to start up their own dnsmasq,
which also wants to run its own DNS service, on the same bridge - the
entire thing fails. If you run a pure dhcp server though, it should work
with no problems.
I have plans to disable even the dns server if someone specifies "<dns
enable='no'/>" in their network config (we can't do it based on the
absence of a <dns> element, since that has never before meant "no dns"),
but that's not implemented yet.