Bind9 failing to start

I am trying to commission RPI from my MaaS rack+region controller, Lenovo T500 running Ubuntu 18.04LTS

The error seems similar to what is here, but the workaround solution doesn’t seem to apply to me.

I found this link as well but it doesn’t seem helpful enough to be related.

I have attached texts of the relevant logs. I would appreciate any insight the community may have in order to solve and commission my PIs.

sudo tail -f /var/snap/maas/common/log/maas.log
sudo snap restart maas.supervisor
sudo maas status
sudo snap logs -f maas.supervisor

sudo cat /var/snap/maas/15003/bind/rndc.conf.maas
sudo cat /var/snap/maas/15003/bind/named.conf

This is what my MAAS-defined subnets looks like:

Thank you for your time and attention.

1 Like

I was able to solve the problem by:
sudo apt install bind9-utils -y
sudo service dnsmasq stop
sudo service bind9 stop
sudo chown root:root /var/snap/maas/15003/bind/rndc.conf.maas
sudo chmod 640 /var/snap/maas/15003/bind/rndc.conf.maas
sudo rndc -c /var/snap/maas/15003/bind/rndc.conf.maas reload
sudo snap restart maas.supervisor

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.