Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An option to pass hostnames directly into the parent proxy (with name resolution). #473

Closed
phantomcraft opened this issue May 7, 2020 · 1 comment

Comments

@phantomcraft
Copy link

I want to use this configuration for DNS over SSH, but there is a issue:

nserver 127.0.0.1:10052/tcp
nscache 65536
nscache6 65536
dnspr -i:: -p53
allow *
parent 1000 socks5+ 127.0.0.1 1080
parent 250 tcp anycast.censurfridns.dk 53
parent 250 tcp unicast.censurfridns.dk 53
parent 250 tcp resolver1.dns.watch 53
parent 250 tcp resolver2.dns.watch 53
tcppm -i127.0.0.1 10052 127.0.0.1 11111

3proxy needs to resolve each domain name in tcp parent, with this configuration it fails because there is no usable resolver.

An option to pass the hostnames directly in the tcp section to the parent proxy with name resolution would be interesting in this case because it can lead to IP leaks in the scheme.

Could you implement this feature?

@z3APA3A
Copy link
Collaborator

z3APA3A commented May 7, 2020

3proxy resolves parent IPs on configuration reading, so the simplest solution is to use

allow *
parent 1000 socks5 127.0.0.1 1080
parent 250 tcp anycast.censurfridns.dk 53
parent 250 tcp unicast.censurfridns.dk 53
parent 250 tcp resolver1.dns.watch 53
parent 250 tcp resolver2.dns.watch 53
tcppm -i127.0.0.1 10052 127.0.0.1 11111
flush
nserver 127.0.0.1:10052/tcp
nscache 65536
nscache6 65536
dnspr -i:: -p53

@z3APA3A z3APA3A closed this as completed May 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants