In my case I have a device that is generating on average 7 queries per day on this backup because this device picks and use the second DNS server from the DCHP answer. For both the Command-line Interface (CLI) and Web Interface, we achieve this through the piholecommand (this helps minimize code duplication, and allows users to read exactly what's happening using bashscripting). This priority ordering is much more a “convention” and you will still see sometimes some queries happening on the backup Pi-hole. The core script of Pi-hole provides the ability to tie many DNS related functions into a simple and user-friendly management system, so that one may easily block unwanted content such as advertisements. But this is not a guarantee (by the spec). Usually, devices will pick the first DNS server, use it, and if not answering will use the other ones. Working with several DNS serversīy pushing 2 DNS servers, most of the DNS queries will go to the first one. This instruction will push to your devices in your network 2 DNS servers in this order: 192.168.125.2 and 192.168.125.3. The idea is to create a Dnsmasq configuration on both Pi-holes. This can be done through the pi-hole configuration steps, of through the web interface: The idea is to assign to both Pi-holes a different DHCP range to serve, and also expose both themselves as DNS servers in the same order. You first need of course to setup 2 Pi-holes the same way, with different IP addresses. So here is a little recipe to put 2 Pi-holes in redundancy so that you have a backup if one fails. And when it happens, all your local network goes down. The problem is that a Raspberry Pi is not as reliable as a NAS or a router. It will act as a DNS/DHCP provider for your local network and block all domains based on some lists (i.e. You probably know about this awesome Ad Blocker called Pi-hole that you can install on a little Raspberry Pi.
0 Comments
Leave a Reply. |