Unfortunately, those are all the logs I have. I can spin up another fresh VM and run again, however.
The interesting thing is that bind9 is still started, it's just not listening on TCP port 53 on any address/interface. I thought of capabilities because A: it binds correctly without them enabled, and B: that "operation not permitted" error seemed that it couldn't "sudo" to root in order to bind to that privileged port before switching over to the "bind" user for the rest of the process. (Apologies in advance for incorrect terminology; I'm not that knowledgeable on the bind9 startup process) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886528 Title: BIND9: unable to set effective uid to 0: Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1886528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
