TCP queries fail - BIND 9.5.0 Windows Server 2003

Vinny Abello vinny at
Mon Jun 16 18:30:53 UTC 2008

I recently upgraded from BIND 9.4.2 on Windows Server 2003 to BIND 9.5.0. I was troubleshooting an issue today only to track it down to the fact that my name servers were no longer servicing requests on TCP port 53. UDP queries continued to work without any issues. On one server I noted in the logs:

16-Jun-2008 13:27:30.687 general: .\socket.c:1934: unexpected error:
16-Jun-2008 13:27:30.687 general: socket() failed: Invalid argument

All of my name servers would not respond to TCP queries during my tests. Eventually I restarted the BIND service on one of my name servers and everything came back to life and was working properly. I downgraded back to BIND 9.4.2 for the time being.

This appears to be a bug from what I can tell. When this was happening, if I telnet to port 53, the socket connects, but as soon as any data is sent, the socket is immediately closed. Again, a restart of BIND seemed to fix it. This is on multiple servers as well.

Has anyone else seen this? I'm cc'ing bind-bugs to file a bug report.


More information about the bind-users mailing list