** Description changed: Steps to reproduce: (1) Install MAAS. (2) Add an interface to a MAAS controller with an IP address - (3) Observe that bind9 is not listening on that interface, and MAAS - internal domains will not resolve (for example, if you run something - like `dig @172.16.99.1 172-16-99-0--24.maas-internal`), assuming - 172.16.99.1 is the IP address that was added to the controller. + (3) Observe that bind9 is responding on the new interface/IP; neither + MAAS internal domains nor recursive queries will resolve (for example, + if you run something like `dig @172.16.99.1 172-16-99-0--24.maas- + internal`), assuming 172.16.99.1 is the IP address that was added to the + controller. (4) If a machine in MAAS attempts to resolve DNS via the new interface, - it will always fail, since bind9 is not listening on that interface/IP + it will always fail, since bind9 is not responding on that interface/IP address. - Conclusion: If MAAS observes an interface or IP address being added or removed to a controller where bind9 is running, MAAS must restart bind9 in order for the DNS server to properly operate, given those changes in the network.
** Description changed: Steps to reproduce: (1) Install MAAS. (2) Add an interface to a MAAS controller with an IP address (3) Observe that bind9 is responding on the new interface/IP; neither MAAS internal domains nor recursive queries will resolve (for example, if you run something like `dig @172.16.99.1 172-16-99-0--24.maas- internal`), assuming 172.16.99.1 is the IP address that was added to the controller. (4) If a machine in MAAS attempts to resolve DNS via the new interface, it will always fail, since bind9 is not responding on that interface/IP address. - Conclusion: + Conclusions: - If MAAS observes an interface or IP address being added or removed to a - controller where bind9 is running, MAAS must restart bind9 in order for - the DNS server to properly operate, given those changes in the network. + - This seems to be a bug in bind9; bind9 should be fixed to properly respond to queries on the new interfaces. (note that MAAS also includes the new networks in its trusted ACL configuration when it sees the new network). bind9 should be fixed to not require a restart in this situation. + - Possible workaround in MAAS: If MAAS observes an interface or IP address being added or removed to a controller where bind9 is running, MAAS must restart bind9 in order for the DNS server to properly operate, given those changes in the network. ** Summary changed: - [2.5] MAAS must restart the bind9 service if controller IP addresses change + After interface/IP changes, bind9 can fail to respond to queries on the new interface -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796164 Title: After interface/IP changes, bind9 can fail to respond to queries on the new interface To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1796164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
