003091a974
patch 0de1d8d4c introduced a new behavior whereby dnsmasq can rely
on dns resolvers defined in the host's resolv.conf, and it did
that by default.
However this may introduce dns timeouts if the dns servers
are not reachable for whatever reason. This may be especially
likely in certain gate configurations (where the VM under test
is a guest itself).
Regardless of the root-cause analysis, this option should have
defaulted to False to preserve backward compatibility, therefore
this patch restores the old behavior in a way that local DNS
resolution occurs only if the new option variable is set to
True, or the admin has not explicitly set the list of DNS
servers to be injected in the DHCP response.
DocImpact: document how to configure DNS resolution by dnsmasq
Change-Id: I90ab26bfa83c2d23c92110b8da73ef771e11f7bb
21 lines
1.2 KiB
YAML
21 lines
1.2 KiB
YAML
---
|
|
fixes:
|
|
- Prior to Mitaka, name resolution in instances requires specifying DNS
|
|
resolvers via the 'dnsmasq_dns_servers' option in the DHCP agent
|
|
configuration file or via neutron subnet options. In this case, the
|
|
data plane must provide connectivity between instances and upstream DNS
|
|
resolvers. Omitting both of these methods 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.
|
|
Mitaka introduces the 'dnsmasq_local_resolv' option, default value False
|
|
to preserve backward-compatibility, that enables the dnsmasq service to
|
|
provide name resolution for instances via DNS resolvers on the host
|
|
running the DHCP agent. In this case, the data plane must provide
|
|
connectivity between the host and upstream DNS resolvers rather than
|
|
between the instances and upstream DNS resolvers. Specifying DNS
|
|
resolvers via the 'dnsmasq_dns_servers' option in the DHCP agent
|
|
configuration overrides the 'dnsmasq_local_resolv' option for all subnets
|
|
using the DHCP agent.
|