yahoo-eng-team team mailing list archive

["Dr. Jens Harbott" <j.harbott@xxxxxxxx>]

We have the same use case as in comment #2, an isolated subnet shared
between tenants in order to share some internal services. Greatest issue
is multiple tenants choosing identical instance names, resulting in DNS
doing round-robin across all of them.

My proposed solution is to redefine the behaviour when setting
`dns_servers = [ "0.0.0.0" ]`, currently this has this effect that each
dhcp agent will announce only itself as DNS server, which seems less
useful than the behaviour when dns_servers is unset, where it will
announce all agents. I'll upload a patch for that, please let me know
what you think about it.

** Changed in: neutron
       Status: Expired => Confirmed

-- 
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:
  Confirmed

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