openstack/neutron
Code Issues Proposed changes

Release notes for dns_domain behavioural changes

Browse Source 
As part of the fix for bug 1826419, a prior release note was
deleted and no new release note was added to document the
change in behaviour as a result of upgrading.

Restore deleted release note in the stable branches,
the new note will be added in the master branch.

Change-Id: Ic668d64c28cdc1068cb2413b09839a127bad46d3
Related-Bug: 1826419
This commit is contained in:
James Page
2019-06-11 14:02:44 +01:00
committed by Brian Haley
parent 4cd7ba7fde
commit e3330b10a9
1 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
releasenotes/notes/dns_domain-6f0e628aeb3c650c.yaml Normal file
View File

@@ -0,0 +1,13 @@
---
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.