Pi-Hole in Synology Docker

[Mainstay]

I am missing something fundamental in my setup of Pi-Hole.

I have the https://hub.docker.com/r/pihole/pihole/ version running without crashing every other second, but I cannot get any ad blocking to occur.

I have my USG's DNS pointing to my NAS but then internet effectively dies.

I am not sure if the fact that my 4 NICS in the NAS being bonded (1 & 2 to private network and 3 & 4 to public network) is the problem.

When the Pi-Hole container is created it makes a new bridged network inside of Docker, and I assume this is the correct behavior, but my experience with Docker is limited to this perpetually failing Pi-Hole experience.

In broad strokes my setup is:

static fiber >> USG >> Synology DS1618+

The USG handles DHCP & VLAN assignments and the NAS is running AD, File Sharing, and backup services.

Anyone have any experience setting up Pi-Hole in this sort of environment?

 

[phaZed]

Your problem could be in any of the steps.. Double and Triple check that your docker container is working correctly and is configured for the correct ports. You may need to give your docker privileged access - for a time while troubleshooting.

Can you ping the PiHole DNS server?

In my experience, I have not had too many issues with bonded connections as long as your networking equipment is new enough.. but certainly something to eliminate as the problem.

Can you post some screenshots of the logs? It's the icon furthest the right of your docker containers:

 

[Mainstay]

Double and Triple check that your docker container is working correctly and is configured for the correct ports.

I am 100% certain that this is the problem. I guess I have no idea what they are supposed to be. Every page on this seems to contradict exactly what environment settings should be used. And of course there is the guy who says they got it running in less than 30 seconds...

I might load up a VM and see if this will work under Ubuntu. I am new to Docker and Pi-Hole and neither are working out.

 

[Mainstay]

Maybe you can't run Pi-Hole on an AD?


TechAdmin@server:/volume1/docker/pihole$ sudo docker-compose up -d
Creating network "pihole_default" with the default driver
Creating pihole_pihole_1 ...
Creating pihole_pihole_1 ... error

ERROR: for pihole_pihole_1 Cannot start service pihole: driver failed programming external connectivity on endpoint pihole_pihole_1 (eeee25047dc08672d40a77411bb9ad33830a7e7a6d25d906 b25208f221701bcf):

Error starting userland proxy: listen tcp 0.0.0.0:53: bind: address already in use

ERROR: Encountered errors while bringing up the project.

TechAdmin@server:/volume1/docker/pihole$ sudo docker-compose down
Removing pihole_pihole_1 ... done
Removing network pihole_default

TechAdmin@server:/volume1/docker/pihole$ sudo netstat -pna | grep 53
tcp 0 0 172.17.0.1:53 0.0.0.0:* LISTEN 26504/named
tcp 0 0 192.168.3.10:53 0.0.0.0:* LISTEN 26504/named
tcp 0 0 192.168.1.10:53 0.0.0.0:* LISTEN 26504/named

 

[phaZed]

Error starting userland proxy: listen tcp 0.0.0.0:53: bind: address already in use

Looks like you have a service already running on port 53, on that server/NIC.

EDIT, should be fine with AD so long as your not hosting the AD server on the same IP..

 

[Mainstay]

If PH is running on the same server as the AD, won't it be the same IP? Or am I supposed to set a different IP in the PH Docker?

 

[phaZed]

For all intents and purposes, ya, the IP for external facing clients will be the same IP. This is where you would use those multiple NICs to supply more than one LAN IP address.

Another way to go about it, in the Docker's settings you can specify the "internal" and "external" ports... so you can pick an unused port for the external and just route it.

So..
[Internal Docker Port 53]---->[Unraid server external facing port 13370]

Now in your router, you can set any requests to an *IP of your choice* at port 53 will route to Unraid IP port 13370.

 

[Mainstay]

thank you - very helpful. Still confused, but I now have some more things to try.

 

[phaZed]

Check out "SpaceInvaderOne" on Youtube, he does a bunch of Unraid setup stuff... he's great.