Pi-Hole 4.3.2 - Hackdot

Re:Pi-Hole 4.3.2 by mikepurvis on Tuesday September 24, 2019 @10:01AM (#21060233)

There are still a few possibilities for how it could work— first would be running multiple instances of dnsmasq and then putting a reverse proxy in front of them that would direct the traffic based on who's asking.

Another would be switching to a purpose-built DNS resolver/cache that had this capability.

Finally, you could have per-client DNS IPs, but this would require the cooperation of the DHCP server, which is less typical on a home network where that's often a closed-source router. But a "super pi-hole" following this pattern could also potentially be the DHCP server. (Yes, raspberry pi can run OpenWRT: https://openwrt.org/toh/raspberry_pi_foundation/raspberry_pi)

[ Parent | on HN ]

Re:Pi-Hole 4.3.2 by Mister_Snuggles on Tuesday September 24, 2019 @11:13AM (#21061050)

> Another would be switching to a purpose-built DNS resolver/cache that had this capability.

Pi-Hole has already gone down this road with their FTLDNS package[0], so it's really a question of where they want the project to go.

[0] https://pi-hole.net/2018/02/22/coming-soon-ftldns-pi-holes-o...

[ Parent | on HN ]

Re:Pi-Hole 4.3.2 by promofaux on Tuesday September 24, 2019 @02:16PM (#21063078)

And of course, now we have more control over/hooks into the resolver, we can look at things like per-client configs:

https://github.com/pi-hole/pi-hole/pull/2935

[ Parent | on HN ]

Re:Pi-Hole 4.3.2 by edoceo on Tuesday September 24, 2019 @10:58AM (#21060875)

Dnsmasq can be the DHCP too. I basically run a "pi-hole" like thing on a Soekris - handles four subnets and routes and other neat network magic.

It serves dead pages for CSS, JS and IMG

[ Parent | on HN ]