Release notes for dns_domain behavioural changes
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.
Add new release note to detail the behaviour of
{network,conf}.dns_domain with respect to the DHCP agent
post upgrade.
The deleted release note will be restored in the stable
branches where it was removed.
Change-Id: Ic668d64c28cdc1068cb2413b09839a127bad46d3
Related-Bug: 1826419
This commit is contained in:
12
releasenotes/notes/dns_domain-1799b939e7248247.yaml
Normal file
12
releasenotes/notes/dns_domain-1799b939e7248247.yaml
Normal file
@@ -0,0 +1,12 @@
|
||||
---
|
||||
fixes:
|
||||
- |
|
||||
A previous bug fix changed the behaviour of the DHCP agent to use a
|
||||
network's ``dns_domain`` as the search path provided to instances
|
||||
overriding the ``dns_domain`` configuration option used by both the DHCP
|
||||
agent and the main server process when generate port DNS assignments.
|
||||
This broke the original design intent of the ``dns_domain`` attribute of
|
||||
a network which was for integration with external DNS systems such as
|
||||
Designate rather than for use in Neutron's internal DNS support.
|
||||
This incorrect change in behaviour has now been reverted - the DHCP
|
||||
agent will only ever use the ``dns_domain`` configuration option.
|
||||
Reference in New Issue
Block a user