I just installed bind9 on a fresh ubuntu 20.04 system, and it started up
just fine, even with apparmor enabled out of the box:
ps:
/usr/sbin/named (enforce) 2696 ? Ssl 0:00 /usr/sbin/named -f
-u bind
ports:
# ss -lnp|grep -E "^tcp.*:53"
tcp LISTEN 0 10 10.0.100.87:53
0.0.0.0:*
users:(("named",pid=2696,fd=55),("named",pid=2696,fd=54),("named",pid=2696,fd=53),("named",pid=2696,fd=52),("named",pid=2696,fd=51))
tcp LISTEN 0 10 127.0.0.1:53
0.0.0.0:*
users:(("named",pid=2696,fd=46),("named",pid=2696,fd=45),("named",pid=2696,fd=44),("named",pid=2696,fd=43),("named",pid=2696,fd=42))
tcp LISTEN 0 4096 127.0.0.53%lo:53
0.0.0.0:*
users:(("systemd-resolve",pid=150,fd=13))
tcp LISTEN 0 10 [fe80::216:3eff:fed6:7653]%eth0:53
[::]:*
users:(("named",pid=2696,fd=75),("named",pid=2696,fd=74),("named",pid=2696,fd=73),("named",pid=2696,fd=72),("named",pid=2696,fd=71))
tcp LISTEN 0 10 [::1]:53
[::]:*
users:(("named",pid=2696,fd=65),("named",pid=2696,fd=64),("named",pid=2696,fd=63),("named",pid=2696,fd=62),("named",pid=2696,fd=61))
You will have to share more information about what is going on in your
environment. The usual culprits of bind not starting up are:
- invalid config
- something else listening on :53 already. Note in the ss output above I have
systemd-resolve listening on 127.0.0.53:53, but that doesn't conflict with bind
because it's a different ip address.
In particular, also check for "listen" options in /etc/bind:
grep listen -r /etc/bind
--
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
