-
Notifications
You must be signed in to change notification settings - Fork 296
Open
Description
Problem Description:
The Pi-hole DNS server within the mpgirro/docker-pihole-unbound container fails to listen on network interfaces on port 53, resulting in "connection refused" errors when attempting to resolve DNS queries from the host. Unbound, however, functions correctly on 127.0.0.1:5335.
Observed Behavior:
netstat -tulnp | grep ":53"inside the container consistently shows:(Only Unbound listening, notcp 0 0 127.0.0.1:5335 0.0.0.0:* LISTEN - udp 0 0 127.0.0.1:5335 0.0.0.0:* -0.0.0.0:53or:::53for dnsmasq).dig @<your_container_ip> pi.holefrom the host (e.g.,dig @192.168.0.33 pi.hole) results in:;; communications error to <your_container_ip>#53: connection refused ;; no servers could be reached- The file
/etc/pihole/dnsmasq.confinside the container consistently contains the lineexcept-interface=nonexisting. - This problematic line automatically reappears in
/etc/pihole/dnsmasq.confafter the container is restarted from Unraid. - The
FTL.logrepeatedly shows:CRIT: Error in dnsmasq configuration: bad port at line 33 of /etc/pihole/dnsmasq.conf(though line 33 in the file is a comment).
Expected Behavior:
Pi-hole (dnsmasq) should listen on port 53 on the configured network interfaces (e.g., br0 / 0.0.0.0 for IPv4 and :: for IPv6) to serve DNS queries, as intended by FTLCONF_dns_listeningMode=all.
Steps to Reproduce:
- Run the
mpgirro/docker-pihole-unboundcontainer on Unraid. - Set environment variables:
PIHOLE_INTERFACE=br0FTLCONF_dns_listeningMode=allDNS1=127.0.0.1#5335TZ=<your_timezone>WEBPASSWORD=<your_secure_password>DNSSEC=true(if applicable)REV_SERVER=true,<your_local_subnet>,<your_router_ip>#53,lan(if applicable)- (List all other environment variables you are using for the container setup).
- Observe
netstat -tulnp | grep ":53"andcat /etc/pihole/dnsmasq.confafter container startup/restart.
Environment:
- Host OS: Unraid 7.1.3
- Docker Image:
mpgirro/docker-pihole-unbound:latest(or specific tag if used) - Pi-hole FTL Version: v6.2.2 (from
FTL.log)
Request:
Please provide guidance on how to prevent except-interface=nonexisting from being added to dnsmasq.conf, or if this is a bug, please consider a fix in a future image release.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels