DNS not being updated with hosts not managed by MAAS

[David Bainbridge]

In my network I have standard compute nodes that PXE boot and are assigned IP addresses by MAAS as well as their names are propagated to bind9 (DNS).

I also have switches with a management connection assigned dynamically as well as uvt-kvm created hosts with an IP assigned dynamically. These latter nodes are given a valid IP address from MAAS, but their names are not propagated to bind9 (DNS).

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.8.3+bzr4053-0ubuntu1~trusty1 all MAAS server all-in-one metapackage
ii maas-cli 1.8.3+bzr4053-0ubuntu1~trusty1 all MAAS command line API tool
ii maas-cluster-controller 1.8.3+bzr4053-0ubuntu1~trusty1 all MAAS server cluster controller
ii maas-common 1.8.3+bzr4053-0ubuntu1~trusty1 all MAAS server common files
ii maas-dhcp 1.8.3+bzr4053-0ubuntu1~trusty1 all MAAS DHCP server
ii maas-dns 1.8.3+bzr4053-0ubuntu1~trusty1 all MAAS DNS server
ii maas-proxy 1.8.3+bzr4053-0ubuntu1~trusty1 all MAAS Caching Proxy
ii maas-region-controller 1.8.3+bzr4053-0ubuntu1~trusty1 all MAAS server complete region controller
ii maas-region-controller-min 1.8.3+bzr4053-0ubuntu1~trusty1 all MAAS Server minimum region controller
ii python-django-maas 1.8.3+bzr4053-0ubuntu1~trusty1 all MAAS server Django web framework
ii python-maas-client 1.8.3+bzr4053-0ubuntu1~trusty1 all MAAS python API client
ii python-maas-provisioningserver 1.8.3+bzr4053-0ubuntu1~trusty1 all MAAS server provisioning libraries

[Andres Rodriguez (andreserl)]

Hi David,

MAAS 1.8/1.9 does not provide DNS records names for anything other than 3 things:

1. The IP address of the PXE interface of the node, based on the node's name.
3. Devices that obtain an IP address from the static range.
2. Any IP address on the dynamic range, based on the IP. Say, the IP is 192.168.2.2, the DNS would be: 192-168-2-2.maas or similar. IN other words, everything that obtains a IP address from the *Dynamic* range won't get a DNS based on the name of a node or device, it will get it based on the IP.

I'm marking this bug invalid.

Also, please note that better support for DNS is provided in MAAS 2.0

[Andres Rodriguez (andreserl)]

Please note that if you list all your Devices as "Devices" in MAAS, and make sure they get an IP address from the Static range, MAAS will add the DNS records for those IP's of the device. This should resolve the issue you are having.

[Christian Reis (kiko)]

I've added a feature request to our roadmap that describes the workflow that would allow easily converting a detected device (which has the "anonymous" IP-based XXX.maas DNS) into a managed device, which can be named and its IP address assignment mechanism modified.