It's just a suggestion, but research the raw events reporting system. If you really want to get a /whois type response, you could set it up so that sometimes a script can make a call, go on and do other things, and then when it gets a /whois from the server with the requested information it automatically deals with the information however you are particularly interested in doing that.
I myself have updated the /dns function so that it is capable of simply *wonderful* things, like opening its own window and then making sure there aren't two, three, four IP adresses that correspond with someone's domain name, then listing all of them.
Although that reminds me, could the /DNS command, whether it's being used for server lookup or manually be *updated* a little so that it doesn't stubbornly hammer at the same address and actually *lists* multiple ones when you query? I've found that in situations where the redirect on a network (irc.dal.net for instance) is pointing to several servers, and the one at the top is down, it would often function much better if the second address were specified instead of the first. Or third. Or fourth, or whichever. So if DNS could list them all, and then the server address lookup could select randomly from the list instead of hammering at the first one, that would be *EXTREMELY* appreciated.
