Tincd fails to resolve domain names before it is started name resolution becomes available.

[William Kennington]

Agreed.
On Feb 1, 2015 4:21 AM, "Etienne Dechamps" <etienne at edechamps.fr> wrote:

> On Sun, Feb 1, 2015 at 11:19 AM, Guus Sliepen <guus at tinc-vpn.org> wrote:
> > On Sun, Feb 01, 2015 at 04:08:47PM +0900, crocket wrote:
> >
> >> If tincd is started before name resolution comes up, it keeps failing
> >> for ever to resolve domain names in Address= host configuration
> >> variable after name resolution becomes possible.
> >>
> >> I think tincd should succeed in resolving domain names after name
> >> resolution becomes available.
> >
> > The problem is when /etc/resolv.conf is changed while a program is
> > running, glibc doesn't automatically notice this. Since tinc 1.0.25 and
> > 1.1pre11, if you send tincd the ALRM signal, it will force glibc to
> > reload /etc/resolv.conf.
>
> Considering how cheap that operation seems to be, would it make sense
> to call res_init() every time tinc retries a metaconnection? It's not
> doing that very often anyway... and it would solve the OP's problem.
> _______________________________________________
> tinc mailing list
> tinc at tinc-vpn.org
> http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20150202/3223a910/attachment.html>