[Expired for nss-mdns (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nss-mdns (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1086
@charleshb: This isn't the same bug as #1086459 which involves mdns
returning NOTFOUND before dns is tried. Whereas you already have dns
before mdns on the "hosts" line in your /etc/nsswitch.conf.
You may be suffering from bug #1003842. Please comment out "dns=dnsmasq"
in /etc/NetworkManager/Netwo
I'm suffering from the same bug. First nslookup is w/o VPN, name
resolution works just fine. Once I'm connected to vpn clemson.edu names
resolve but other domains do not resolve. I did a second set of
nslookups at the end of this to show the last.
[chbaker@reacher:~]$ nslookup slashdot.org
@Lothar: Can you please provide the same information that others were
asked for earlier in this bug log (bug #1086459)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1086459
Title:
Name resolution o
Oh, and I forgot to mention it worked flawless until about a month ago
(before I went into Christmas vacation)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1086459
Title:
Name resolution over VPN f
I'm having the same problem that DNS resolution stops working after a VPN
connection (Cisco VPN) is established.
However changing /etc/nsswitch.conf like in comment #20 does NOT work for me. I
still get *unknown host* messages from ping.
I'm running LTS 12.04
$ cat /etc/lsb-release
DISTRIB_ID=
The new issue I'm facing seems to be exactly this:
http://ubuntuforums.org/showthread.php?t=1692353
A problem that's been making VPN usage miserable in Ubuntu for some time
:(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
This is likely unrelated, but any traffic sent over the VPN connection
sputters and dies after about 5-10 seconds. For the initial 5-10
seconds, Internet and local names resolve without issue. After this, all
name resolving & traffic fails, and the VPN eventually gives a "VPN
Connection Failed" mes
** Package changed: resolvconf (Ubuntu) => nss-mdns (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1086459
Title:
Name resolution over VPN fails; mdns4_minimal returns NOTFOUND
To manage no
Here's a more up-to-date link than the one I gave in comment #22.
https://help.ubuntu.com/12.10/serverguide/network-configuration.html
The relevant passage hasn't changed: it still says "if you prefer to use
legacy Unicast DNS versus Multicast DNS, you can change the string in
/etc/nsswitch.c
This looks like bug #140663 with the twist that it only happens when
connected via VPN.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1086459
Title:
Name resolution over VPN fails; mdns4_minimal ret
** Summary changed:
- DNS Resolution Fails Except for 'host' Utility
+ Name resolution over VPN fails; mdns4_minimal returns NOTFOUND
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1086459
Title:
Na
12 matches
Mail list logo