[Bug 1580588] Re: [RFE] use network's dns_domain to generate dns_assignment

[James Page]

This commit:

  https://opendev.org/openstack/neutron/commit/137a6d61053

has somewhat complicated this problem as the dns_domain set on the
network now might get used in some parts of the configuration of the
dnsmasq instance for a network.

This becomes inconsistent as a dns_assignment record is generated for a
port centrally using the CONF.dns_domain which is then used by the DHCP
agent to generate the hosts file for dnsmasq, however the "--domain"
parameter for the dnsmasq instance will be set to the dns_domain of the
network.

Net result is that forward/reverse lookups are not mirrored:

root at bionic-045546-2:~# host 192.168.21.222
222.21.168.192.in-addr.arpa domain name pointer bionic-045546-2.jamespage.internal.
root at bionic-045546-2:~# host bionic-045546-2
bionic-045546-2.designate.local has address 192.168.21.222

and the search path for an instance is set to the dns_domain of the
network which won't match the dns_assigned records written to the hosts
file for dnsmasq.

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1580588

Title:
  [RFE] use network's dns_domain to generate dns_assignment

Status in neutron:
  Confirmed
Status in neutron package in Ubuntu:
  New

Bug description:
  Problem:
  currently, the port's dns_assignment is generated by combining the dns_name and conf.dns_domain
  even if the dns_domain of port's network is given.

  expectation:

  generate the dns_assignment according to the dns_domain of port's network, which will scope the dnsname by
  network instead of each neutron deployment.

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