Ubuntu
network-manager package

  1. Bug #991347
  2. Comment #9

Comment 9 for bug 991347

Revision history for this message
Thomas Hood (jdthood) wrote : Re: After upgrade to 12.04 resolvconf seems ok but does not work

200.162.192.51 replies with "status: NOERROR" and "ANSWER: 0". What may be happening is that 200.162.192.51 is answering quickly and dnsmasq is therefore choosing it over the other nameservers, with bad results.

If the problem is a flaky nameserver which responds quickly then having a list of nonlocal nameserver addresses rather than "127.0.0.1" in resolv.conf avoids the problem because the resolver tries one nameserver at a time. See bug #1003842 for explanation.

You don't need the "dnsmasq" package unless you want to run dnsmasq independently of NetworkManager. I suggest you remove it, keeping only dnsmasq-base.

See if this fixes the problem. Edit /etc/NetworkManager/NetworkManager.conf, comment out the line "dns=dnsmasq" and do "sudo restart network-manager". Then NM won't use dnsmasq any more.