community – Why Connection in dnstt confige isn’t profitable

0
5
community – Why Connection in dnstt confige isn’t profitable


Tried to make use of “dnstt” to avoid censorship. Downloaded the mission:

git clone https://www.bamsoftware.com/git/dnstt.git

A DNS tunnel works by having the tunnel server act as an authoritative resolver for a selected area identify. The recursive resolver within the center acts as a proxy by forwarding queries for that area to the tunnel server. I did these setups for the server:

A   tns.instance.com factors to   203.0.113.2
AAAA    tns.instance.com factors to   2001:db8::2
NS  t.instance.com   is managed by   tns.instance.com

I configured these DNS settings in Cloudflare.
Then began “Tunnel server setup”:

tunnel-server$ cd dnstt/dnstt-server
tunnel-server$ go construct
tunnel-server$ ./dnstt-server -gen-key -privkey-file server.key -pubkey-file server.pub
privkey written to server.key
pubkey  written to server.pub

tunnel-server$ ./dnstt-server -udp :5300 -privkey-file server.key t.instance.com 127.0.0.1:8000

tunnel-server$ sudo iptables -I INPUT -p udp --dport 5300 -j ACCEPT
tunnel-server$ sudo iptables -t nat -I PREROUTING -i eth0 -p udp --dport 53 -j REDIRECT --to-ports 5300
tunnel-server$ sudo ip6tables -I INPUT -p udp --dport 5300 -j ACCEPT
tunnel-server$ sudo ip6tables -t nat -I PREROUTING -i eth0 -p udp --dport 53 -j REDIRECT --to-ports 5300

And eventually:

tunnel-server$ sudo apt set up ncat
tunnel-server$ ncat -l -k -v 127.0.0.1 8000
Ncat: Model 7.70 ( https://nmap.org/ncat )
Ncat: Listening on 127.0.0.1:8000

After that, the Tunnel consumer setup on my native Home windows downloaded the newest DNSTT supply from:
and within the tunnel-client folder ran these:

tunnel-client$ cd dnstt/dnstt-client
tunnel-client$ go construct



./dnstt-client -doh https://unfiltered.adguard-dns.com/dns-query -pubkey-file server.pub t.qawqa.hyperlink 127.0.0.1:7000

It didn’t join, and this was the end result:

uTLS fingerprint iOS 12.1
 efficient MTU 135
 start session 535fb52f
 sendLoop: Put up "https://unfiltered.adguard-dns.com/dns-query": dial tcp 10.10.34.36:443: connectex: A connection try failed as a result of the linked occasion didn't correctly reply after a time frame, or established connection failed as a result of linked host has failed to reply.

I search so much to search out the answer. I don’t perceive why in these traces I see a non-public IP of 10.10.34.36, and I needed to know if this downside could possibly be as a result of I set DNS settings on the Cloudflare web site. If not, how can I repair this error?

LEAVE A REPLY

Please enter your comment!
Please enter your name here