Pi-hole is working fine and happily blocking DNS queries as it's supposed to, however I'd like to run DHCP from Pi-Hole so I can (hopefully) get logging by individual host rather than just localhost. BUT - Every time I turn on DHCP pi-hole shuts down DNS
latest pi-hole running in latest Docker on Windows 10
Standard install, the only change I have made is adding some additional lists to Gravity.
Here is my debug log token - q4SVL0HG
I'm afraid that's not possible with Docker for Windows.
A DHCP server can only answer DHCP requests of clients within the same network segment. By default, Docker isolates a container into a network segment.of its own.
Normally, you could just configure Docker to use e.g. host network mode for a container.
However, Docker on Windows is limited when compared to a Linux Docker. Specifically, host network mode is not supported on Windows.
Another approach would be to install a DHCP relay in order to forward DHCP requests from one network segment to another.
However, that relay would need a route from your client's network segment to Pi-hole's Docker internal IP address.
But alas, Docker for Windows cannot route traffic to Linux containers.
You could consider to search Docker's documentation and forum for further support. Maybe someone there has found a workaround.
Thanks for that 
I guess I should have read all those disclaimers "does not work on windows" before learning more about macvlan than I ever wanted to know.
I think i'll spin up a rasberry pi for the task.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.