Public bug reported: The logic to prevent SLAAC entries from being entered as hosts into the lease DB[1] is preventing the hosts from getting name resolution from dnsmasq.
1. https://github.com/openstack/neutron/blob/7707cfd86f47dfc66411e274f343fe8484f9e250/neutron/agent/linux/dhcp.py#L534-L535 ** Affects: neutron Importance: Undecided Assignee: Kevin Benton (kevinbenton) Status: New ** Changed in: neutron Assignee: (unassigned) => Kevin Benton (kevinbenton) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1498665 Title: no dnsmasq name resolution for slaac addresses Status in neutron: New Bug description: The logic to prevent SLAAC entries from being entered as hosts into the lease DB[1] is preventing the hosts from getting name resolution from dnsmasq. 1. https://github.com/openstack/neutron/blob/7707cfd86f47dfc66411e274f343fe8484f9e250/neutron/agent/linux/dhcp.py#L534-L535 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1498665/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
