Package: dnssec-trigger,resolvconf Control: found -1 dnssec-trigger/0.13~svn685-3 Control: found -1 resolvconf/1.76.1
Dear Maintainers of dnssec-trigger and resolvconf, besides the installation issue just reported at https://bugs.debian.org/776776, these two packages don't work well together either: After reconnecting to my LAN via Network Manager with both packages installed, /etc/resolv.conf looked like this: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 192.168.1.1 nameserver 127.0.0.1 search deuxchevaux.org This is definitely not what is expected: /etc/resolv.conf only should contain 127.0.0.1 and the local unbound instance should then forward requests to 192.168.1.1, but 192.168.1.1 must not appear in /etc/resolv.conf as that may circumvent local DNSSEC validation. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (110, 'experimental'), (109, 'buildd-unstable'), (109, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.18.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
