yarrick
commented
3 months ago Thanks for the comment. You can do it by giving the iodined server as the nameserver for the client to use as the optional first argument.
Sending the queries directly does not help that much though if the packets still need to use the DNS protocol. The raw mode does direct traffic as well as the next optimization, sending the data packets with a minimal header (like a normal vpn app but on port 53) directly to the server if possible. As expected this leads to performance similar to other tunneling protocols.
Just stumbled across this project and thought it was really cool! The only downside seems to be the throughput, but I understand the reasoning behind it (not wanting to affect intermediate DNS servers that we don't own). I wonder, though, would it be possible to speed up the throughput of the DNS tunnel by setting the client's DNS resolver to be the server running iodined?
In my mind, it would be some sort of additional flag where we set a static IP (e.g.
--iodined X.X.X.X). If there was a way to attempt this with the client, we could send the DNS packets directly to our server as fast as we want.I'm probably making a lot of incorrect assumptions here because I am super new to this project and idea, but I thought I'd throw the thought out there and see what others think.