I agree @poolwaffle make your pool source code open source on github or such similar open source sites so suspicions such as these can be allayed. you scrypted the re-direct of pool to ghash.io for the 2x promotion before ...
That was not a redirect, but a proxy. All miners were still directed to us, and we relayed information back/forth to GHash. In no way similar to the redirect attack. I don't plan on opensourcing the pool a this time. If I wanted to "steal" hashrates, lets be honest, there would be much easier ways that would be much less obvious (this is a blatent attack).
There are far easier ways for a pool operator to skim off the top without leaving much of a trail for you to follow, and this is especially true for multicoin pools, so if you have reason to doubt the character of a pool operator then you should immediately switch to a different pool. As for wafflepool, I tracked down poolwaffle's true identity (no, I won't share it so don't ever bother asking for a hint), so I know exactly with whom I am dealing, and he has thus far shown to be trustworthy and conscientious. But don't take my word for it; make your own judgments.
Well that worries me slightly if its true. Gotta love the internet

I should have investigated the ip address first before posting the complicated answer. 192.99.25.62 (otherwise known as ns236914.ip-192-99-35.net) appears to be wafflepool's useast stratum server. (Unless a dns hijack currently in progress, which I seriously doubt.)
Before using netstat, I had suggested that you create a table of your expected server host names to ip address mappings so as to be able to properly evaluate the results. Did you do that first?
This is correct. That is one of the new boxes we spooled up during the DDOS. Its been running faster than the last box we had in that location, so it has become the new primary there.