https://bind9.readthedocs.io/en/v9.18.27/reference.html#namedconf- statement-automatic-interface-scan is the default enabled feature that causes bind9 to start the conflicting listener, or at least I think it is.
I believe this is more a bug with how MAAS configures bind9 than something LXD could improve on. LXD really needs that dnsmasq listener so bind9 taking it over is nothing LXD can do about. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1995194 Title: lxd init fails with 'Address already in use' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1995194/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
