So, the DNS requests go from my clients to Google WiFi, and then from there two one of my RPis, and then from there (through HTTPS) to Google's DNS server on the internet (or one of the backups).Įdit to add: What this does mean is your DNS server can't tell what the source of any particular DNS request actually was, since they are all coming from 192.168.86.1 at that point. Those RPi units on my internal network are configured in my Google WiFi as the primary and secondary DNS servers, but then they are each configured to resolve through HTTPS via Google, Cloudflare, or Quad9 DNS. If you want to test the results of your Raspberry Pi DNS server without changing your DNS you can by making use of the dig tool. Pihole has other features like a built in DHCP server. If you are up to it I would advice to take a fresh raspbian stretch image. Nxfilter has a lot more functionality built in regarding DNS-level ad and malware blocking. I use this setup to get all of my DNS traffic tunneled through DNS-over-HTTPS by running a couple of Raspberry Pi units with "cloudflared" installed. As you are new to raspberry and unix you may have a high learning cave. What will happen is all of the clients will still be configured to use the primary Google WiFi unit (typically 192.168.86.1) as the DNS server, but all of the requests that get sent there will then be forwarded to whatever DNS server(s) you have configured. 2.Raspberry PI 4 compute module(lot of compute module boards coming with multiple NICs) 3.NanoPi R4S (small, cheap, 6 core CPU) Logged pakcjo. Hello may not look like it, but it's actually working.
0 kommentar(er)
