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@bionic-045546-2:~# host 192.168.21.222 222.21.168.192.in-addr.arpa domain name pointer bionic-045546-2.jamespage.internal. root@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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580588 Title: [RFE] use network's dns_domain to generate dns_assignment To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1580588/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
