I’ve got this issue after renaming my DNS domain “maas” to “maas.mycompany.org”.
(For safety, I re-created a DNS domain “maas” with just a single host A-entry for my maas server (so that previously installed clients still find their configured proxy server).
After a full restart of my maas server, everything seemed to work fine. But a few minutes later, I realized, that DHCP isn’t working any more. Same result of sudo maas status
as from routergod
My current maas version is:
maas 3.2.7-12037-g.c688dd446
When I take a look into the subnets, I realized that my typical LAN subnet appears at the wrong fabric: my fabric-LAN doesn’t contain any subnets any more, but my fabric-DMZ contains my DMZ subnets + my LAN subnet. Fabric-DMZ is configured for No DHCP
, while Fabric-LAN’s DHCP setting is MAAS-provided
.
After opening my LAN Subnet (attention: it took several seconds or minutes to open/load the page!), I was able to edit my LAN Subnet and re-asssign to my Fabric-LAN.
Et voilĂ : DHCP server is again running and working 
EDIT: The maas logs didn’t contain any useful information for DHCP server.
root@maas:/var/snap/maas/common/log# grep -i "dhcp" /var/snap/maas/common/log/maas.log
root@maas:/var/snap/maas/common/log# grep -i "dhcp" /var/snap/maas/common/log/rackd.log
2023-03-22 10:53:03 provisioningserver.rackdservices.dhcp_probe_service: [info] Probe for external DHCP servers started on interfaces: eth0, eth1.
2023-03-22 10:53:23 provisioningserver.rackdservices.dhcp_probe_service: [info] External DHCP probe complete.
2023-03-22 11:02:53 provisioningserver.rackdservices.dhcp_probe_service: [info] Probe for external DHCP servers started on interfaces: eth0, eth1.
2023-03-22 11:03:13 provisioningserver.rackdservices.dhcp_probe_service: [info] External DHCP probe complete.