I also deviated from the Network Filter article on how I store and update the dnscrypt-resolvers.csv file and how I select and specify the servers I want to use from that list.įirst, download the dnscrypt-resolvers.csv to your PC and open it in Excel. We also want the Pi to be able to set its time via NTP without waiting for DNSCRYPT. We really just want to encrypt the lookups that DNSMASQ is making for your other network clients. We're not too worried about encrypting the DNS lookups the Pi is making. There is no way when DNSCRYPT is starting that it will be able to resolve its nameservers when DNSMASQ running on 127 is trying to use DNSCRYPT. I would even remove the 127 address as an option. The upshot of this is the standard /etc/nf file used by your Pi (and DNSCRYPT) should only contain nameserver lines pointing to your ISP's nameservers. Pay careful attention to the configuration of the nf and nf files. Read the Network Filter article on how to set up DNSMASQ and DNSCRYPT on your Pi. The Pi needs to be configured so that its own lookups go through your regular DNS servers - otherwise DNSCRYPT can't resolve the name servers it needs to establish encrypted connections to.ĭNSMASQ will be used by other clients on your network that try to use the Pi as a name server. DNSCRYPT proxies lookups through certain DNS servers on the internet that support DNSCRYPT and claim they will not log your lookups. DNSMASQ caches DNS lookups it does through DNSCRYPT so you are not using DNSCRYPT for every lookup. DNSMASQ is fully featured DNS server and is required for the Ad Blocking feature as well. This consists of two services - DNSMASQ and DNSCRYPT. You'll also want to assign it a static IP - outside of the DHCP range of your router. The Pi also seems powerful enough to run a web server, web application framework and a decent database such as Postgres, but you might be better off hosting that on a t2.micro instance on Amazon EC2.įirst, follow my Raspberry Pi 3 Initial Configuration guidelines except I recommend you connect this Pi to your home network using an Ethernet cable rather than use Wi-Fi. So your FTP address ( ) always points to your public IP
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |