CLOSE_WAIT not closing in Bind 9.2.0
D.M.
hmprimerib at hotmail.com
Mon Jan 21 22:36:50 UTC 2002
> In article <a2hrqo$odt at pub3.rc.vix.com>, D.M. <hmprimerib at hotmail.com> wrote:
> >We have multiple lingering CLOSE_WAIT's on our bind 9.2.0 server which
> >means the client sent a FIN, but the server hasn't closed its socket
> >yet. This leads me to believe this is possibly a problem with the
> >server. Anyone know how to control these? make sure they die after a
> >set time?
>
> Since DNS clients normally use UDP, not TCP, are you sure that these
> connections are related to BIND? Normally, TCP is only used for zone
> transfers. Are the connections going to port 53 on the server?
Thanks for the reply.
Yes, netstat says port 53. It's all TCP stuff.
# netstat -an |grep WAIT
Local Address Remote Address Swind Send-Q Rwind Recv-Q State
-------------------- -------------------- ----- ------ ----- ------ -------
192.168.30.2.53 210.156.196.31.1260 32120 0 24583 0 CLOSE_WAIT
192.168.25.2.53 130.125.1.10.1397 17520 0 24774 0 CLOSE_WAIT
192.168.30.2.53 209.192.164.70.59595 17520 0 24774 0 CLOSE_WAIT
192.168.25.2.53 216.37.1.19.1269 32120 0 24570 0 CLOSE_WAIT
192.168.30.2.53 62.232.35.13.4088 17520 0 24777 0 CLOSE_WAIT
192.168.30.2.53 204.201.58.9.59167 17520 0 24774 0 CLOSE_WAIT
Any thoughts?
More information about the bind-users
mailing list