>> # rndc status >> rndc: connect failed: 127.0.0.1#953: connection refused >> >> In syslog I can see among the startup messages: >> >> Jun 30 12:53:31 nlab0 named[31772]: couldn't add command channel >> 127.0.0.1#953: permission denied >> Jun 30 12:53:31 nlab0 named[31772]: couldn't add command channel ::1#953: >> permission denied > > Potentially a change in 9.19's port binding logic triggering by > mac_portacl(4)? > > https://forums.freebsd.org/threads/named-could-not-listen-on-udp-socket-permission-denied.11196/ > > Does it help adding 953 to > security.mac.portacl.rules=uid:53:tcp:53,uid:53:udp:53?
Well, I don't use mac_portacl at all on this host, and there is no sysctl OID security.mac.portacl.rules: # sysctl security.mac.portacl.rules sysctl: unknown oid 'security.mac.portacl.rules' I could probably *make* it work with mac_portacl - however, I would much prefer to get a solution which doesn't need special kernel config etc. Steinar Haug, AS2116
