3 ms·

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 the

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 https://openwrt.org/toh/raspberry_pi_foundation/raspberry_pi)

Mister_Snuggles 7y ago
> 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-own-dns-dhcp-server/ https://pi-hole.net/2018/02/22/coming-soon-ftldns-pi-holes-o...
- promofaux 7y ago
  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 https://github.com/pi-hole/pi-hole/pull/2935
edoceo 7y ago
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