At Wed, 22 Jul 2009 15:56:38 +0200,
Jan Hansen bi...@nhl-data.dk wrote:
As I wrote in the post Master is unreachable (cached), I've switched
to windows server 2003, which currently *seem* to have a positive
effect. I haven't seen the behaviour yet after the switch, but Ian Tait
sees this
At Mon, 20 Jul 2009 16:13:03 +0100,
Ian Tait ia...@thoughtbubble.net wrote:
I see exactly this problem too on windows 2003.
Lookups happen normally after this behaviour occurs though.
Restarting bind cures the problem.
I haven't bothered to debug the issue as yet :-)
We've found a bug that
At Mon, 20 Jul 2009 12:41:24 -0700,
JINMEI Tatuya jin...@isc.org wrote:
We've found a bug that can cause this problem. We're working on a
complete fix to the problem, but a workaround patch copied below may
work for you in the mean time.
Sorry that patch was incorrect. Copying the correct
Chris Buxton wrote:
On Jun 30, 2009, at 6:15 AM, bind9 wrote:
1) skipping zone transfer as master 213.173.250.146#53 (source
0.0.0.0#0) is unreachable
(cached) seem to indicate that the slave has cached a knowledge about
the master being
unreachable. It isn't. I can nslookup on the master
On Jun 30, 2009, at 6:15 AM, bind9 wrote:
1) skipping zone transfer as master 213.173.250.146#53 (source
0.0.0.0#0) is unreachable
(cached) seem to indicate that the slave has cached a knowledge
about the master being
unreachable. It isn't. I can nslookup on the master from the slave
just
Hi list,
I'm currently developing a management application that will run on each of
our nameservers
and take care of domain creation, deletion and updates. Sort of remote
controlling Bind via
commands entered in a database. My setup is one master and three slaves, all
running windows
(2008,
6 matches
Mail list logo
