[Bug 396387] Re: Unable to resolve VPN names AND connect to the Internet

2011-08-05 Thread Mathieu Trudel-Lapierre
Unfortunately, this appears to be expected and wanted behavior. The reason for this is that you can only go two different ways: either the VPN's nameserver is set *above* the local nameserver so that VPN connections will work automatically once connected to (the issue the original reporter was refe

[Bug 396387] Re: Unable to resolve VPN names AND connect to the Internet

2011-04-03 Thread David Harper
Following some of the steps above, when connected to my domain via VPN, resolv.conf has: domain my-domain.com search my-domain.com google.com nameserver [my-dns-ip] nameserver 8.8.8.8 nameserver 8.8.4.4 and I also have the "Routes - Only traffic" box ticked. Under this configuration, the outside

[Bug 396387] Re: Unable to resolve VPN names AND connect to the Internet

2011-04-03 Thread David Harper
Hi, Just updated to clean Natty Beta and am coming across this issue. Was working for me fine previously. More than willing to provide files and traces if you tell me what you want. Thanks, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubu

[Bug 396387] Re: Unable to resolve VPN names AND connect to the Internet

2010-12-10 Thread Joseph Garvin
Gah, I switched this from "expired" by accident (have a similar but different problem) and launchpad doesn't give me the option to change it back. Feel free to revert :p -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.laun

[Bug 396387] Re: Unable to resolve VPN names AND connect to the Internet

2010-12-10 Thread Joseph Garvin
** Changed in: network-manager-vpnc (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/396387 Title: Unable to resolve VPN names AND connect to the Internet -- ub

[Bug 396387] Re: Unable to resolve VPN names AND connect to the Internet

2010-11-26 Thread Launchpad Bug Tracker
[Expired for network-manager-vpnc (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager-vpnc (Ubuntu) Status: Incomplete => Expired -- Unable to resolve VPN names AND connect to the Internet https://bugs.launchpad.net/bugs/396387 You received this bug no

[Bug 396387] Re: Unable to resolve VPN names AND connect to the Internet

2009-11-15 Thread Eeqmcsq
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/ When I am connected

[Bug 396387] Re: Unable to resolve VPN names AND connect to the Internet

2009-11-11 Thread Matt Trudel
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 mac

[Bug 396387] Re: Unable to resolve VPN names AND connect to the Internet

2009-11-08 Thread Eeqmcsq
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 svl.access-company.c

[Bug 396387] Re: Unable to resolve VPN names AND connect to the Internet

2009-11-08 Thread Matt Trudel
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 and

[Bug 396387] Re: Unable to resolve VPN names AND connect to the Internet

2009-09-20 Thread Eeqmcsq
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 re

[Bug 396387] Re: Unable to resolve VPN names AND connect to the Internet

2009-09-19 Thread Matt Trudel
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 a

[Bug 396387] Re: Unable to resolve VPN names AND connect to the Internet

2009-09-19 Thread Eeqmcsq
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,

[Bug 396387] Re: Unable to resolve VPN names AND connect to the Internet

2009-09-18 Thread Matt Trudel
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