User Tools

Site Tools


pfsense:dns:force_dns_over_tls

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
pfsense:dns:force_dns_over_tls [2022/10/08 08:39] peterpfsense:dns:force_dns_over_tls [2022/10/08 09:13] (current) – [Another Example] peter
Line 3: Line 3:
 DNS requests are normally not encrypted, and therefore visible to your ISP to record, use for research / marketing purposes, or even (in the case of some nefarious actors) manipulate or change. DNS requests are normally not encrypted, and therefore visible to your ISP to record, use for research / marketing purposes, or even (in the case of some nefarious actors) manipulate or change.
  
-Running DNS over TLS prevents that, by encrypting your DNS traffic so that it can’t be manipulated or collected.+Running DNS over TLS prevents that, by encrypting your DNS traffic so that it cannot be manipulated or collected.
  
 <WRAP important> <WRAP important>
Line 90: Line 90:
 </code> </code>
  
-See https://nlnetlabs.nl/documentation/unbound/unbound.conf/ for info on these options.+<WRAP info> 
 +**NOTE:**  See https://nlnetlabs.nl/documentation/unbound/unbound.conf/ for info on these options.
  
-It’s OK to set the resolver to listen on all interfaces, since the firewall rules on the WAN will prevent Internet hosts from using your resolver anyway.+It is OK to set the resolver to listen on all interfaces, since the firewall rules on the WAN will prevent Internet hosts from using your resolver anyway. 
 + 
 +</WRAP>
  
 <WRAP important> <WRAP important>
pfsense/dns/force_dns_over_tls.1665218391.txt.gz · Last modified: 2022/10/08 08:39 by peter

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki