Relays are very simple software, you just have to configure it to point to your Docker host's IP port 67.Īlthough uncommon, if your router is an advanced enough router it may support a DHCP relay. A relay points to your containers forwarded port 67 and spreads the broadcast signal from an isolated docker bridge onto your LAN network. If you want to use docker's bridged network mode then you need to run a DHCP relay.
Tony Lawrence detailed macvlan setup for Pi-hole first in the second part of his great blog series about Running Pi-hole on Synology Docker, check it out here: Free your Synology ports with Macvlan Docker Pi-hole with a bridge networking ¶Īdvantages: Works well with container web reverse proxies like Nginx or Traefik Having the container get its own IP not only solves the broadcast problem but avoids port conflicts you might have on devices such as NAS devices with web interfaces. This mode is similar to host network mode but instead of borrowing the IP of your docker host computer it grabs a new IP address off your LAN network.
This document details why Docker Pi-hole DHCP is different from normal Pi-hole and how to fix the problem. Optional: Dual operation: LAN & VPN at the same timeĭocker runs in a separate network by default called a docker bridge network, which makes DHCP want to serve addresses to that network and not your LAN network where you probably want it.