Ask Your Question

How does dnsmasq configuration get reloaded when dhcp_domain is set

asked 2013-05-21 09:03:54 -0500

updated 2013-06-11 10:25:43 -0500

fifieldt gravatar image

On a running openstack deployement I am trying to modify dhcp_domain in /etc/nova/nova.conf but this isn't taken into account when I start an instance.

What service do I have to restart or which command do I have to issue to get it to run ?

I am looking at the --domain= in dnsmasq instances (I have over 30 on each compute node) but no new dnsmasq with my new domain name seems to pop up.

Additional question : is there a way to apply this new domain name to all running instances ?

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2013-05-21 10:59:35 -0500

lorin gravatar image

Assuming you're running nova-network and not quantum, on the cloud controller you need to kill all of the dnsmasq processes and restart the nova-network service. On Ubuntu, this should work (as root):

killall dnsmasq
restart nova-network

When nova-network starts up again, it will start up the dnsmasq processes using the configuration options specified in your nova.conf file.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools


Asked: 2013-05-21 09:03:54 -0500

Seen: 4,571 times

Last updated: May 21 '13