Openconnect resolution issue

[Nikos Mavrogiannopoulos]

On Sat, Sep 19, 2015 at 1:14 AM, Ronen Leibovici <rleibovici at gmail.com> wrote:
> Good day,
> Here is the situation.
> When working on my RHEL6 host, I use AT&T dialer to connect to my
> companies intranet.
> When doing so, my resolv.conf file is updated to include the
> nameservers of my company.
> Then, I use openconnect in order to connect to our customer. This also
> works and the resolv.conf file is edited by VPNC to include the
> nameservers of our customer.
> The problem lies in the fact that if i try to perform any resolution,
> it fails because, for some reason, my O/S has now been told that
> recursion is not allowed and only the first name server in my
> resolv.conf file is queried.

I don't believe there is such thing as putting the OS at recursion or not.

>
> ex:
> [root at oc8146477318 ~]# nslookup w3.ibm.com
> Server: 96.4.1.83
> Address: 96.4.1.83#53
>
> ** server can't find w3.ibm.com: NXDOMAIN
> ex:
>    [root at oc8146477318 cscotun0]# nslookup w3.ibm.com
> ;; Got recursion not available from 96.4.1.83, trying next server
> ;; Got recursion not available from 96.130.126.21, trying next server
> Server: 9.0.148.50
> Address: 9.0.148.50#53

The decision on whether to fallthrough or not is part of nslookup, not
of the system. I'd suggest to check your resolv.conf for differences
and use nslookup in debug mode.

regards,
Nikos