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 th
The latest package that's waiting in NEW will have a different
default resolver and should work fine with DNSSEC.
* 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
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
Control: tags -1 fixed-upstream
So this should be fixable in the next release when the anycast
addresses are added for http://dnsrec.meo.ws/.
* Ivan Vilata i Balaguer (i...@selidor.net) wrote:
> Package: dnscrypt-proxy
> Version: 1.4.3-2
> Severity: normal
>
> Hi! The README of ``dnscrypt-prox
* Ivan Vilata i Balaguer (i...@selidor.net) wrote:
> Package: dnscrypt-proxy
> Version: 1.4.3-2
> Severity: normal
>
> Hi! The README of ``dnscrypt-proxy`` recommends using Unbound as a DNS
> caching resolver in combination with it. However, Unbound enables DNSSEC and
> the default configuration
Package: dnscrypt-proxy
Version: 1.4.3-2
Severity: normal
Hi! The README of ``dnscrypt-proxy`` recommends using Unbound as a DNS
caching resolver in combination with it. However, Unbound enables DNSSEC and
the default configuration of ``dnscrypt-proxy`` sets
``DNSCRYPT_PROXY_RESOLVER_NAME=opendn
6 matches
Mail list logo
