yahoo-eng-team team mailing list archive

[OpenStack Infra <1311040@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/495781
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=584b7561c162ec461e5c6a8dff5c012402cac5e0
Submitter: Jenkins
Branch:    master

commit 584b7561c162ec461e5c6a8dff5c012402cac5e0
Author: Jens Harbott <j.harbott@xxxxxxxx>
Date:   Mon Aug 21 09:13:33 2017 +0000

    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


** 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/1311040

Title:
  Subnet option to disable dns server

Status in neutron:
  Fix Released

Bug description:
  Multiple NIC/subnet may attach to a VM instance, if both subnets
  provide dns servers, only the last one will be used (overrides the
  previous one), so we need a method to disable dns server on some
  subnets.

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