MasterDnsVPN
github.com/masterking32/masterdnsvpn- Category
- Cybersecurity
- Rank
- No. 491Tools index
Previous survey · No. 486 ·
- Pricing
- Open Source
- Platform
- cli · desktop
- Type
- TOOL
- Builder
- masterking32
- GitHub
- 7.0k stars
- Latest release
- v2026.06.13.234407-7de2476
- Date
About
Advanced DNS tunneling VPN that bypasses internet censorship by disguising traffic as normal DNS queries. Optimized for stability in harsh network conditions with multi-resolver support and adaptive routing.
What it does
MasterDnsVPN is a research-oriented client and server system that carries TCP connections through DNS exchanges. You delegate a subdomain to the server, then connect applications through local SOCKS4, SOCKS5, or TCP forwarding while its custom reliable transport handles fragmentation, acknowledgments, retries, and path failures.
Why it's ranked here
The implementation backs its harsh-network focus with concrete machinery: MTU probing, resolver health monitoring, automatic failover, packet duplication, adaptive retransmission, and prioritized queues. That depth makes it technically interesting, though the performance comparisons and blackout claims come from the project itself rather than independently presented evidence.
What's good
It treats unreliable DNS paths as an engineering problem, not a transport assumption. Upload and download MTU tests identify weak resolvers, health checks can disable and later reconsider them, and adaptive retransmission tracks timing separately for data and control traffic. Compression, request packing, caching, and configurable encryption provide useful operational choices.
Tradeoffs
Setup requires a public server, domain control, and correct subdomain delegation. Advanced tuning exposes many interacting limits and timeouts. Duplication improves delivery probability by consuming more traffic. XOR is explicitly the lower-security encryption option. The authors classify the project as educational and research-oriented, warn that production use may disrupt networks, and provide no warranty.
How to use it well
Use it for research or carefully controlled TCP access where ordinary routes are filtered or unstable. Start with its SOCKS proxy mode, test available resolvers, and let MTU discovery establish safe packet sizes before tuning. Pair TCP forwarding with another TCP-based protocol when needed. It does not provide a general transport for non-TCP application traffic.
Technical notes+
The Go module in go.mod targets Go 1.25.0 and declares TOML, compression, crypto, and system dependencies. internal/arq/arq.go implements the reliable stream overlay with send and receive buffers, adaptive data and control RTO state, ACK and NACK handling, retransmission workers, backpressure, and explicit stream lifecycle states. internal/client/mtu.go probes upload and download limits, filters low-MTU resolver outliers, and runs resolver health rechecks. internal/mlq/mlq.go provides a synchronized six-level priority queue with keyed removal and atomic size tracking. Packet types are centralized in internal/enums/dns.go. Configuration in internal/config/server.go supports TOML, JSON fallback, base64-encoded JSON, and overrides. Tests are present in internal/arq/arq_test.go and internal/mlq/mlq_test.go.
Observed
- Primary language
- Go, with the README also identifying a legacy Python version.
- Packaging
- Go module named masterdnsvpn-go, targeting Go 1.25.0.
- Interfaces
- Client-server application with SOCKS4, SOCKS5, and TCP forwarding modes.
- Configuration
- Server configuration supports TOML, JSON fallback, base64-encoded JSON, and overrides.
- Dependencies
- Uses BurntSushi TOML, klauspost compression, LZ4, Go crypto, and Go system packages.
- Test structure
- Repository text includes Go tests for the reliable transport overlay and multi-level priority queue.
Read from README.MD, go.mod, internal/arq/arq.go, internal/mlq/mlq.go, internal/enums/dns.go, internal/client/mtu.go, internal/arq/arq_test.go, internal/mlq/mlq_test.go, internal/config/server.go, internal/client/client.go.
What it can do
Tunnel TCP traffic through DNS queries
TCP network traffic → DNS queries containing encapsulated traffic
Bypass internet censorship and firewalls
Blocked network connections → Unblocked access to restricted content
Disguise VPN traffic as normal DNS requests
VPN network packets → DNS queries that appear legitimate to network monitors
Adapt routing based on network conditions
Network performance metrics and connection quality → Optimized routing paths for stable connectivity
Switch between multiple DNS resolvers
DNS resolver endpoints and availability status → Active connection through best available resolver
Maintain connection stability in poor network conditions
Unreliable or monitored network connections → Stable data transmission despite network interference
Tags
Tech Stack
Media
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.