Pi Hole - Docker container - DHCP

[Coop777]

I'm running (2) Pi Hole docker containers. Supposedly you can run DHCP server via Pi Hole but I have never been able to get it to work. This would be handy for being able to track individual IP addresses, with DHCP running on my router this doesn't work right. Any ideas?

 

[Telos]

AdguardHome can track users without DHCP. Better than pihole IMO.

 

[Coop777]

does this tutorial for setup look accurate?

How to Install AdGuard Home on a Synology NAS! - WunderTech

This tutorial will show you how to setup AdGuard Home on a Synology NAS! Full setup instructions that guide you through the whole process!

www.wundertech.net

 

[Telos]

does this tutorial for setup look accurate?

When I set this up initially, I went with @Dr_Frankenstein 's post here (Wundertech is usually reliable, but I prefer to avoid macvlan unless it offers a clear benefit).

 

[Coop777]

I thank you sir

 

[RonV42]

I'm running (2) Pi Hole docker containers. Supposedly you can run DHCP server via Pi Hole but I have never been able to get it to work. This would be handy for being able to track individual IP addresses, with DHCP running on my router this doesn't work right. Any ideas?

I would suggest MacVLAN networking in Docker for those running Pi Hole in docker and wanting to use DHCP. This puts the MAC off the service right on your network adapter of the Synolgoy. Be careful with the ip addressing and subnetting.

Here is a snippet of my docker-compose file:

services:
  pihole:
    container_name: pihole
    image: pihole/pihole:latest
    hostname: pihole2
    domainname: mydomain.com             # <-- Update
    mac_address: 02:42:c0:a8:0a:cd          # <-- leave out initally then add when the mac is generated from container for consitantcy
    cap_add:
      - NET_ADMIN
    networks:
      pihole_network:
        ipv4_address: 192.168.10.205  # <-- Update
    dns:
      - 1.1.1.1
      - 1.0.0.1
    ports:
      - 443/tcp
      - 53/tcp
      - 53/udp
      - 67/udp
      - 80/tcp
    environment:
      ADMIN_EMAIL: [email protected]
      TZ: America/Chicago
      ServerIP: 192.168.10.205               # <-- Update (match ipv4_address)
      WEBPASSWORD: letmein                   # <-- Add password (if required)
      VIRTUAL_HOST: piholeX.xxxx.xxx  # <-- Update (match hostname + domainname)
      PIHOLE_DNS_: 192.168.10.206#53
      REV_SERVER: "true"
      REV_SERVER_DOMAIN: xxxxx.xxx     # domain of local network router/dhcp server
      REV_SERVER_TARGET: 192.168.10.252      # ip address of local network router
      REV_SERVER_CIDR: 192.168.0.0/16        # Reverse DNS Zone
      DNSMASQ_LISTENING: all                 # Listen on all interfaces
      TEMPERATUREUNIT: 'f'                     # temperature units
      WEBUIBOXEDLAYOUT: boxed                # for working on large screens
    volumes:
       - './etc-pihole/:/etc/pihole/'
       - './etc-dnsmasq.d/:/etc/dnsmasq.d/'
    restart: unless-stopped

networks:
  pihole_network:
    driver: macvlan
    driver_opts:
      parent: eth0
    ipam:
      config:
        - subnet: 192.168.10.0/24            # <-- Update
          gateway: 192.168.10.252              # <-- Update
          ip_range: 192.168.10.201/32        # <-- Update

 

[Coop777]

I've done the MACVLAN setup with Portainer/Docker, so I get the gist of what you are saying, there is simply more involved with getting everything up and running. I honestly don't remember if I tested DHCP on the Portainer/Docker setup. It would be logical to me that ports 67 and 68 (DHCP server/client ports) would need to be opened up, and I recall trying that on the non Portainer docker Pi-Hole container and no luck, but none of tutorials I have seen mention needing to open them....

Your thoughts on MACVLAN benefit, as pertains to AdGuard Telos?