The --tcp-port option is gone in the just-released dnscrypt-proxy 0.9.4.
-T (alias --tcp-only) should be used to force TCP.
-t is now an alias for --resolver-port, that changes the resolver port, but doesn't force TCP.
OpenDNS supports TCP and UDP on ports 53, 443 and 5353.
When UDP is available (and routers are usually just hijacking port 53), it is preferred over TCP, especially on Windows since the UDP->TCP fallback is pretty slow.
It would be awesome if dnscrypt-winclient could let the user pick the port and the protocol he wants to use.
The --tcp-port option is gone in the just-released dnscrypt-proxy 0.9.4.
-T (alias --tcp-only) should be used to force TCP.
-t is now an alias for --resolver-port, that changes the resolver port, but doesn't force TCP.
OpenDNS supports TCP and UDP on ports 53, 443 and 5353.
When UDP is available (and routers are usually just hijacking port 53), it is preferred over TCP, especially on Windows since the UDP->TCP fallback is pretty slow.
It would be awesome if dnscrypt-winclient could let the user pick the port and the protocol he wants to use.