Nicolai: Please also do the following.
dpkg -l bind9
ps -ef|grep dns
ps -ef|grep named
(That is, run these in a terminal and post the output here.)
** Summary changed:
- resolvconf incorrectly configures resolv.conf
+ "nameserver 127.0.0.1" in resolv.conf causes failure of name resolution
--
Nicolai: I'm glad I asked because my first thought was that you might
have the "dnsmasq" package installed and disabled in a non-standard way.
The "dnsmasq" initscript sends "nameserver 127.0.0.1" to resolvconf
unless the dnsmasq service is disabled in a standard way. But you don't
have the "dnsma
On 05/22/2012 12:14 PM, Thomas Hood wrote:
> Nicolai: You say that the dnsmasq package is installed but that no
> dnsmasq process is running. How did you disable dnsmasq?
I don't think I did. For hor many versions of ubuntu has it been
supposed to be running?
> Also, please send the output of t
Nicolai: You say that the dnsmasq package is installed but that no
dnsmasq process is running. How did you disable dnsmasq?
Also, please send the output of this command run in a terminal on the
system in question:
dpkg -l \*dnsmasq\*
--
You received this bug notification because you are a
On 05/20/2012 10:56 PM, Thomas Hood wrote:
> People who don't know about resolvconf won't be so clever as to remove
> it as a way of solving a name resolution problem in another package.
>
> In the submitted file, "nameserver 127.0.0.1" correctly refers to the
> caching nameserver (dnsmasq) listen
On Sun, May 20, 2012 at 07:05:10PM -, janl wrote:
> Brilliant phrasing: "The expected configuration" falls so hard into the
> deep black hole of bug number 1 that there is no come back.
It doesn't for the vast majority of users.
Do you have a local nameserver installed on your system? This i
People who don't know about resolvconf won't be so clever as to remove
it as a way of solving a name resolution problem in another package.
In the submitted file, "nameserver 127.0.0.1" correctly refers to the
caching nameserver (dnsmasq) listening on that loopback address. If
dnsmasq doesn't reso
On 05/20/2012 08:08 PM, Stéphane Graber wrote:
> This is actually the expected configuration. The fact that you don't get
> working DNS resolving might be caused by bug 993379 which should get
> resolved with the next batch of Network Manager updates (workaround is
> to reconnect to the network pos
This is actually the expected configuration. The fact that you don't get
working DNS resolving might be caused by bug 993379 which should get
resolved with the next batch of Network Manager updates (workaround is
to reconnect to the network post-boot).
You can learn more about the DNS changes here
