Anyway, i have a Synology NAS with Docker installed and wanted to use Pi-Hole on the Docker. I was able to install it and it works, i can access the admin interface and all, works.
Problem is, my Router doesn't allow me to change the DNS Server, so i went ahead and disabled the DHCP Service on my Router and enabled the one on the Pi-Hole.
When i restart any Device in my Network, so they use the new DHCP Server, they are completely unable to even connect to the Network, seems like they're getting no IP Adress at all.
I used the same IP Range in the Pi-Hole as in the Router.
Also is it maybe possible to let my Router still be the DHCP Server? While googling i found a method, by setting the first UpStream DNS to the Router IP in the Pi-Hole, but this doesn't seem to work here.
Hope somebody can help me, also i'm not a pro on all that, so please keep answers simple if possible
Was your docker ran using host network mode --net=host (or the synology equivilent)? This puts it on the same network as your router - by default docker is on a segregated network. Imagine your network and docker container's networks like a like a router behind a router, two isolated networks - The 2nd router's DHCP wouldn't work on the 1st router if you turn off the 1st's DHCP. Docker host network mode connects a container to your network rather than docker's network enabling things like DHCP services to broadcast from a container onto your primary network.
The ports will need to go away from the container run command (host networking exposes all ports) and you may need to add --cap-add=NET_ADMIN as noted in the env var section of my README
I've never had to actually setup the DHCP in my docker so this is about the limit of my knowledge on the subject, purely from research.
Stupid Question: How can i start the docker with the "--net=host" and "--cap-add=NET_ADMIN" arguments?
Also yeah, the docker is running in the "bridge" mode (synology equivilent i guess), from what i can see here, not the "host" mode, i guess thats the problem.
I do not have a synology so I do not know exactly how to manage their containers on them. The synology forums look like they'd be your best bet on this topic - on which there is already some discussion here https://forum.synology.com/enu/viewtopic.php?f=258&t=119490
Well, i just tried this method described in the Synology forums, so starting the dock on host.
Pi-Hole refuses to start, since of Port 80 if i read that correctly from the logfile. Probably because the Synology also uses Port 80. I had to manually "map" Port 80 to 8080 (which is thrown out in host, as you also wrote) as i found this in a Youtube Video, demonstrating running Pi-Hole on Docker on a Synology NAS. But the Guy in the Video had better luck, since his Router allowed change of the DNS xD.
I guess this is a very unique Problem here, i mean i did found a Solution so it works at least. (Setting the DNS manually on the devices to the NAS)
