Yes, it looks as if the problem is that NM is forgetting the second
nameserver address.
Can you reproduce this malfunction with the Quantal version of network-
manager?
** Package changed: dnsmasq (Ubuntu) => network-manager (Ubuntu)
** Summary changed:
- vpn dns server addresses - host lookups
I believe that you might be able to replicate this bug by setting up a
vpn in "Automatic (VPN) addresses only" mode and specifying two DNS
server addresses (one valid and one not). See attached image for
example.
** Attachment added: "snapshot.png"
https://bugs.launchpad.net/ubuntu/+source/dn
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.0.1
search kl.imgtec.org
$ ping glenn.kl.imgtec.org
ping: unknown host glenn.kl.imgtec.org
--
You recei
> I would have expected the DNS lookup to fall back to the second server
when it failed to receive a reply from the first server instead of just
giving up.
What is the output of "cat /etc/resolv.conf"?
What happens if you do "ping glenn.kl.imgtec.org"?
--
You received this bug notification beca
