dhcp_agent only allows one dnsmasq_dns_server
Bug #1240027 reported by
Jesse Pretorius
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Sylvain Afchain |
Bug Description
As quantum.
This is not ideal.
Ideally if a network is not created with its own dns server options, the options provided in dnsmasq_dns_server should be used and put into the opts file just as the network-configured options would be.
This would enable dns to work without dns options configured on the network using defaults provided by the deployer.
Changed in neutron: | |
status: | Incomplete → New |
Changed in neutron: | |
assignee: | nobody → Sylvain Afchain (sylvain-afchain) |
Changed in neutron: | |
importance: | Undecided → Medium |
milestone: | none → icehouse-3 |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | icehouse-3 → 2014.1 |
To post a comment you must log in.
If the tenant does not define a name server for the network, the update DNS is the dnsmasq. dnsmasq will default to the servers for the network host. Are you proposing that this option be converted to a list?