Hi
I've uploaded openresolv-3.4.4 to mentors@ which fixes this problem by
specifying default config files to write out for dnsmasq, pdns and
unbound.
Please test it, and if let me know if it works for you.
Thanks
Roy
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
OK, so what's the correct protocol here?
Do not, under any circumstances, break my system without at least
printing a warning during the upgrade and mailing root.
Thoughts?
Since I'm not sure what issues with resolvconf openresolv is trying to
solve, it's difficult for me to make any
On Fri, 2011-06-17 at 07:45 +0100, Simon Kelley wrote:
On 17/06/11 07:34, Roy Marples wrote:
On Fri, 2011-06-17 at 00:02 +0200, Juliusz Chroboczek wrote:
The point I'm making is that replacing dhcpd with dhcpcd5 broke
a working system by replacing resolvconf with openresolv. I'd like to
Can you tell me which package owns a file in /etc/resolvconf/update.d
which updates dnsmasq?
$ dpkg -S /etc/resolvconf/update.d/dnsmasq
dnsmasq: /etc/resolvconf/update.d/dnsmasq
$ dpkg -s dnsmasq | grep ^Version
Version: 2.57-1
$
-- Juliusz
--
To UNSUBSCRIBE, email to
On Fri, 2011-06-17 at 00:02 +0200, Juliusz Chroboczek wrote:
The point I'm making is that replacing dhcpd with dhcpcd5 broke
a working system by replacing resolvconf with openresolv. I'd like to
clarify whose bug that is:
...
No, it worked out of the box.
Well, that is interesting because
On 17/06/11 07:34, Roy Marples wrote:
On Fri, 2011-06-17 at 00:02 +0200, Juliusz Chroboczek wrote:
The point I'm making is that replacing dhcpd with dhcpcd5 broke
a working system by replacing resolvconf with openresolv. I'd like to
clarify whose bug that is:
...
No, it worked out of the
Package: Openresolv
Version: 3.4.0-1
Severity: important
Upgrading from the old dhcpcd package to the dhcpcd5 one, caused
openresolv to replace resolvconf, and my DNS stopped working.
Investigation showed that the openresolv doesn't write
/var/run/dnsmasq/resolv.conf, instead appending the
On Thu, 2011-06-16 at 11:54 +0200, Juliusz Chroboczek wrote:
Investigation showed that the openresolv doesn't write
/var/run/dnsmasq/resolv.conf, instead appending the DHCP-provided name
servers to /etc/resolv.conf (*after* 127.0.0.1, which is why everything
broke).
openresolv does not come
(Roy, resending due to incorrect headers in previous copy.)
openresolv does not come pre-configured for non libc resolvers.
You are expected to configure /etc/resolvconf.conf (which has a man
page) to get it to write out a dnsmasq configuation file which dnsmasq
can then include.
Ah, I see.
9 matches
Mail list logo
