Running Unbound with MINI PC in Redundancy

[jorge512]

The issue I am facing: One mini pc cancels the other. Cannot access GUI

Details about my system: @ mini pc’s running pihole with unbound. Router set up with primary and seconday dns of mini pc. One mini pc cancels the other. Cannot access pihole GUI and it goes offline. Read possible dns conflicts

What I have changed since installing Pi-hole: Switched prom raspberry pi in redundancy to 2 mini pc’s running debian amd64

Does anyone have experienced the above situation and have some solutions.

thank you

[nero355]

Dude what is a Mini PC in this case ?

How does your setup look like IP Addressing wise ?

You need to give us A LOT more information if you expect any help from anyone…

[jorge512]

replaced 2 raspberry pi’s in my network w/ BOSGAME E2 Mini PC Ryzen 5 3550H(Max 3.7GHz) DDR4 Mini Computers, 16GB RAM 512GB NVMe SSD. installed debian 13 amd64 on both mini pc’s, installed piholed and unbound. both pc’s have have their unique ip address. router’s dns was set to primary and secondary using the mini pc’s ip address. there is a dns conflict as one of the mini pc’s is cancelling the other. one of the mini pc’s goes offline.

the set up process was the same as the previous raspberry pi’s

[Bucking_Horn]

For each of your Pi-hole installations, please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:

sudo pihole -d

or if you run your Pi-hole as a Docker container:

docker exec -it <pihole-container-name-or-id> pihole -d

where you substitute <pihole-container-name-or-id> as required.

[jorge512]

got it. i am going to reinstall the mini pc’s again. should issue reappear. i’ll run the log and post it.

thx