Real world use. (Test)

[sharif221]

Hi, I was looking for dnstt and found your project it's interesting.
I tried to run it in local mode and it works that's so nice.

But running it across 2 Linux servers. I'm little bit confused.
Can you help me about that.

For dnstt we do a normal subdomain pointed to the server, and a ns record pointed to first Subdomain. Then we do create a tunnel like what is told in in repo.

For this I wanted to ask to see if it's clear how can we do it across 2 servers.

Appreciate your work.

[Mygod]

This should basically works the same as dnstt and acts as a drop-in replacement. You cannot mix and match dnstt + slipstream server/client though since they use different underlying protocols over DNS.

Option A: via public/recursive DNS (typical)

• DNS: create a tunnel subdomain like t.example.com, add t.example.com NS ns.example.com, and an A/AAAA for ns.example.com pointing to the server’s public IP (include glue if needed).
• Server (public host): run slipstream-server with UDP/53 open, e.g. --dns-listen-port 53 --domain t.example.com --target-address <service> --cert --key.
• Client (remote host): run slipstream-client --resolver <recursive>:53 --domain t.example.com --tcp-listen-port 7000 (optional --cert to pin).
• Then connect locally to 127.0.0.1:7000 to reach the server-side target.

Option B: direct authoritative (no recursion)

• Client points straight at your server: --authoritative <server-ip>:53 (can also add --resolver if you want both).
• This bypasses public resolvers and sends directly to your server, so only use it when you control the path and can handle higher QPS.

[Mygod]

I've opened up discussions section for this repo. Future discussions/questions are moved there.