When pihole is working as my DNS, with querries being logged and ads being blocked, pi.hole:[port]/admin should be accessible from any client using pihole as its DNS resolver. IP:[port]/admin is working.
pi.hole:[port]/admin returns "ERR_NAME_NOT_RESOLVED" on both chrome and firefox.
By restarting the client, pi.hole:[port]/admin will be accessible for an indeterminant amount of time but will eventually be inaccessible.
Yes. I am able to access the admin console directly via the LAN IP.
I set lighttpd port to 1980 because my port 80 is being used by something else.
My router requires me to have a secondary DNS server. What I see is happening is that my router sometimes switch to the secondary DNS because if I set the secondary DNS to an empty address, the behavior reported in this thread does not happen.
On a router that demands a second DNS server address, I entered the same DNS as the PiHole again, so the PiHole was listed twice. It appears the router just wanted some digits in that second address. All my DNS requests get routed to the PiHole.
For redundancy, what would you recommend as the best approach? I can put two Pi's on my network, each on a UPS (the routers and modems are also on UPS). One is a 3B+, the other a Zero W.
On my router (which is my DHCP server), list 3B+ first, then ZeroW on the DNS list? That way, if either is offline, the system will seamlessly go to the other. I don't think I can force my router to use one before the other (Apple router), so traffic would likely go to both on a regular basis as long as they are both up.
Have the 3B+ use it's internal unbound resolver first, then list the IP of the ZeroW as a second DNS server option (and use strict-control to enforce the order)? The weakness I see here is that if the 3B+ fails, there won't be any routing to the secondary.
Use your chronic script to have the backup Pi-Hole pickup if the primary fails.
Yes. That would be the best solution (i have that myself)
You can use them as standalone resolvers. Each with it’s own unbound. You don’t neet do point any of the two to each other.
The script is good and works if one of the Pi-hole devices would have been the DHCP server. In your case where the router does that, you don’t need the script.
Just run both raspberries in paralel, each with local unbound (if you want) set their IPs as DNS1 and DNS2 on the router and you are set.