MAAS injected region controller as first DNS server

[Jacek Nykis]

I was deploying a machine using MAAS 1.9.5. In my subnet config I had 2 DNS server listed, both of them in the same subnet as cluster controller and the server I was provisioning.

I was getting failures and with developers help we found that it was a DNS problem. My machine could not talk to the MAAS region controller using DNS name.

We switched to use IP address and noticed that it was because MAAS injected region controller as first DNS server in resolv.conf and our firewalls block this type of traffic.

I specifically checked DNS settings and tested both servers listed in my subnet config. MAAS region controller is definitely not showing there, it was added silently.

un maas <none> <none> (no description available)
ii maas-cli 1.9.5+bzr4599-0ubuntu1~14.04.2 all MAAS command line API tool
un maas-cluster-controller <none> <none> (no description available)
ii maas-common 1.9.5+bzr4599-0ubuntu1~14.04.2 all MAAS server common files
un maas-dhcp <none> <none> (no description available)
ii maas-dns 1.9.5+bzr4599-0ubuntu1~14.04.2 all MAAS DNS server
ii maas-proxy 1.9.5+bzr4599-0ubuntu1~14.04.2 all MAAS Caching Proxy
ii maas-region-controller 1.9.5+bzr4599-0ubuntu1~14.04.2 all MAAS server complete region controller
ii maas-region-controller-min 1.9.5+bzr4599-0ubuntu1~14.04.2 all MAAS Server minimum region controller
ii python-django-maas 1.9.5+bzr4599-0ubuntu1~14.04.2 all MAAS server Django web framework
ii python-maas-client 1.9.5+bzr4599-0ubuntu1~14.04.2 all MAAS python API client
ii python-maas-provisioningserver 1.9.5+bzr4599-0ubuntu1~14.04.2 all MAAS server provisioning libraries