neutron/releasenotes/notes/bug-1311040-dhcp-no-dns-09291c23e2ce800a.yaml
Jens Harbott 584b7561c1 Allow to disable DNS server announcement per subnet
Currently there is no way to have DHCP agents not announce DNS servers
for a subnet. The current behaviour when the dns_nameservers option is
set to '0.0.0.0' is that each agent will only announce itself instead of
announcing the list of all dhcp agents for that subnet, which seems not
too useful. So we redefine the meaning of this option to instruct the
DHCP agent to not announce any DNS server in that case.

Actually, going back to square one, it would be more natural to swap the
meaning of "option unset" and "option 0.0.0.0", but that would change
the default behaviour for all existing installation and thus does not
seem feasible.

Change-Id: I32d943360162c483ac1364100a21ab56b13517fb
Closes-Bug: 1311040
2017-09-07 19:20:18 +00:00

17 lines
727 B
YAML

---
prelude: >
DNS server assignment can now be disabled in replies sent from the DHCP agent.
features:
- |
It is now possible to instruct the DHCP agent not to supply any DNS server
address to their clients by setting the ``dns_nameservers`` attribute for
the corresponding subnet to ``0.0.0.0`` or ``::``, for IPv4 or IPv6 subnets
(respectively).
upgrade:
- |
The functionality when a subnet has its DNS server set to ``0.0.0.0`` or
``::`` has been changed with this release. The old behaviour was that each
DHCP agent would supply only its own IP address as the DNS server to its
clients. The new behaviour is that the DHCP agent will not supply any DNS
server IP address at all.