Am Dienstag, 18. August 2015, 08:56:43 schrieben Sie:
is sufficient to let 'named' successfully bind to the IP address of the
bge1 interface.
Sounds like a named bug to me then.
hmm,
i use the internal version of bind as the pkgsrc variants without any hassle
- over their correlative rc
On Mon, Aug 17, 2015 at 09:23:58PM -0500, John D. Baker wrote:
This works quite well. In fact,
!sleep 1
is sufficient to let 'named' successfully bind to the IP address of the
bge1 interface.
Sounds like a named bug to me then.
Martin
On Mon, 17 Aug 2015, Eric Haszlakiewicz wrote:
On August 17, 2015 12:17:37 PM EDT, John D. Baker jdba...@mylinuxisp.com
wrote:
I still shouldn't need this. Why is the address not available when
the first attempt to start 'named' is made?
Is your address set by dhcp, or statically? If
On Mon, 17 Aug 2015, John D. Baker wrote:
On Mon, 17 Aug 2015 11:19:54 -0700 Brian Buhrow buh...@nfbcal.org wrote:
hello. what if you put a line like:
!sleep 30
in your /etc/ifconfig.* files to make sure the interfaces are up before
you try to bind to them?
Still a hack, but
On Mon, 17 Aug 2015, John D. Baker wrote:
I tried putting in an @reboot cron job to wait a couple of minutes and
restart 'named', but that seems to have no effect. Perhaps wait longer?
Oops. I discovered an omission in my crontab entry.
But that's just an attempted workaround.
It works
Playing with my @reboot crontab entry, since 'cron' is started last,
the elapsed time since 'named' was first started is enough and no
additional delay is needed. As such, it simply restarts 'named' and
then external queries are received/answered.
I still shouldn't need this. Why is the address
I don't know why your bge1 isn't available yet. Maybe look in your dmesg
for more details about it and share here.
As another workaround, maybe use sleep with some amount of seconds in
your named startup script to delay its startup to make sure your bge1 is
up.
(By the way, named has
On August 17, 2015 12:17:37 PM EDT, John D. Baker jdba...@mylinuxisp.com
wrote:
Playing with my @reboot crontab entry, since 'cron' is started last,
the elapsed time since 'named' was first started is enough and no
additional delay is needed. As such, it simply restarts 'named' and
then external
John D. Baker wrote:
Playing with my @reboot crontab entry, since 'cron' is started last,
the elapsed time since 'named' was first started is enough and no
additional delay is needed. As such, it simply restarts 'named' and
then external queries are received/answered.
I still shouldn't
hello. what if you put a line like:
!sleep 30
in your /etc/ifconfig.* files to make sure the interfaces are up before
you try to bind to them?
Still a hack, but not as bad as the cron job.
-Brian
On Aug 17, 10:35am, John D. Baker wrote:
} Subject: Re: named unable to bind to address
/05/02/msg027329.html
--
Andreas Gustafsson, g...@gson.org
From r...@reedmedia.net Mon Aug 17 11:57:29 2015
Date: Mon, 17 Aug 2015 11:54:41 -0500 (CDT)
From: Jeremy C. Reed r...@reedmedia.net
To: John D. Baker jdba...@mylinuxisp.com
Cc: current-users@NetBSD.org
Subject: Re: named unable to bind
I've been working on a machine that's been running -current for a while
now. It seems that after the latest BIND updates, 'named' has trouble
binding to an external IP address at which to listen for queries when
starting up after a reboot.
$ uname -a
NetBSD brenowin.reltuk.net 7.99.21 NetBSD
12 matches
Mail list logo
