Setting "try-tcp-refresh no;" would have most probably fixed
it.
> This was 9.5.0-P1, BTW.
> =20
> =20
> Thanks,
> CJD
> =20
>
> Curt Deslatte
> curtis.desla...@acs-inc.com
>
> =20
>
>
> -----Original Message-
> From: bind-use
Deslatte
curtis.desla...@acs-inc.com
-Original Message-
From: bind-users-boun...@lists.isc.org
[mailto:bind-users-boun...@lists.isc.org] On Behalf Of Mark Andrews
Sent: Friday, April 03, 2009 1:08 PM
To: Chris Buxton
Cc: bind-users@lists.isc.org; bind-work...@lists.isc.org
Subject
There is no such version as BIND 9.5P1.
There are both BIND 9.5.0-P1 and BIND 9.5.1-P1.
If Mark is using BIND 9.5.0-P1 then I would recommend upgrading.
Mark
In message , Chris Buxton
writes:
> We've seen this repeatedly with our customers, usually evidenced by
We've seen this repeatedly with our customers, usually evidenced by
slaves that stop refreshing and eventually expire the zone. It seems
to happen most on Mac OS X and Solaris, and less often (or perhaps
never) on Linux.
named just stops listening on the TCP port. If you execute "lsof -i:
Greetings.
We have 4 masters (rsync'd together) and a pair of load balancers each of which
distributes queries to any of the 4. On the masters, we run Solaris 10 with
BIND 9.5P1. Recently, one of the 4 stopped using TCP on port 53, but UDP
traffic continued unaffected. What would cause the T
5 matches
Mail list logo