[Dnssec-trigger] [Bug] incorrect DNS servers are used when network-manager connects to VPN
post at ralfj.de
Wed Sep 3 17:32:49 UTC 2014
Dear dnssec-trigger developers,
I hope this is the right channel for a bugreport, please excuse me if it
First of all, thanks a lot for making this awesome program. It is
exactly what I looked for to finally use DNSSEC on my Laptop :)
I am having a problem though when using dnssec-trigger with
network-mananger and VPN connections. After the connection is
established, dnssec-trigger still uses the DNS servers supplied by the
physical "outer" connection, instead of the ones that came from the VPN.
Thus, DNS does not work if the servers are configured to serve the local
I can see the following in the system journal after the VPN connection
> Sep 01 11:12:12 r-schnelltop logger: dnssec-trigger-hook(networkmanager) vpn0 vpn-up added global DNS 220.127.116.11 18.104.22.168 22.214.171.124
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.
I am using the packages in Debian testing, and also reported this issue
The version of NM is 0.9.10.0, dnssec-trigger is at version 0.13~svn685.
More information about the dnssec-trigger