[Resolvconf-devel] Bug#776778: Please play nicely with resolvconf

Ondřej Surý ondrej at sury.org
Wed Feb 4 10:02:05 UTC 2015


Hi Thomas,

do you think that we can push the resolvconf compatibility to jessie?

I see two possible paths here:

a) add Breaks: resolvconf
b) add (Pre-)Depends: resolvconf and force resolvconf usage

BTW does resolvconf play nicely with NetworkManager?

Cheers,
Ondrej

On Tue, Feb 3, 2015, at 21:07, Thomas Hood wrote:
> Currently dnssec-trigger is not resolvconf-compatible. For one thing,
> dnssec-triggerd writes /etc/resolv.conf directly and sets the
> immutability attribute on the file, causing resolvconf installation to
> fail and resolvconf to fail to function as designed.
> 
> Let this report track the request that dnssec-trigger be made
> resolvconf-compatible.
> 
> To be resolvconf-compatible, dnssec-trigger executables should refrain
> from writing to /etc/resolv.conf.
> 
> Looking at unbound, I see that its initscript already communicates
> correctly with resolvconf. So there may be no need at all for
> dnssec-trigger itself to futz with /etc/resolv.conf.
> -- 
> Thomas Hood


-- 
Ondřej Surý <ondrej at sury.org>
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server



More information about the Resolvconf-devel mailing list