Strange pihole result

Help Synology
1

been running pihole on my Nas for a while using the YAML file below. I also run TailScale on the same nas which is set as myexit node, “was told thast would send all inquiries through pihole. Lately I haven’t notice issues other than the blocked percentage is below 1 percent when it was way higher before, like 30-50%. If included the YAML I’m using below along with a screen grab of the pihole dashboard.

Also, could someone explain how to get the diagnostics (Pihole d) through a Synolgy nas?

TIA

pihole dash
pihole dash1408×700 116 KB

More info at GitHub - pi-hole/docker-pi-hole: The official Pi-hole Docker image from pi-hole.net · GitHub and https://docs.pi-hole.net/

services:

pihole:

container_name: pihole

image: pihole/pihole:latest

ports:

  # DNS Ports

  - "53:53/tcp"

  - "53:53/udp"

  # Default HTTP Port

  - "8080:443/tcp" 

  # Default HTTPs Port. FTL will generate a self-signed certificate

  - "8443:443/tcp"

  # Uncomment the line below if you are using Pi-hole as your DHCP server

  #- "67:67/udp"

  \# Uncomment the line below if you are using Pi-hole as your NTP server

  #- "123:123/udp"

environment:

  \# Set the appropriate timezone for your location ( https://en.wikipedia.org/wiki/List_of_tz_database_time_zones ), e.g:

  TZ: 'US/Eastern'

  \# Set a password to access the web interface. Not setting one will result in a random password being assigned

  FTLCONF_webserver_api_password: 'x'

  \# If using Docker's default \`bridge\` network setting the dns listening mode should be set to 'ALL'

  FTLCONF_dns_listeningMode: 'ALL'

\# Volumes store your data between container upgrades

volumes:

  \# For persisting Pi-hole's databases and common configuration file

  - './etc-pihole:/etc/pihole'

  \# Uncomment the below if you have custom dnsmasq config files that you want to persist. Not needed for most starting fresh with Pi-hole v6. If you're upgrading from v5 you and have used this directory before, you should keep it enabled for the first v6 container start to allow for a complete migration. It can be removed afterwards. Needs environment variable FTLCONF_misc_etc_dnsmasq_d: 'true'

  #- './etc-dnsmasq.d:/etc/dnsmasq.d'

cap_add:

  \# See https://github.com/pi-hole/docker-pi-hole#note-on-capabilities

  \# Required if you are using Pi-hole as your DHCP server, else not needed

  - NET_ADMIN

  \# Required if you are using Pi-hole as your NTP client to be able to set the host's system time

  - SYS_TIME

  \# Optional, if Pi-hole should get some more processing time

  - SYS_NICE

restart: unless-stopped
2

Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from your Docker host machine's CLI:

docker exec -it <pihole-container-name-or-id> pihole -d

where you substitute <pihole-container-name-or-id> as required.

Alternatively, login to your Pi-hole container's shell and run the following command from within your Pi-hole container:

pihole -d
3

not sure how to accomplish what you asked.

4

Which part of the directions were you not able to follow? Two methods for generating a debug log and obtaining a token were presented.

5

Access the NAS using a terminal window, then execute the command suggested by Bucking_Horn:

Since your compose file shows the container name is pihole, the command is:

docker exec -it pihole pihole -d
6

Found below but you can leave the port for the SSH service on default 22 in your home network:

7

https://tricorder.pi-hole.net/4tFxXqKa/

8

Hey guy, I’d really appreciate any help. HI read where the link is erased after 48 hours, so II created another here:

https://tricorder.pi-hole.net/Pdd8kV1H/

Pihole Diagnostics.

9

That drop from 30-50% to basically nothing suggests your DNS queries probably aren't going through Pi-hole at all. Setting Tailscale as an exit node is different from pointing your clients to Pi-hole as the DNS server — might be worth checking where your queries are actually resolving.