dns resolution behind proxy

Guus Sliepen
Tue, 27 Oct 2015 13:08:36 -0000

On Tue, Oct 27, 2015 at 12:33:35PM +0000, Uwe Werler wrote:

>  I wonder why tinc tries to resolve host names before connection even
> with configured (socks5) proxy which fails behind restrictive firewalls.

You are right that it shouldn't be necessary to do this with SOCKS5.
With SOCKS4, it needs to know the exact address, and then I just used
that for SOCKS5 as well.

> Is there any "workaround"?

The workaround is to do resolve the hostnames yourself and replace the
hostnames in the Address statements with numeric addresses. I'll try to
change tinc so it will allow connections via SOCKS5 even if it cannot
resolve the hostname itself.

--
Met vriendelijke groet / with kind regards,
     Guus Sliepen <guus at tinc-vpn.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL:
<http://www.tinc-vpn.org/pipermail/tinc/attachments/20151027/50e1a0ae/attachment.sig>