Hi team,
I would like to request that MasterDnsVPN (or similar DNS-tunneling technology) be added to several servers in a test mode. This is to evaluate its effectiveness in bypassing strict censorship, including whitelist-based filtering, in countries like Russia.
The setup requires:
· An external domain (e.g., example.com) and a subdomain (e.g., v.example.com) delegated via an NS record to point to the MasterDnsVPN server.
· An A record for the delegated subdomain (e.g., v.example.com) that points to the server's public IP address.
· The server to have port 53 (TCP and UDP) open and available for the MasterDnsVPN service.
· The server acts as an authoritative DNS nameserver to tunnel TCP traffic via DNS queries.
This test aims to explore an additional circumvention layer for our infrastructure. Please let me know if this is feasible.
Best regards
3 Comments
I understand DNS tunneling will be slow. But this is meant as an emergency fallback — better than losing all access. Even low bandwidth would be enough for Telegram messages and channels when everything else is blocked
I’ve glanced at the code, and it doesn’t look good 🫣
Thanks for taking a look. I’ve double-checked the repository, and it seems the main version is actively developed in Go - the latest commit was just a few days ago, and the project has 6.4k stars with regular releases.
That said, if you still have specific concerns about the code quality or architecture, I’d be happy to hear them. We’re not committed to this exact implementation — the main goal is to test the DNS tunneling approach itself as an emergency fallback. And there are alternatives like DNSTT and SlipStream if this one doesn't work out