[Bug 1066958] Re: DNS config is invalid after a node gets enlisted.
Diogo Matsubara
matsubara at canonical.com
Tue Oct 23 19:45:26 UTC 2012
** Tags removed: verification-needed
** Tags added: verification-done
** 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 CASE ==
1. Install MAAS and manage DHCP/DNS server.
- 2. Enlist machine
+ 2. Enlist machine
3. Make sure DNS config is correct
+
+ Tested in the lenovo lab. No CNAME records appear in the zone.master
+ file.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in 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
More information about the Ubuntu-server-bugs
mailing list