| 1 |
--- |
| 2 |
fixes: |
| 3 |
- Prior to Mitaka, name resolution in instances requires specifying DNS |
| 4 |
resolvers via the 'dnsmasq_dns_servers' option in the DHCP agent |
| 5 |
configuration file or via neutron subnet options. In this case, the |
| 6 |
data plane must provide connectivity between instances and upstream DNS |
| 7 |
resolvers. Omitting both of these methods causes the dnsmasq service |
| 8 |
to offer the IP address on which it resides to instances for name |
| 9 |
resolution. However, the static dnsmasq '--no-resolv' process argument |
| 10 |
prevents name resolution via dnsmasq, leaving instances without name |
| 11 |
resolution. |
| 12 |
Mitaka introduces the 'dnsmasq_local_resolv' option, default value False |
| 13 |
to preserve backward-compatibility, that enables the dnsmasq service to |
| 14 |
provide name resolution for instances via DNS resolvers on the host |
| 15 |
running the DHCP agent. In this case, the data plane must provide |
| 16 |
connectivity between the host and upstream DNS resolvers rather than |
| 17 |
between the instances and upstream DNS resolvers. Specifying DNS |
| 18 |
resolvers via the 'dnsmasq_dns_servers' option in the DHCP agent |
| 19 |
configuration overrides the 'dnsmasq_local_resolv' option for all subnets |
| 20 |
using the DHCP agent. |