ProxymanApp / ProxymanApp/Proxyman
Support server-side DNS resolution when using Socks5h for internal/external proxy
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 7k
- Forks
- 237
- PR merge metrics
- No merged PRs in 30d
Description
Description
Socks5 usually indicates that host name resolution to IP address happens on the client side whereas Socks5h denotes it happens on the server side. It would be great to have support for server-side DNS resolution (AKA "socks5h")
Why this feature/change is important?
Many times, the result of responses differ depending on what IP you connect to (e.g. geographical considerations etc.).
When proxying through Proxyman using an external socks proxy, resolution happens where Proxyman is installed, while all other traffic goes through the socks server is intended, this creates inconsistent results comparing to connecting directly to the Socks server which is confusing an undesirable.
The same is true when Proxyman supports a socks proxy as well (not just for an external proxy).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are mentioned. Start by tracing where Proxyman resolves host names for external SOCKS proxies and for its own SOCKS proxy support. Done means SOCKS5h-style server-side DNS resolution is used consistently, with behavior matching direct connections through the SOCKS server.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100