Want to increase being safe when surfing the internet? <br />Want to minimize the number of DNS lookup requests leaving your network?<br /> Stay tuned and I will show you how<br /> <br />• Removing Cloudflare client<br />sudo systemctl stop cloudflared<br /> • Verify it is stopped<br />sudo systemctl status cloudflared<br /> • uninstall service<br />Sudo cloudflared service uninstall<br /><br />Install Unbound<br />sudo apt install unbound<br /><br />Sudo nano /etc/unbound/unbound.conf.d/pi-hole.conf<br /><br />server: # If no logfile is specified, syslog is used # logfile: "/var/log/unbound/unbound.log" verbosity: 0<br />interface: 127.0.0.1 port: 5335 do-ip4: yes do-udp: yes do-tcp: yes<br /># May be set to yes if you have IPv6 connectivity do-ip6: no<br /># You want to leave this to no unless you have *native* IPv6. With 6to4 and # Terredo tunnels your web browser should favor IPv4 for the same reasons prefer-ip6: no<br /># Use this only when you downloaded the list of primary root servers! # If you use the default dns-root-data package, unbound will find it automatically #root-hints: "/var/lib/unbound/root.hints"<br /># Trust glue only if it is within the server's authority harden-glue: yes<br /># Require DNSSEC data for trust-anchored zones, if such data is absent, the zone becomes BOGUS harden-dnssec-stripped: yes<br /># Don't use Capitalization randomization as it known to cause DNSSEC issues sometimes # see <a href="https://discourse.pi-hole.net/t/unbound-stubby-or-dnscrypt-proxy/9378" target="_blank" rel="nofollow">https://discourse.pi-hole.net/t/unbound-stubby-or-dnscrypt-proxy/9378</a> for further details use-caps-for-id: no<br /># Reduce EDNS reassembly buffer size. # Suggested by the unbound man page to reduce fragmentation reassembly problems edns-buffer-size: 1472<br /># Perform prefetching of close to expired message cache entries # This only applies to domains that have been frequently queried prefetch: yes<br /># One thread should be sufficient, can be increased on beefy machines. In reality for most users running on small networks or on a single machine, it should be unnecessary to seek performance enhancement by increasing num-threads above 1. num-threads: 1<br /># Ensure kernel buffer is large enough to not lose messages in traffic spikes so-rcvbuf: 1m<br /># Ensure privacy of local IP ranges private-address: 192.168.0.0/16 private-address: 169.254.0.0/16 private-address: 172.16.0.0/12 private-address: 10.0.0.0/8 private-address: fd00::/8 private-address: fe80::/10<br /><br />Start your local recursive server and test that it's operational:<br />sudo service unbound restart dig pi-hole.net @127.0.0.1 -p 5335<br /><br />You can test DNSSEC validation using<br />dig sigfail.verteiltesysteme.net @127.0.0.1 -p 5335 dig sigok.verteiltesysteme.net @127.0.0.1 -p 5335<br /><br />Finally, configure Pi-hole to use your recursive DNS server by specifying 127.0.0.1#5335 as the Custom DNS (IPv4):<br /><br />⏱️TIMESTAMPS<br />...<br /><a href="https://www.youtube.com/watch?v=U_OSX3-Kcrc" target="_blank" rel="nofollow">https://www.youtube.com/watch?v=U_OSX3-Kcrc</a>