Etienne Dechamps
2015-Feb-01 12:20 UTC
Tincd fails to resolve domain names before it is started name resolution becomes available.
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.
William Kennington
2015-Feb-02 18:14 UTC
Tincd fails to resolve domain names before it is started name resolution becomes available.
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>
Nicolás Reynolds
2015-Feb-02 18:32 UTC
Tincd fails to resolve domain names before it is started name resolution becomes available.
William Kennington <william at wkennington.com> writes:> Agreed. > On Feb 1, 2015 4:21 AM, "Etienne Dechamps" <etienne at edechamps.fr> wrote: > >> 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.+1 we were running a networkmanager dispatcher[^1] for cases like this :) [^1]: https://github.com/fauno/librevpn/blob/develop/lib/skel/50_tincd -- :> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 584 bytes Desc: not available URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20150202/50101d14/attachment.sig>
Apparently Analagous Threads
- Tincd fails to resolve domain names before it is started name resolution becomes available.
- Tincd fails to resolve domain names before it is started name resolution becomes available.
- Tincd fails to resolve domain names before it is started name resolution becomes available.
- Tincd fails to resolve domain names before it is started name resolution becomes available.
- Tincd fails to resolve domain names before it is started name resolution becomes available.