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
Whatever Stéphane thinks will be helpful in debugging this is probably
correct, so it'd be helpful if you could provide that output.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/991347
Title:
==
OUTPUT OF dig @200.212.223.43 www.terra.com.br
==
; DiG 9.8.1-P1 @200.212.223.43 www.terra.com.br
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached
==
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/991347
Title:
After upgrade to 12.04 resolvconf seems ok but does not work
To manage notifications about this bug go to:
Thanks for this bug report. Since resolvconf appears to be populating
/etc/resolv.conf as designed, but dnsmasq is failing to resolve for you,
I'm reassigning this to network-manager (the package responsible for
setting up dnsmasq this way on the desktop).
Since you're getting an answer at all,
Could you also post the same dig result for each of the servers listed
in your dnsmasq configuration?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/991347
Title:
After upgrade to 12.04 resolvconf
Steve Langasek, I do not have bind installed, but I have some packages
named bind9-host, libbind9-60 and libbind9-80. They must not be
interfering with dnsmasq, bind9-host doesn't even have an executable
other than host.
Reducing the number of nameservers actually worked! I editted my
dhcpd.conf
About the last comment: I do not understand very well what's going on.
Here's what I did:
* Before looking at these comments, I removed all wired connections from
network manager configuration. I rebooted the server and the resulting
resolv.conf was not referencing 127.0.0.1 anymore, but the DNS
Stéphane, I will wait from a response from Steve before posting all
these digs, ok? Or do you still want me to try using all these dns
servers so that DNS resolution does not work again and digging on all?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is