[Dnssec-trigger] dnssec trigger 0.4 release

Stephane Bortzmeyer bortzmeyer at nic.fr
Fri Sep 23 19:34:45 UTC 2011


On Fri, Sep 23, 2011 at 10:28:57AM +0200,
 W.C.A. Wijngaards <wouter at NLnetLabs.nl> wrote 
 a message of 78 lines which said:

> http://www.nlnetlabs.nl/~wouter/dnssec-trigger-0.4.tar.gz

It no longer works on my Ubuntu Oneiric Ocelot (Beta, updated today).
dnssec-trigger-control status reports properly:

% dnssec-trigger-control status                         
at 2011-09-23 21:31:30
cache 212.27.40.240: OK 
cache 212.27.40.241: error no EDNS
state: cache secure

But resolv.conf is the one from NetworkManager, it does not point
towards the local Unbound:

# Generated by NetworkManager
nameserver 212.27.40.241
nameserver 212.27.40.240
nameserver 2a01:e00::2
# NOTE: the libc resolver may not support more than 3 nameservers.
# The nameservers listed below may not be recognized.
nameserver 2a01:e00::1

As a result, I no longer get my AD bit (since Free Telecom's name
servers do not validate).



More information about the dnssec-trigger mailing list