yahoo-eng-team team mailing list archive

[OpenStack Infra <1950686@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/neutron/+/820858
Committed: https://opendev.org/openstack/neutron/commit/a416f8b0ab810f34ea274183df590a73d150a137
Submitter: "Zuul (22348)"
Branch:    master

commit a416f8b0ab810f34ea274183df590a73d150a137
Author: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
Date:   Tue Dec 7 11:42:53 2021 +0000

    Do not announce any DNS resolver if "0.0.0.0" or "::" provided
    
    The DHCP server should not announce any DNS resolver at all on the
    subnet if "0.0.0.0" (IPv4) or "::" (IPv6) are configured as DNS
    name servers in any subnet.
    
    https://docs.openstack.org/neutron/latest/admin/config-dns-res.html
    
    Closes-Bug: #1950686
    Change-Id: I78dd012764c7bd7a29aeb8d97c00b627d7723aeb


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1950686

Title:
  [OVN] dns-nameserver=0.0.0.0 for a subnet isn't treated properly

Status in neutron:
  Fix Released

Bug description:
  As documented in
  https://docs.openstack.org/neutron/latest/admin/config-dns-
  res.html#case-1-each-virtual-network-uses-unique-dns-resolver-s ,
  setting dns-nameserver=0.0.0.0 for a subnet should indicate that DHCP
  should not advertise any DNS server to instances on that subnet. This
  works fine with LB or OVS, but with OVN, instead the IP 0.0.0.0 is
  advertised as nameserver to instances.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1950686/+subscriptions