Has anyone gotten this to work? The TCP/UDP argument here is a red herring, we are calling dig/nslookup from the command line, so its just doing what the script tells it, which is UDP. I can see that it works on the command line just fine:
[andreas@ltm01:Active] config /usr/bin/monitors/dns_test 10.70.24.14 53 www.bigfishgames.com 208.77.152.196
UP
All I can do is assume that the healthcheck is supplying those arguments correctly. Adding some logging I was able to see that the script actually does run against the node:
This dig @${node_ip} ${3}, became this: dig @10.70.24.14 www.bigfishgames.com, which means it got the hostname variable, and inserted that into $1, and also took $3. Now what? It still always marks the nodes down even though the script returns 'UP' (not sure if that is an automatic OK response, but I assume it is)
Any ideas? This seems like it should be a built-in check.