H3is3nb3rg Posted March 9, 2023 Share Posted March 9, 2023 (edited) Hello all, I'm trying to get a second pihole setup to have a failover incase the first one on my Synology NAS goes out. But when I try and setup using custom network, I cannot access the pihole with the 192.16899.203 IP. If I set it up under bridge it then works but only as the same IP as my Unraid server, it will not come up under the specified IP address I gave it (192.16899.203). I did point the IP address on the second image to the first pihole IP address. The last image shows to use Bridge mode instaead of br0 and that worked but its using the Unraid Ip address instead of the IP address I specified. I know I'm kind of rambling on here but hope it makes sense! I should also note, I have Unbound setup as well Any help would be appreciated! Edited March 10, 2023 by H3is3nb3rg Quote Link to comment
H3is3nb3rg Posted March 10, 2023 Author Share Posted March 10, 2023 (edited) With these settings, it states the 2nd pihole is unreachable. I must be doing something wrong? Is it because of port 80? Do I need to change it to port 8080? Edited March 10, 2023 by H3is3nb3rg Quote Link to comment
Vr2Io Posted March 10, 2023 Share Posted March 10, 2023 1 hour ago, H3is3nb3rg said: Is it because of port 80? Do I need to change it to port 8080? No, both were different IP. You should check the logs and confirm 2nd Pihole have start and you must use separate path mapping for 2nd Pihole. I simple try as below and config 2nd Pihole use custom DNS ( 1st Pihole IP and not set any path mapping because just for testing ), that's all. Quote Link to comment
H3is3nb3rg Posted March 10, 2023 Author Share Posted March 10, 2023 (edited) 11 hours ago, Vr2Io said: No, both were different IP. You should check the logs and confirm 2nd Pihole have start and you must use separate path mapping for 2nd Pihole. I simple try as below and config 2nd Pihole use custom DNS ( 1st Pihole IP and not set any path mapping because just for testing ), that's all. Thank you for this but unfortunately, it's still a no go. It states it took too long to reach and cannot reach this page. Edited March 10, 2023 by H3is3nb3rg Quote Link to comment
H3is3nb3rg Posted March 10, 2023 Author Share Posted March 10, 2023 The pihole DNS on the second one is pointing to the first Pihole. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.