You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have setup the single container and adjusted the bottom of pi-hole.conf in an effort to get Docker traffic to resolve.
# Ensure privacy of local IP ranges
#private-address: 192.168.0.0/16
private-address: 169.254.0.0/16
private-address: 172.16.0.0/12
#private-address: 10.0.0.0/8
private-address: fd00::/8
private-address: fe80::/10
# Only give access to recursion clients from LAN IPs
access-control: 127.0.0.1/32 allow
access-control: 192.168.0.0/16 allow
access-control: 172.16.0.0/12 allow
access-control: 10.0.0.0/8 allow
access-control: 172.17.0.1/24 allow
access-control: 192.168.0.0/16 allow
# access-control: fc00::/7 allow
# access-control: ::1/128 allow
For reference when I say Docker traffic I mean my DuckDNS unsuccessfully pings their server, I have to change the containers DNS to 1.1.1.1; Wireguard VPN set to use my PiHole once in network will not resolve any DNS (but I can access everything on the network as usual); even the adlists are failing to update from their sources but I can access them fine through my browser. Anything that shows up as Docker Host in Client (172.17.0.1) fails to resolve DNS. Below shows some of the pings when I VPN in from my phone to test. Even though it says a cached response it never successfully resolved on my phone.
I have setup the single container and adjusted the bottom of pi-hole.conf in an effort to get Docker traffic to resolve.
# Ensure privacy of local IP ranges
#private-address: 192.168.0.0/16
private-address: 169.254.0.0/16
private-address: 172.16.0.0/12
#private-address: 10.0.0.0/8
private-address: fd00::/8
private-address: fe80::/10
For reference when I say Docker traffic I mean my DuckDNS unsuccessfully pings their server, I have to change the containers DNS to 1.1.1.1; Wireguard VPN set to use my PiHole once in network will not resolve any DNS (but I can access everything on the network as usual); even the adlists are failing to update from their sources but I can access them fine through my browser. Anything that shows up as Docker Host in Client (172.17.0.1) fails to resolve DNS. Below shows some of the pings when I VPN in from my phone to test. Even though it says a cached response it never successfully resolved on my phone.
Environmentals:
FTLCONF_LOCAL_IPV4=192.168.0.107
TZ=America/Chicago
WEBTHEME=default-darker
REV_SERVER=${REV_SERVER:-false}
REV_SERVER_TARGET=${REV_SERVER_TARGET}
REV_SERVER_DOMAIN=${REV_SERVER_DOMAIN}
REV_SERVER_CIDR=${REV_SERVER_CIDR}
PIHOLE_DNS_=127.0.0.1#5335
DNSSEC=false
DNSMASQ_LISTENING=single
PATH=/opt/pihole:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
phpver=php
PHP_ERROR_LOG=/var/log/lighttpd/error-pihole.log
IPv6=true
S6_KEEP_ENV=1
S6_BEHAVIOUR_IF_STAGE2_FAILS=2
S6_CMD_WAIT_FOR_SERVICES_MAXTIME=0
FTL_CMD=no-daemon
DNSMASQ_USER=pihole
QUERY_LOGGING=false
Thanks for any help.
The text was updated successfully, but these errors were encountered: