The solution with pushing all domains is just not convenient, when
accessing hundreds of domains through the VPN. Why having DNSMASQ on all
hosts in the first place?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
I can confirm this behavior:
- Connected with VPN, resolv.conf is proper
- Connected with network manager vpnc, resolv.conf does not update
- Connected using vpnc-connect command line updates resolv.conf properly
This is a big problem, as this affects "less experienced" users that are
not confid
And guess what; This server side tweak fixed a few mobile clients that
use our VPN that would not get DNS resolution, likely using similar
domain based routing like dnsmasq.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Wow, it took me a while to find this post. For OpenVPN users
specifically, there should be some sort of release note addition that
explains that having the DNS push is no longer enough to have VPN dns
resolution work.
i.e. Your OpenVPN DNS will no longer resolve resolve if you do not have
the dh
So closing this bug for both tasks as Invalid; since we're covering the
vpnc issues separately in bug 954747.
** Changed in: network-manager-vpnc (Ubuntu)
Status: Confirmed => Invalid
** Changed in: network-manager-openvpn (Ubuntu)
Status: Confirmed => Invalid
--
You received this
Hi Marton,
I can confirm this.
You can also configure the dns and searchdomain manually in the client, if you
have no access to the vpn server.
After that, address resolution works vor names and ips again, even if the vpn
is only used for adresses in the vpn network.
--
You received this bug
I experienced the same issue. After sucessfull OpenVPN connection
/var/run/nm-dns-dnsmasq.conf contains the following:
server=/10.in-addr.arpa/10.1.106.7
server=192.168.0.1
server=192.168.3.2
This 10.in-addr.arpa prefix appears only when "Use this connection only for
resources on its network" ch
It turns out that for my case, it was a misconfiguration on the VPN.
Once the correct domain was set, resolution started working.
** No longer affects: network-manager-openconnect (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
In that last attachment, it works (I think) because the 42.11 name
server was used first without being qualified by xxx.domain1.com, so it
was used to resolve everything. (I think that it would fall back to the
other servers if it could not resolve, but I know not how that magic
works.)
--
You re
** Attachment added: "Older (11.10) VPN Connection syslog (not debug)"
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/924013/+attachment/2858564/+files/11.10%20VPN%20Connection%20Log.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
I checked some non-debug log messages from before I upgraded to 12.04,
and they only show the one domain, but resolution was working fine then.
I tried getting the debug logs for the nm-openconnect-service, but they
did not look useful. I will try again.
--
You received this bug notification bec
This is all I get:
~# /usr/lib/NetworkManager/nm-openconnect-service --debug
** WARNING **: property 'cookie-flags' unknown
** WARNING **: property 'certsigs-flags' unknown
** WARNING **: property 'autoconnect-flags' unknown
** WARNING **: property 'gateway-flags' unknown
** WARNING **: prop
Right. Notice how you get only one of them in the debugging logs you've
attached?
Mar 10 11:24:09 vicap-21299 NetworkManager[1025]: DNS Domain:
'xxx.domain1.com'
In the suggested debugging howto
(http://live.gnome.org/NetworkManager/Debugging) for your VPN, there
should be another set of logs wh
The domain is set to xxx.domain1.com (scrubbed name), domain2.com (also
scrubbed) should also be set as a search domain, but it is not.
cat /run/nm-dns-dnsmasq.conf:
server=/xxx.domain1.com/192.168.42.11
server=/98.168.192.in-addr.arpa/192.168.42.11
server=/100.168.192.in-addr.arpa/192.168.42.11
The "use this connection" change really shouldn't be affecting much.
I can confirm this on n-m-vpnc as well; though it's unclear there yet
whether the extra domains (in split-domain config on my Cisco ASA) are
actually supported by vpnc. I'm adding a task to get this fixed.
Fixing this in openvpn
Please provide full logs from /var/log/syslog after reproducing the
problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924013
Title:
VPN DNS only works for IP, not names
To manage notifications
** Also affects: network-manager-openconnect (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924013
Title:
VPN DNS only works for IP, not names
To
My vpn pushes two search domains down. Only one is showing in /run/nm-
dns-dnsmasq.conf. All the reverse dns entries are there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924013
Title:
VPN DNS
jck's workaround from comment 5 does not work in my case. The first
search domain is still there, the second is not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924013
Title:
VPN DNS only works f
Workaround: If I disable the option option to use the vpn connection
only for resources in the vpn network in the routing options, everything
works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924013
Reverse resolving ip's works.
Resolving the name dont' works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924013
Title:
VPN DNS only works for IP, not names
To manage notifications about this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager-openvpn (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/9240
Just updated to 12.04 beta this. morning. VPN DNS resolving is broken.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924013
Title:
VPN DNS only works for IP, not names
To manage notifications about
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924013
Title:
VPN DNS only works for IP, not names
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manag
24 matches
Mail list logo
