[Pkg-dns-devel] Bug#871177: search domains declared in /etc/resolv.conf not taken over by dnssec-trigger
Sven Bartscher
kritzefitz at debian.org
Sun Aug 6 22:22:19 UTC 2017
Package: dnssec-trigger
Version: 0.13-6
Severity: normal
Greetings,
When dnssec-trigger overwrites /etc/resolv.conf it doesn't seem to
take over search domaions declared there. I would expect it to
integrate non-nameserver options declared there into its own generated
configuration file. Otherwise I don't see a way to effectively set
these options while dnssec-trigger is active.
This also affects search-domains received via DHCP.
Regards
Sven
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages dnssec-trigger depends on:
ii gir1.2-networkmanager-1.0 1.8.2-1
ii init-system-helpers 1.49
ii libc6 2.24-12
ii libgdk-pixbuf2.0-0 2.36.5-2
ii libglib2.0-0 2.52.3-1
ii libgtk2.0-0 2.24.31-2
ii libldns2 1.7.0-3
ii libssl1.1 1.1.0f-3
ii python 2.7.13-2
ii python-gi 3.22.0-2+b1
ii python-lockfile 1:0.12.2-2
ii unbound 1.6.4-1
dnssec-trigger recommends no packages.
dnssec-trigger suggests no packages.
-- no debconf information
More information about the pkg-dns-devel
mailing list