Some questions about Shadowsocks configuration

[mintydev789]

I have a basic shadowsocks-rust server set up with this config file:

{
    "server": "0.0.0.0",
    "server_port": 443,
    "password": "...",
    "method": "...",
    "mode": "tcp_and_udp"
}

I then connect to it from both my Android phone (shadowsocks-android) and Linux computer (shadowsocks-rust) using the server's IP address, port and password. On my phone I also have remote DNS with 8.8.8.8. I have a couple questions that I've not found the answers to anywhere:

1. Is it normal to use the same connection (same password and everything) on every device, or am I supposed to have different configurations for every device? If it's the latter, how do I set that up?
2. How does DNS work over Shadowsocks? Do DNS requests also run through the proxy, being hidden from the ISP? If it doesn't work like that by default, am I supposed to set it up myself with local-dns?
3. What does the remote DNS feature on Android do, and is it possible to set it up on Linux too?
4. Is there a recommended client for iPhone? (I know that's not relevant to this repo, but I don't know where else to ask)
5. Is "mode": "tcp_and_udp" all I need to support both protocols? On the Linux side I use the -U flag with sslocal, and I don't have anything set up on Android, so I'm not sure it supports UDP.
6. Should I bother with IPv6 at all? I haven't done anything with it so far.

[zonyitoo]

1. It's up to you. You could use the "extended configuration format" to setup multiple server instances.

2. DNS resolution depends on what "protocol" interface you have chosen in sslocal. For example, SOCKS5 protocol supports resolving domain names remotely, your clients could send proxy requests with the domain names directly without resolving it locally.

3. I don't know. Maybe it is one of the parameter protocol=dns.

4. Maybe shadowrocket?

5. Yes.

6. Leave it there if you have encountered any issue related to IPv6.

[mintydev789]

Thank you so much for the detailed response! Regarding 1., does each server instance have to work over a different port? If yes, it's probably not suitable for regions where non-HTTP(S) traffic is blocked. If no, does having two separate instances on the same port mean that each client won't be "fighting" to use the same connection and will see better speeds?

[zonyitoo]

Every server instances will start a socket listeners, so they must have different ports.

[catscarlet]

I had a research about DNS so I would like to share it here.

Proxy over Socks5 support both local dns resolve and remote dns resolve

• The local dns resolve is like socks5://YOURPROXYSERVERIP:PORT
• The remote dns resolve is like socks5h://YOURPROXYSERVERIP:PORT

You can try

curl -vL4 --socks5 socks5://YOURPROXYSERVERIP:PORT https://cloudflare.com/

and

curl -vL4 --socks5 socks5://YOURPROXYSERVERIP:PORT https://cloudflare.com/

to see where the domain gets resolved.

The params -vL4 means: verbose, follow redirects, and use ipv4.