Re: 53/TCP port unresponsive

2009-04-08 Thread Mark Andrews
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

RE: 53/TCP port unresponsive

2009-04-08 Thread Deslatte, Curtis
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

Re: 53/TCP port unresponsive

2009-04-03 Thread Mark Andrews
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

Re: 53/TCP port unresponsive

2009-04-03 Thread Chris Buxton
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: