In article <20170415005323.ga17...@falu.nl>, Rhialto <rhia...@falu.nl> wrote: >-=-=-=-=-=- > >On Fri 14 Apr 2017 at 19:20:13 -0500, Jeremy C. Reed wrote: >> On Sat, 15 Apr 2017, Rhialto wrote: >> >> > and these errors about re1 (my external interface) kept going all the >> > time. When I noticed them and restarted named, they went away. >> > >> > Why does named not succeed in using the interface when it gets an >> > address again? What to do about it? I noticed partly because my dns data >> > seemed to have dropped out of caching name servers elsewhere. >> >> See the BIND docs about automatic-interface-scan (enabled by default) >> and interface-interval (defaults to 60 minutes). > >Ok, that it scans for interfaces is nice. I had noticed that already. >But why does it get "permission denied" errors? A google search >indicated that "the usual" cause for this seems to be that multiple >instances of bind are running, but that isn't the case here. At least >not when I looked. > >Maybe it is a simple matter where it has dropped permissions by the time >it needs to re-bind to re1, or something like that? > >I also noticed the error seems to mention IPv4 only. I am not sure if it >managed to bind an IPv6 address on the same interface (and now it is too >late, unfortunately). > >In case it makes a difference, I am running bind in the chroot as >provided by named_chrootdir="/var/chroot/named". And I have 2 views, an >internal and an external one.
It is not root anymore so rescaning interfaces fails. We should fix it. christos
