Instance gets dns nameservers in incorrect order

asked 2015-02-28 20:11:25 -0600

If multiple dns-nameservers are assigned to a subnet using the GUI or the neutron command, then the list of dns nameservers given to a launched instance is in the wrong order. For example: if the dns-nameservers specified in the GUI are and then the Instance is given and With dns nameservers, the search order is critical! You usually want to search the local nameserver first. [ System Config: Devstack with neutron version 2.3.10, Virtualbox version 4.3.22, Windows 8.1]

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted

answered 2015-03-06 03:36:55 -0600

Poonam Agarwal gravatar image

Can you try adding below to /etc/nova/nova.conf to see if it populates in the correct order?

dns_server =
dns_server =

However agree that both DNS Servers should be equally capable of servicing the requests and if one fails , the other one should be queried automatically

edit flag offensive delete link more


This won't work. Neutron is involved and not nova network. Dnsmasq is responsible for handing out ips not nova.

sfcloudman gravatar imagesfcloudman ( 2015-03-06 08:58:21 -0600 )edit

answered 2015-03-01 15:29:51 -0600

DNS should not be designed the way you are thinking. The values used for DNS servers should be redundant name servers and should be exact replicas of each other.

If you are using and as your name servers then if becomes unavailable then .1 will used to try to get name resolution. Its is not normally meant that these 2 servers have different host records. These 2 servers should know about their peer resolvers and should forward any unknown resolutions to their peers.

The search order is actually defined , on linux, in /etc/nsswitch.conf.

hosts:          files dns
edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2015-02-28 20:09:56 -0600

Seen: 300 times

Last updated: Mar 06 '15