Related to bug 1580588 - there seems to have been some discussion in the past about the dns_domain attribute of a network being used for external DNS integration only.
The changes that form part of the fix for this bug make that boundary less clear and its possible to end up with inconsistency between the records being written to the dnsmasq hosts file (based on the CONF.dns_domain which is used by neutron to generate the dns_assignment properties for a port) and the value passed for "--domain" to dnsmasq which will prefer the dns_domain of the network if set over CONF.dns_domain. This results in forward/reverse lookup inconsistency against the dnsmasq for the network: 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 In this deployment network.dns_domain == designate.local. and CONF.dns_domain == jamespage.internal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774710 Title: DHCP agent doesn't do anything with a network's dns_domain attribute To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1774710/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
