Package: dnssec-trigger Version: 0.13~svn685-1 Severity: normal Dear Maintainer,
when NetworkManager connects to a VPN, dnssec-trigger still uses the old DNS servers from the "outer" (plain) network connection. I can see the following in the system journal: Sep 01 11:12:12 r-schnelltop logger[3766]: dnssec-trigger-hook(networkmanager) vpn0 vpn-up added global DNS 134.96.7.100 134.96.7.99 134.96.7.5 However, these are the DNS servers of wlan0. The VPN returned a different set of DNS servers. Only after supplying the VPN-DNS-servers to dnssec-trigger-control, everything works as expected. Kind regards Ralf -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.1 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dnssec-trigger depends on: ii init-system-helpers 1.21 ii libc6 2.19-9 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libglib2.0-0 2.40.0-4 ii libgtk2.0-0 2.24.24-1 ii libldns1 1.6.17-5 ii libssl1.0.0 1.0.1i-2 ii python 2.7.8-1 ii unbound 1.4.22-2 dnssec-trigger recommends no packages. dnssec-trigger suggests no packages. -- Configuration Files: /etc/dnssec-trigger/dnssec-trigger.conf changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
