[Openstack-operators] dnsmasq and --no-resolv

Mordur Ingolfsson rass at 1984.is
Mon Dec 30 19:49:25 UTC 2013

Hi, I have a question regarding dnsmasq.

I have a neutron ovs setup with a vlan per tenant.  dhcp on the sub-nets
works fine, but dns resolving from within the instances does not work on
vm instantiation unless I specify external name servers when I create
the sub-net. Otherwise, the first unused ip on the subnet will be in the
vm instance's resolv.conf

This is a typical dnsmasq process in my controller node:

nobody   16068  0.0  0.0  31004   960 ?        S    01:56   0:00 dnsmasq
--no-hosts --no-resolv --strict-order --bind-interfaces
--interface=ns-1416129b-06 --except-interface=lo
--pid-file=/var/lib/neutron/dhcp/fe335957-5ed2-433b-86b3-8324493b07c3/pid --dhcp-hostsfile=/var/lib/neutron/dhcp/fe335957-5ed2-433b-86b3-8324493b07c3/host
--leasefile-ro --dhcp-range=set:tag0,,static,86400s
--dhcp-lease-max=256 --conf-file=/etc/neutron/dnsmasq-neutron.conf

I suspect that the --no-resolv option is to blame for the lack of dns
resolving out of the box. I ask:

1. Do you think that this is a likely explanation?

2. Is this the way things are meant to work?

3. Can I change this so that my hosts resolv.conf content will be
useable  by instances for dns resolving through dnsmasq.

4. Is there a better way? (am I completely misunderstanding everything?)


More information about the OpenStack-operators mailing list