Hi guys,
I upgraded a rack controller from Ubuntu 18.04 and Maas 2.8 to Ubuntu 22 and Maas 3.3.
Everything is fine except the DNS service, named fails to start.
From syslog:
Jun 28 13:41:13 dc3-it-maas-01 named[4716]: loading configuration from '/etc/bind/named.conf'
Jun 28 13:41:13 dc3-it-maas-01 named[4716]: /etc/bind/maas/named.conf.maas:2: parsing failed: file not found
Jun 28 13:41:13 dc3-it-maas-01 named[4716]: loading configuration: file not found
Jun 28 13:41:13 dc3-it-maas-01 named[4716]: exiting (due to fatal error)
Jun 28 13:41:13 dc3-it-maas-01 systemd[1]: named.service: Control process exited, code=exited, status=1/FAILURE
Jun 28 13:41:13 dc3-it-maas-01 systemd[1]: named.service: Failed with result 'exit-code'.
Jun 28 13:41:13 dc3-it-maas-01 systemd[1]: Failed to start BIND Domain Name Server.
And in bind configuration files:
dc3-it-maas-01:/etc/bind/maas$ head -2 named.conf.maas
include "/etc/bind/maas/named.conf.rndc.maas";
include "/etc/bind/maas/keys.conf.maas";
dc3-it-maas-01:/etc/bind/maas$ ls -l
total 16
-rw-r--r-- 1 maas maas 407 Jun 28 13:34 named.conf.maas
-rw-r--r-- 1 maas maas 165 Jun 28 13:34 named.conf.options.inside.maas
-rw-r----- 1 maas bind 257 Nov 15 2019 named.conf.rndc.maas
-rw------- 1 maas root 539 Nov 15 2019 rndc.conf.maas
As opposed to my region controller I do not have this file here keys.conf.maas and I confirm that it did not exist before starting my upgrade (so at 2.8)
When I comment this line (which is absent as well in my backup from 2.8)
# include "/etc/bind/maas/keys.conf.maas";
And restart the service, everything is fine.
The issue is those files keep being regenerated at each reboot and the line uncommented/added.
What is the good way to proceed here?
Thanks!