Facing old bug LP:1683047 with MaaS 2.5 stable - bind9 fails to start, duplicated entry

Mine appears to have happened when the region and rack controllers auto-detected a new interface on a subnet and assigned it to the wrong fabric.