Repository navigation
bind is not able to listen on new interfaces when interfaces change #233
Description
Activity
- added a commit that references this issue
on Mar 17, 2020 - added a commit that references this issue
on Jun 7, 2020 It looks like a full explicit restart of the
pkgsrc/bindsmf service fixes this.- added a commit that references this issue
on Dec 14, 2020 - added 3 commits that reference this issue
on Jun 15, 2021 - added a commit that references this issue
on Dec 18, 2021 - added a commit that references this issue
on Sep 4, 2022 - added a commit that references this issue
on Sep 13, 2022 60 remaining items
- added 4 commits that reference this issue
on May 14, 2026 - added 2 commits that reference this issue
on May 19, 2026 - added 3 commits that reference this issue
on May 22, 2026 - added a commit that references this issue
on Jun 1, 2026 - added a commit that references this issue
on Jun 23, 2026 - added a commit that references this issue
on Aug 2, 2026 - added a commit that references this issue
on Aug 25, 2026 - added a commit that references this issue
on Aug 30, 2026
After the last change to drop permissions on bind, if the interfaces change named won't be able to open a socket.
Using either
rndc scanorrndc reconfigwill result in the following errors written to syslog:I can run
ppriv -s A+net_privaddr $(pgrep -c $(svcs -H -o ctid pkgsrc/bind)), which will allow named to recognize new interfaces and work properly with bothrndc scanandrndc reconfig.