On Tue, Aug 30, 2016 at 11:36:03AM -0400, Eric Dorland wrote: > The latest package that's waiting in NEW will have a different > default resolver and should work fine with DNSSEC.
If the dnscrypt-resolvers.csv from the current master git branch is the same as the one in the 1.7.0-1 package then this does not hold true: Name,Full name,Description,Location,Coordinates,URL,Version,DNSSEC validation,No logs,Namecoin,Resolver address,Provider name,Provider public key,Provider public key TXT record fvz-anyone,Primary OpenNIC Anycast DNS Resolver,Fusl's public primary OpenNIC Tier2 Anycast DNS Resolver,Anycast,,http://dnsrec.meo.ws/,1,no,yes,yes,185.121.177.177,2.dnscrypt-cert.dnsrec.meo.ws,1A6A:D0A3:2B4C:5A61:A695:D153:670D:69AB:1690:3F9E:C3F7:F64F:13E5:35A3:18B2:28A5, fvz-anytwo,Secondary OpenNIC Anycast DNS Resolver,Fusl's public secondary OpenNIC Tier2 Anycast DNS Resolver,Anycast,,http://dnsrec.meo.ws/,1,no,yes,yes,185.121.177.53,2.dnscrypt-cert.dnsrec.meo.ws,1A6A:D0A3:2B4C:5A61:A695:D153:670D:69AB:1690:3F9E:C3F7:F64F:13E5:35A3:18B2:28A5, > > * har...@a-little-linux-box.at (har...@a-little-linux-box.at) wrote: > > Dear Eric Dorland, > > > > according to the dnscrypt-resolvers.csv file these resolvers don't > > support DNSSec, so I guess this bug should be kept open - IMHO it would > > make more sense to tell users how to disable DNSSec :-/. > > > > Kind regards > > Harald Jenny > > -- > Eric Dorland <e...@kuroneko.ca> > 43CF 1228 F726 FD5B 474C E962 C256 FBD5 0022 1E93
