DNSMASQ_WARN warning spam

Help docker
1

Hi there, i have been using pihole with docker and dhcp helper for a few days now.

Everything seems to be working fine (it seems to get a very little dns query from my devices but i will have to investigate it later...), but i get spammed with those two messages:

no address range available for DHCP request via eth1
no address range available for DHCP request via eth0

My compose file is almost identical to the one pointed out in the docs (here)

I have this separate file (99-second-DNS.conf) as described in the post linked above, and i added those two lines to try to fix the problem. (192.168.1.2 is IP of my raspberry on host network)

dhcp-option=option:dns-server,192.168.1.2
no-dhcp-interface=eth0
no-dhcp-interface=eth1

Is there anything else to do in orded to fix this issue?

https://tricorder.pi-hole.net/WJDUIosw/ this is my debug log

2

I suspect that those messages may be triggered by the very lines you've added.

But before we start investigating this:
When operating a dockered Pi-hole as DHCP server, it may be easier to have the container run in Docker's host or macvlan network mode, as that would eliminate the need for a DHCP relay, see also Docker DHCP and Network Modes.

Is there a specific reason that you opted to stick with Docker's brigde mode (e.g. other containers on the same bridge network that your Pi-hole would somehow depend on)?

3

I suspect that those messages may be triggered by the very lines you've added.

Those message were already present before i added the two lines. It was just a try to fix the problem.

I can't use host mode because the pihole's web interface is running behind a reverse-proxy (nginx) in the same docker network.

4

Another problem i encountered:
a lot of devices are receiving DHPC leases where the DNS Server is 8.8.8.8 and not my local raspberry IP. The log is the same as before, i have not touched anything since then.

5

That would indicate that those devices didn't acquire their lease through Pi-hole's DHCP server.

Please share your docker-compose or docker run file.

6

this is my docker compose:

version: "3"
services:
  pihole:
    image: pihole/pihole:latest
    hostname: pihole
    ports:
      - "53:53/tcp"
      - "53:53/udp"
    restart: unless-stopped
    cap_add:
        - NET_ADMIN
    dns:
      - 127.0.0.1
      - 1.1.1.1
    environment:
      ServerIP: 192.168.1.2
      DNS1: 1.1.1.1
      DNS2: 1.0.0.1
      VIRTUAL_HOST: pi.hole
      DNSMASQ_LISTENING: all
      WEBPASSWORD: *****
    volumes:
      - '/home/pi/docker/pihole/pihole/:/etc/pihole/'
      - '/home/pi/docker/pihole/dnsmasq.d/:/etc/dnsmasq.d/'
    depends_on:
      - dhcphelper
    networks:
      backend: 
        ipv4_address: '172.31.0.100'
      webnet: {}

  dhcphelper:
    image: dhcp-helper:latest
    restart: unless-stopped
    network_mode: "host"
    command: -s 172.31.0.100
    cap_add:
      - NET_ADMIN

networks:
  backend:
    ipam:
      config:
        - subnet: 172.31.0.0/16
  webnet:
    name: webnet
    external: true

webnet is the docker network with the reverse-proxy