From 8497d4fb847a276a580b0af4daaaf9d94f93260a Mon Sep 17 00:00:00 2001 From: Mikaela Suomalainen Date: Mon, 26 Nov 2018 23:43:39 +0200 Subject: [PATCH] dnscrypt-proxy.toml: enable require_nolog Learning that I don't have to specify servers there is a lot more variety even if I start requiring more things, as Sedric says to see 33 live servers, I guess dnscrypt servers in general respect privacy. However I guess I still have to trust on what the servers say as AFAIK dnscrypt-proxy is only that, a proxy, and won't start validating dnssec by itself. --- etc/dnscrypt-proxy/dnscrypt-proxy.toml | 1 + 1 file changed, 1 insertion(+) diff --git a/etc/dnscrypt-proxy/dnscrypt-proxy.toml b/etc/dnscrypt-proxy/dnscrypt-proxy.toml index f8d4df80..e91dfd58 100644 --- a/etc/dnscrypt-proxy/dnscrypt-proxy.toml +++ b/etc/dnscrypt-proxy/dnscrypt-proxy.toml @@ -18,6 +18,7 @@ ipv6_servers = true block_ipv6 = false require_dnssec = true require_nofilter = true +require_nolog = true # Use Google DNS B for resolving the server_names[] if the system # resolver is broken (which it is for me as it points directly to