0de1d8d4ca
It's pointless to not include default DNS resolution for Neutron. This adds a new config option (dnsmasq_local_resolv) which defaults to 'True' and will allow for DNS name resolution to work out of the box. The caveat is that if the 'dnsmasq_dns_servers' is set it will override the 'dnsmasq_local_resolv' setting, thus allowing operators to explicitly set their own DNS servers. DocImpact: Default to using local DNS resolution with the DHCP agent. Change-Id: I17a884f467d307432a06f67a9dd93ed2fa6081a3 Closes-Bug: #1466117 Signed-off-by: Kyle Mestery <mestery@mestery.com>
15 lines
885 B
YAML
15 lines
885 B
YAML
---
|
|
fixes:
|
|
- Prior to Mitaka, neither specifying DNS resolvers via the
|
|
'dnsmasq_dns_servers' option in the DHCP agent configuration file nor via
|
|
neutron subnet options causes the dnsmasq service to offer the IP address
|
|
on which it resides to instances for name resolution. However, the static
|
|
dnsmasq '--no-resolv' process argument prevents name resolution via dnsmasq
|
|
leaving instances without name resolution. In Mitaka+, the
|
|
'dnsmasq_local_resolv' option in the DHCP agent configuration file enables
|
|
(by default) the dnsmasq service to provide name resolution for instances
|
|
via DNS resolvers on the host running the DHCP agent by effectively
|
|
removing the '--no-resolv' option from the dnsmasq process arguments.
|
|
Adding custom DNS resolvers to the 'dnsmasq_dns_servers' option in the DHCP
|
|
agent configuration file disables this feature.
|