Closed entianbucali closed 3 years ago
Maybe it’s a little hacky, but using some special proxy server like clash which supports fake DNS would do your favor.
DNS module included fake DNS support was deprecated in previous version since it should not be tun2socks’ job to handle.
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days
@xjasonlyu , fake DNS should fall within scope. I see the name tun2socks
as transparently redirecting traffic to a SOCKS5 proxy. SOCKS5 supports remote DNS resolution that is impossible without tricks like fake DNS. Adding this feature would make the SOCKS5 part complete.
SOCKS5 supports both local and remote DNS resolving, and I agree FakeDNS is a nice feature to have.
For now, users can use proxy servers like clash/v2ray with fake dns support to enhance the experience.
Clash's TUN mode falls flat on Windows with IP routing enabled (to achieve gateway proxy). Self-loop was monitored on Wireshark. I'm yet to experiment with v2ray.
That said, providing FakeDNS would give this project a huge edge over alternatives. Hope that gives you some motivation for this feature ask :grin:
Using v2ray's fakeDNS works fine when it's on another machine, but when on localhost, tun2socks has the infinite-feedback issue... Is this private IP range '172.16.0.0/15' treated somehow specially w/in tun2socks?!
P.S. W/o FakeDNS, I don't have a problem running it on localhost.
Would it be possible to include the FakeDNS option which would allow for remote DNS use in socks 5 proxies. Thanks