Releases
v0.2.2.1
Compare
Sorry, something went wrong.
No results found
What's New in v0.2.2.1
E2E test: real SOCKS5 CONNECT through the tunnel
E2E now sends a real SOCKS5 CONNECT request through the DNS tunnel
Test path: client → dnstt-client → DNS tunnel → resolver → dnstt-server → reply back
Any SOCKS5 reply (even failure) proves bidirectional tunnel data flow
Previous version only checked if the TCP port opened — that was local and never tested the tunnel
Default e2e timeout bumped to 30s
DNS tunnels at MTU 50 can take 10+ seconds for the Noise handshake alone
Old 15-20s timeout caused false failures on slow tunnel conditions
30s gives enough headroom while keeping scans practical
TUI bug fixed
TUI and CLI now use the same e2e function — identical results
Fixed false positives where all resolvers passed e2e instantly
Removed unused fields
Test URL, Proxy Auth, and curl dependency removed
TUI now only shows: Domain, Pubkey, Cert, Query Size, E2E Timeout
Worker recommendations for e2e
Use --workers 5 to --workers 10 for e2e scans
Higher worker counts overload the dnstt server and cause timeouts
IP list export
_ips.txt file is automatically created alongside JSON output — one IP per line, ready for scripts
dnstt-client binaries included
dnstt-client-linux and dnstt-client.exe with custom -mtu flag support
You can’t perform that action at this time.