DNSCheck

DNSCheck was written to Combat a bug in the Windows build of BIND 9. Under load, it appears that BIND 9 simply STOPS answering queries on either or both TCP and/or UDP ports, although the service continues to run, so service recovery does not solve the problem. I tried using other DNS monitoring applications, however most of them monitored the UDP port only. When the BIND`s TCP port would hang, the other applications would not Detect it. Because the TCP port is usually used for zone transfers, this is a critical problem on a primary or secondary DNS. I decided to write my own monitor. This monitor does a simple lookup against both the TCP and UDP ports at a preset interval. If it receives no response, it initiates a reset sequence that stops and restarts the DNS server. Technically this application will work on any Windows-based DNS server, although it was written specifically to combat my BIND 9 problems. Doing Its Thing The DNSCheck installer does not install DNSCheck into your system startup folder by Default, because I hate programs that do that. If you`re administrating BIND, you`re more than capable of putting it there yourself. Once it is running, you can force it to check the DNS status by pressing the Check button. When it checks the DNS, it follows this Process: * Connects to TCP port of server * Queries for specified record * Waits for response * If timeout occurs, shows error, logs error and executes restart routine * If response received, displays response data * If TCP response received OK, sends UDP query * Waits for response * If timeout occurs, shows error, logs error and executes restart routine * If response received, displays response data