** Description changed: After a node gets enlisted, its hostname is set to a generated address based on its IP address (e.g. 192-168-10-10). When the DNS config gets written, if the hostname is not changed to a custom value, the CNAME record conflicts with a pre-populated A record for that IP: Content of /etc/bind/maas/zone.master IN NS master. master. IN A 192.168.10.1 [...] 192-168-10-10 IN A 192.168.10.10 [...] 192-168-10-10 IN CNAME 192-168-10-10 One solution is to change DNSForwardZoneConfig.get_cname_mapping so that the records where generated_hostname(ip) == hostname are filtered out. - == TEST == - This fix has been tested on both canonistack and in the lenovo lab. + == TEST CASE == + 1. Install MAAS and manage DHCP/DNS server. + 2. Enlist machine + 3. Make sure DNS config is correct
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066958 Title: DNS config is invalid after a node gets enlisted. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1066958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
