shadowsocks / shadowsocks/shadowsocks-org
[SIP009] Handling remote DNS in ss-server in a backwards compatible way
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1k
- Forks
- 694
- PR merge metrics
- No merged PRs in 30d
Description
I propose that if shadowsocks server receives a (TCP/UDP) connection to 0.0.0.0:53 or [::]:53, it should redirect the connection to current default DNS resolver (on Linux, this might be handled by res_query). This is useful for socksifier VPNs as well as resolving ACL rules.
This is a backwards compatible change and should not break anything. (maybe this is an SIP?)
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
Start with the ss-server entry point and review the 23-comment discussion before coding; the issue names no files or tests. Clarify how TCP and UDP requests to 0.0.0.0:53 and [::]:53 should use the current default DNS resolver while preserving existing behavior, then define tests covering both protocols and address families.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100