Hello list,
I'm running bind9 on my local router which is connected to the internet via a
ppp link over my ADSL modem. This link has a static IP assigned, but is not
permanently up. Once a day the connection is dropped for a few seconds and
re-established, which leads to the following problem:
-
-bind named to all interfaces
Hello list,
I'm running bind9 on my local router which is connected to the internet via a
ppp link over my ADSL modem. This link has a static IP assigned, but is not
permanently up. Once a day the connection is dropped for a few seconds and
re-established, which leads
On 12/04/12 15:32, Mihai Moldovan wrote:
Is there any way to tell bind9 to re-evaluate the network situation and bind to
all new interfaces (if allowed, see listen-on)?
I have tried firing up rndc reload and rndc reconfig via the pppd if-up/if-down
scripts, but neither try was successful.
* On 12.04.2012 04:49 PM, Phil Mayers wrote:
rndc reconfig has worked when I've tried it in the past; are you sure you're
running it in the right place? You want to run it in the ip-up / ip-down
scripts, because IP might not be up when LCP is.
Absolutely positive. I'm running rndc reconfig in
* On 12.04.2012 04:44 PM, Todd Snyder wrote:
You can set interface-interval to a low number to make BIND scan for new
interfaces frequently:
Interesting option! Weird thing is, the documentation as per
/usr/share/doc/bind-9.9.0/html/Bv9ARM.ch06.html says:
The server will scan the network
On 12/04/12 16:44, Mihai Moldovan wrote:
Hmm, permission denied while binding to ppp0? Maybe that's because my named is
running as the non-privileged system user named and binding to the privileged
port 53? Makes sense... but... hm. I guess in this case there's no other way but
running named as
It probably has to do with BIND dropping privileges.
If you run BIND with -u so it changes to an unprivileged user, then BIND may
not be able to bind() to new interfaces created on your system.
I use FreeBSD, and my solution was to do this every time I add a new interface:
RESET=`sysctl -e
* On 12.04.2012 09:11 PM, Mark Pettit wrote:
If you run BIND with -u so it changes to an unprivileged user, then BIND
may not be able to bind() to new interfaces created on your system.
[...]
What OS are you using, and what's the command-line you use to launch BIND?
I'm using Linux 3.0.2
* On 12.04.2012 10:01 PM, Mihai Moldovan wrote:
Seems fine... but: I found out my bind was built with --disable-linux-caps and
--disable-threads... enabling the first option sounds promising (second one is
just for my own pleasure.)
Rebuilding... I'll report back once I know whether this
9 matches
Mail list logo
