On 01/06/15 16:56, 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 > Answering my own post. It looks like this has been submitted as a bug since last year. Apparently openvpn doesn't re-check the contents of resolv.conf - and keeps on trying to resolve the hostname using whatever dns server was in resolv.conf before the connection was established. As luck would have it, a patch was submitted only 26 hours ago, which should cure it. Full bug report here:
https://community.openvpn.net/openvpn/ticket/523 ------------------------------------------------------------------------------ _______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
