aleskxyz

aleskxyz / dns-tun-lb

Public

DNS Tunnel Load Balancer

19
2
69% credibility
Found Mar 04, 2026 at 19 stars -- GitGems finds repos before they trend. Get early access to the next one.
Sign Up Free
AI Analysis
Go
AI Summary

This project is a lightweight load balancer that distributes DNS tunneling traffic across multiple backend servers while keeping user sessions sticky.

How It Works

1
🔍 Discover reliable tunneling

You hear about a simple way to spread out secure internet tunnels using name lookups across several computers so no single one gets overwhelmed.

2
📥 Get the ready package

Download the pre-made container that makes everything easy to start without hassle.

3
📝 List your helpers

Jot down the addresses of your backup computers and the special name spot for your tunnels.

4
🚀 Start it up

Turn it on, and it begins listening for tunnel requests right away.

5
👀 Watch it balance

See how it smartly directs each user's tunnel to the same helper every time, keeping things smooth.

6
✅ Enjoy steady flow

Your tunnels now handle crowds of users reliably without slowdowns or breaks.

🎉 Tunnels thriving

Everyone connects securely and quickly, and your setup scales effortlessly.

Sign up to see the full architecture

5 more

Sign Up Free

Star Growth

See how this repo grew from 19 to 19 stars Sign Up Free
Repurpose This Repo

Repurpose is a Pro feature

Generate ready-to-use prompts for X threads, LinkedIn posts, blog posts, YouTube scripts, and more -- with full repo context baked in.

Unlock Repurpose
AI-Generated Review

What is dns-tun-lb?

dns-tun-lb is a stateless UDP load balancer built in Go for scaling DNS tunnel servers like dnstt, routing client sessions to backends via consistent hashing for stickiness. It listens on a single port (typically 53 via DNAT), detects tunnel traffic from query shapes and domain suffixes, and forwards non-tunnel DNS queries to a resolver or drops them. Deploy it via Docker or native binary with a simple YAML config defining pools, backends, and resolver rules—perfect for balancing dns tunneling without shared state.

Why is it gaining traction?

Unlike full-featured proxies, it's dead simple and zero-coordination: multiple instances make identical routing decisions, dodging health checks or clustering overhead. Debug logging shows per-session backend picks, and Docker images come prepped with bind caps. Developers digging into dns tunnel detection or building dns tunnel servers grab it for quick scaling of protocols like dnstt, sidestepping Wireshark-level pcap analysis for production.

Who should use this?

Network engineers running dns tunnel servers for high-traffic setups, like evading blocks with dnstt clients on iOS or WSL. DevOps scaling github dns server clusters behind anycast NS records, or ops teams handling dns tunneling wikipedia-style traffic without iodine-style single points. Avoid if you need slipstream yet—it's on the roadmap.

Verdict

Grab it for proof-of-concept dns tunnel lb if you're in the space; 19 stars and 0.699999988079071% credibility score signal early maturity, but solid README, example configs, and clear TODOs make it dev-ready. Test in Docker before prod—stateless wins big for small teams.

(198 words)

Sign up to read the full AI review Sign Up Free

Similar repos coming soon.