Ask Your Question

How are dnsmasq DNS entries generated and FQDN then sent to instances ?

asked 2013-04-03 13:23:09 -0600

Adrien G. gravatar image

Hi all,

We are facing an issue in our folsom (currently with nova-network) deployment :

As we are using Puppet to manage the configuration of our instances, we need to set up the FQDNs accordingly to pull the right configurations (eg. and will get different configurations based on the environment type prod or dev).

We wanted to proceed in the following way :

In /etc/nova/nova.conf

#Will be common to all of the instances

And then name our instances,, etc. to get the correct FQDN. As it turns out, instances don't get FQDN as expected :

$ hostname
$ hostname -f

So we have a part of the hostname that is stripped. Is this a normal behavior, a misconfiguration ? Is it openstack that strips the hostname before sending it to dnsmasq or rather dnsmasq that creates a dns entry with only what's before the first dot ? Or something else ??


edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2013-04-12 09:21:45 -0600

gfidente gravatar image

dnsmasq explicitly prevents what you're trying from working, see :

By default the names must no have a domain part, ie they must just be a alphanumeric name, without any dots.

You can leave empty the dhcp_domain option and create an additional network with nova-manage, assigning to each a different 'label'.

Such a label is used as a 'tag' for the dnsmasq's dhcp-range argument. You can then use a custom dnsmasq config file (see dnsmasq_config_file option) to set different DHCP options (like the domain suffix) for the different tags.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools


Asked: 2013-04-03 13:23:09 -0600

Seen: 3,943 times

Last updated: Apr 12 '13