System - Preferences - Network Connections - VPN tab - Edit (my VPN
connection) - IPv4 Settings tab. The Method is set to Automatic (VPN).
The DNS Servers and Search Domains are empty (and disabled anyway).
When I am NOT connected via VPN:
$ grep -R 192 /etc/resolvconf/
No results found
When I
I realise that it's not likely the case, but please take a look at your
wired or wireless connection and ensure you haven't set DNS servers
somewhere (in settings in resolvconf (somewhere under /etc/resolvconf),
and in the network-manager connection configuration dialogs).
I'll build a virtual
Eeqmcsq,
Sorry for the delay in getting back to you on this.
AFAIK, the DNS resolver would have continued on to the next DNS server,
*unless* the first answered with NXDOMAIN, which is likely the case when
you try to ask for DNS information on a domain that is available both
from the Internet
Without connecting via VPN, my work domain svl.access-company.com is
still not resolvable by the sbcglobal's DNS servers. And yes, they are
returning NXDOMAIN.
~$ nslookup svl.access-company.com
Server: 68.94.156.1
Address:68.94.156.1#53
** server can't find
Since using my.work-domain.com would be vague and confusing, I have
decided not to hide the actual domain. That way, you will be able to
run tests of your own. The original domain name is svl.access-
company.com. I will continue to hide my work PC name and IP address.
my.work-domain.com is
Since the results were long, I have attached the results in a .txt file.
The only modification I made to the results was to edit out my work
company's name and used my.work-domain.com. Otherwise, the results
were copied directly from the console output to the .txt file.
In analyzing the results,
This is likely due to the fact that my.work-domain.com is resolvable
both by 68.94.156.1 and 68.94.157.1, as well as 192.168.101.5 but
contain different entries depending on the fact that the request is
from the internet or from the VPN.
Could you please try to set your VPN connection to IP
Hi, thanks for reporting this bug and helping improve Ubuntu and
NetworkManager. Unfortunately, we cannot start looking into this bug as
there is not enough information.
Could you provide us with the contents of /etc/resolv.conf as well as
the output of the 'netstat -rn' command when connected to
