![]() ![]() 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. Pi-holeSafeSearch.sh -enable This can all be done via ssh to the blockhole. 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. 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. Even better, its free for environments up to 25 users. 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. NxFilter is a product Ive used for years as a self hosted, DNS-based content filter. ![]() ![]() Hello may not look like it, but it's actually working. ![]()
0 Comments
Leave a Reply. |