From 1ca46105773a318dbd5d9a53e9704610de43b209 Mon Sep 17 00:00:00 2001 From: Joachim Fasting Date: Thu, 24 Mar 2016 15:14:10 +0100 Subject: dnscrypt-proxy service: change default upstream resolver Previously, the cisco resolver was used on the theory that it would provide the best user experience regardless of location. The downsides of cisco are 1) logging; 2) missing supoprt for DNS security extensions. The new upstream resolver is located in Holland, supports DNS security, and *claims* to not log activity. For users outside of Europe, this will mean reduced performance, but I believe it's a worthy tradeoff. --- nixos/modules/services/networking/dnscrypt-proxy.nix | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/nixos/modules/services/networking/dnscrypt-proxy.nix b/nixos/modules/services/networking/dnscrypt-proxy.nix index 2c5c82f4d55c..886bfc30468e 100644 --- a/nixos/modules/services/networking/dnscrypt-proxy.nix +++ b/nixos/modules/services/networking/dnscrypt-proxy.nix @@ -74,13 +74,13 @@ in ''; }; resolverName = mkOption { - default = "cisco"; + default = "dnscrypt.eu-nl"; type = types.nullOr types.string; description = '' The name of the upstream DNSCrypt resolver to use. See - ${resolverListFile} for alternative resolvers - (e.g., if you are concerned about logging and/or server - location). + ${resolverListFile} for alternative resolvers. + The default resolver is located in Holland, supports DNS security + extensions, and claims to not keep logs. ''; }; customResolver = mkOption { -- cgit 1.4.1