repository·main·Indexed 20 days ago
https://github.com/bugfloyd/dnstt-deployAn automation tool for deploying and managing dnstt DNS tunnel servers on Linux. It simplifies the setup of DNS tunneling, management of systemd services, and configuration of SOCKS or SSH modes. The tool includes an interactive menu for reconfiguring the server, updating the script, and monitoring service logs and status.
During the setup process, you can choose between two tunnel modes:
127.0.0.1:1080.22).The script supports multiple domains by creating separate key pairs for each. However, only one domain configuration can be active at a time because all configurations share port 53 for DNS traffic.
To switch domains:
dnstt-deploy.You can install and start the interactive setup process with a single command. This will download the script to /usr/local/bin/dnstt-deploy and begin the automatic configuration of your dnstt server.
Prerequisites:
sudo privilegesbash <(curl -Ls https://raw.githubusercontent.com/bugfloyd/dnstt-deploy/main/dnstt-deploy.sh)To use the tunnel, download the appropriate client binary from dnstt.network. Once you have your server's public key (found in /etc/dnstt/), use the following command structure to connect:
dnstt-client -udp <DNS_SERVER_IP>:53 -pubkey-file <path_to_pubkey> <tunnel_subdomain> <local_address>:<local_port>Example Connection:
dnstt-client -udp 127.0.0.53:53 -pubkey-file server.pub t.example.com 127.0.0.1:7000Finding your DNS_SERVER_IP:
systemd-resolve --status | grep "DNS Servers"ipconfig /all | findstr /C:"DNS Servers"scutil --dns | grep nameserverdnstt-client -udp DNS_SERVER_IP:53 -pubkey-file server.pub t.example.com 127.0.0.1:7000Before installing dnstt-deploy, you must configure your domain's DNS records to point to your server. This allows DNS traffic to be routed to your tunnel server.
Required Setup Example:
example.com203.0.113.2t.example.comtns.example.comDNS Records to Add:
| Type | Name | Points to |
|---|---|---|
| A | tns.example.com | 203.0.113.2 |
| AAAA | tns.example.com | 2001:db8::2 (optional) |
| NS | t.example.com | tns.example.com |
Note: DNS propagation can take up to 24 hours. Ensure records are active before proceeding with installation.
You can monitor the service using the internal log viewer (Menu option 4) or via manual commands:
5300 and 1080.systemctl status.journalctl with the follow flag.sudo ss -tulnp | grep -E "(5300|1080)"
sudo systemctl status dnstt-server
sudo journalctl -u dnstt-server -f --no-pagersudo ss -tulnp | grep -E "(5300|1080)"
sudo systemctl status dnstt-server
sudo journalctl -u dnstt-server -f --no-pagerOnce installed, run the dnstt-deploy command to access an interactive management menu. This is the primary way to manage the server without manual configuration files.
Menu Options:
Ctrl+C to exit).dnstt-deployAfter installation, run the dnstt-deploy command to access an interactive management menu. The menu provides the following options:
Ctrl+C to exit).dnstt-deploydnstt documentation at https://dnstt.network for specific setup instructions.Before using the script, you must configure your domain's DNS records to point to your server. This allows the DNS tunnel to route traffic through your domain.
Required Setup Example:
example.com203.0.113.22001:db8::2t.example.comtns.example.comDNS Record Table:
| Type | Name | Points To |
|---|---|---|
| A | tns.example.com | 203.0.113.2 |
| AAAA | tns.example.com | 2001:db8::2 (if IPv6 available) |
| NS | t.example.com | tns.example.com |
Note: DNS propagation can take up to 24 hours before the tunnel can be tested.
The dnstt-deploy management menu provides quick access to built-in troubleshooting tools:
MTU (Maximum Transmission Unit) affects the stability and speed of your DNS tunnel. You can adjust this via the dnstt-deploy interactive menu (Option 1).
Recommended MTU Values:
Troubleshooting MTU Errors:
If you see FORMERR: requester payload size X is too small (minimum Y), run dnstt-deploy, select option 1, and enter the suggested MTU value.