MAAS DNS fails to update with correct information

[Imran]

You have the flat network layout, MAAS installed on a machine, one /24 range given to MAAS to look after (DNS and DHCP).

On a machine you have 3 interfaces, 2 bonded, one not, you set the bonded one to be a static ip in your subnet/fabric/range and you leave the other one unconfigured, however it is used to PXE boot.

You commission the machine and click leave the network config alone, MAAS updates the bind server with the floating IP that was given to the non-bonded interface used to PXE boot.

If you use the Openstack Installer from Landscape for example, the machine will go into deploying mode and the OS will be setup, MAAS still hasn't updated bind, once the machine switches to "Deployed" state bind is not updated and various things on the machine fail because it does a hostname lookup for itself, MAAS tells it the floating IP that the unconfigured interface got from DHCP and things fail.

A manual workaround is to wait until the machine is set to "Deployed", quickly edit /etc/bind/maas/zone.<dns name> on the MAAS server with the correct IP addresses, restart bind, before the OS boots so when does lookups it gets the right IP address. During the landscape auto install you'll have to do this several times as the IPs get set back when the other nodes come online.

root@ubuntu-maas:~# dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===================================-=====================================-============-===============================================================================
ii maas 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS server all-in-one metapackage
ii maas-cli 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS command line API tool
ii maas-cluster-controller 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS server cluster controller
ii maas-common 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS server common files
ii maas-dhcp 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS DHCP server
ii maas-dns 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS DNS server
ii maas-proxy 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS Caching Proxy
ii maas-region-controller 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS server complete region controller
ii maas-region-controller-min 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS Server minimum region controller
ii python-django-maas 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS server Django web framework
ii python-maas-client 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS python API client
ii python-maas-provisioningserver 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS server provisioning libraries

[Andres Rodriguez (andreserl)]

In 1.9 on any earlier release, MAAS will only provide DNS mapping against the PXE interface. As such, when leaving the PXE interface unconfigured, the machine will DHCP from MAAS' Dynamic range, causing to not create a DNS record against the node, and hence DNS resolution will fail.

MAAS 2.0 will continue to provide DNS mapping against PXE, but provide PTR records for the rest of interfaces.