137a6d6105
The Neutron API exposes the 'dns_domain' attribute on the Network model. Presently, deployments using the DHCP agent ignore this attribute when resolving DNS queries between instances. This patch changes that so that the DHCP agent will pass on the dns_domain to the network's dnsmasq process, in turn passing it to instances. UpgradeImpact Closes-Bug: 1774710 Change-Id: I6120d504959631f084d63458f6e9dada0dc5cbdf
14 lines
732 B
YAML
14 lines
732 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Previously a network's dns_domain attribute was ignored by the DHCP agent.
|
|
With this release, OpenStack deployments using Neutron's DHCP agent will
|
|
be able to specify a per network dns_domain and have instances configure
|
|
that domain in their dns resolver configuration files (Linux's
|
|
/etc/resolv.conf) to allow for local partial DNS lookups. The per-network
|
|
dns_domain value will override the DHCP agent's default dns_domain
|
|
configuration value. Note that it's also possible to update a network's
|
|
dns_domain, and that new value will be propogated to new instances
|
|
or when instances renew their DHCP lease. However, existing leases will
|
|
live on with the old dns_domain value.
|