public/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

nixos/dnscrypt-proxy docs: reword section on forwarding

Browse Source 
Newer versions of DNSCrypt proxy *can* cache lookups (via
plugin); make the wording more neutral wrt. why one might want
to run the proxy in a forwarding setup.
This commit is contained in:
Joachim Fasting 2017-03-09 20:32:03 +01:00
parent c0a8a9205b
commit 5279ec111f
No known key found for this signature in database
GPG Key ID: 7544761007FE4E08
1 changed files with 4 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
nixos/modules/services/networking/dnscrypt-proxy.xml
View File

@ -31,15 +31,12 @@
</sect1> </sect1>
<sect1><title>As a forwarder for a caching DNS client</title> <sect1><title>As a forwarder for another DNS client</title>
<para> <para>
By default, DNSCrypt proxy acts as a transparent proxy for the To run the DNSCrypt proxy client as a forwarder for another
system stub resolver. Because the client does not cache lookups, this DNS client, change the default proxy listening port to a
setup can significantly slow down e.g., web browsing. The recommended non-standard value and point the other client to it:
configuration is to run DNSCrypt proxy as a forwarder for a caching DNS
client. To achieve this, change the default proxy listening port to
a non-standard value and point the caching client to it:
<programlisting> <programlisting>
services.dnscrypt-proxy.localPort = 43; services.dnscrypt-proxy.localPort = 43;
</programlisting> </programlisting>
@ -60,7 +57,6 @@
<para> <para>
<programlisting> <programlisting>
{ {
networking.nameservers = [ "127.0.0.1" ];
services.unbound.enable = true; services.unbound.enable = true;
services.unbound.forwardAddresses = [ "127.0.0.1@43" ]; services.unbound.forwardAddresses = [ "127.0.0.1@43" ];
} }