Guides
DNS & Browsers
Point your browser at the relay and stop Firefox from leaking DNS.
Point Firefox/Chrome at "Use system proxy settings" to follow socksy on
GNOME or KDE. With the env backend there is no system proxy, so start
browsers from a shell that has sourced ~/.config/socksy/env.sh.
DNS posture with the relay:
| Client | DNS resolution | Leak? |
|---|---|---|
CLI via socks5h:// | at the exit (remote) | no |
| System-proxy apps (GNOME/KDE) | hostname passed to SOCKS | no |
| Chrome + SOCKS5 | remote by default | no |
| Firefox | local, unless configured | yes |
So socksy dns on flips Firefox's network.proxy.socks_remote_dns in every
profile (restart Firefox to apply); socksy dns off reverts it. Everything
else already resolves at the exit.
socksy dns on|off|reset|status # reset removes socksy's block from user.jsLAN bypass
socksy manages the no-proxy (ignore-hosts) list so local and private traffic never goes through the relay:
socksy bypass list|add|rm|resetThe default list covers loopback, .local, and the RFC1918 private ranges —
see the ignore_hosts key in the config file.