Hi, On Mon, Jun 01, 2015 at 04:56:59PM +0100, Sebastian Arcus wrote: > Could anyone throw some light on this please. I've noticed this problem > for a long time. If openvpn on the client starts before Internet > connectivity, and the 'remote' directive uses a host name, not an IP > address, when the connectivity is restored openvpn continues to fail in > resolving the hostname. The following errors are recorded in the log > again and again: > > RESOLVE: Cannot resolve host address: my.openvpn.server.hostname: System > error > RESOLVE: Cannot resolve host address: my.openvpn.server.hostname: System > error > RESOLVE: Cannot resolve host address: my.openvpn.server.hostname: System > error
I assume this is a variant of bug #523 in trac, to be fixed in 2.3.7, to be released later this week. (See https://community.openvpn.net/openvpn/ticket/523 for a detailed description what happens - though usually the scenario is slightly different, with /etc/resolv.conf being modified and not automatically re-read on retry) Out of curiousity: what operating system is this on? I tried to reproduce this on Linux, and it did not work out, because at least on Gentoo, glibc will notice "changes" on its own... gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany g...@greenie.muc.de fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
pgpSyKf1uKlec.pgp
Description: PGP signature
------------------------------------------------------------------------------
_______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
