Thanks to all of you for your replies.

The consensus seems to be that the documentation is correct, and that if
OpenVPN behaves differently then that is a bug.

I'll try to get the user's configs/logs, or try to generate some test cases
that show this myself (and include a 2.1... test case to see if this
behavior was introduced in 2.2) and post them on this thread.

On Mon, Oct 22, 2012 at 6:11 AM, David Sommerseth <
openvpn.l...@topphemmelig.net> wrote:

> On 22/10/12 10:48, Gert Doering wrote:
> > Hi Jonathan,
> >
> > On Sun, Oct 21, 2012 at 06:40:08PM -0400, Jonathan K. Bullard wrote:
> >> A Tunnelblick user has reported odd behavior with name resolution
> failures.
> >> I can't tell if it is a bug in OpenVPN, a bug in the documentation, or
> >> something else. The behavior is apparently the same in OpenVPN 2.2.1 and
> >> 2.3alpha1.
> > [..]
> >> Any ideas if this is a program bug, a documentation bug, or something
> else,
> >> for example, a problem that only occurs on OS X?
> >
> > "One of those" :-) - I don't know yet, and haven't looked into the code
> yet
> > (will do ASAP).
> >
> > The resolver code has been changed for 2.2 (getting rid of the old
> > randomization stuff), so it might be a bug introduced there, or a much
> > older bug that nobody ever noticed.
> >
> > Do you have an OpenVPN log that shows this behaviour?  Might help in
> > digging down to it...
>
> A client config file would help in addition.  I'm also wondering if
> connection profiles are used ... that is, more --remote options or
> <connection> blocks.
>
> Otherwise, I would not be surprised if there are some corner case here
> appearing, which surfaced more easily when the resolving code was
> re-written (as Gert mentioned).
>
> This resolver_retry_second option is only used in socket.c AFAICT, which
> most of us try to avoid looking too hard on, to avoid eye cancer and/or
> loosing our sanity ;-)  But there's work in progress on cleaning up that
> one, unfortunately that will take some time.  But we'll try to hunt down
> this which looks like an openvpn bug to me.
>
>
> kind regards,
>
> David Sommerseth
>
>

Reply via email to