Installed Pihole with docker on synology with the lastest update.
but something is worng, because nothing is blocked. maybe its a dns error, but I tried everything and I cant figure out how to solve it.
Debug token: https://tricorder.pi-hole.net/I5Q6YD7F/
thanks
Your Pi-hole host has two active (virtual) network interfaces, each configured for a different subnet:
*** [ DIAGNOSING ]: Network interfaces and addresses
16: eth1@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default
inet 192.168.178.199/24 brd 192.168.178.255 scope global eth1
valid_lft forever preferred_lft forever
17: eth0@if18: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
inet 192.168.2.2/24 brd 192.168.2.255 scope global eth0
valid_lft forever preferred_lft forever
While your Pi-hole is configured for the latter 192.168.2.2, your router is handing out yet another address as DNS server:
*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
Scanning all your interfaces for DHCP servers
* Received 548 bytes from eth1:192.168.178.1
DHCP options:
Message type: DHCPOFFER (2)
dns-server: 192.168.178.60
As far as can be deduced from the debug log, that .60 is neither asscoiated to Pi-hole nor its host machine, which would leave your clients talking to a potentially non-existing IP for DNS.
The IP distributed as local DNS server via DHCP should match the one that your Pi-hole is configured for. You should adjust your router's copnfiguration accordingly.
Furthermore, your debug log reports Pi-hole's required ports to be already taken:
*** [ DIAGNOSING ]: Ports in use
[✗] udp:0.0.0.0:53 is in use by (https://docs.pi-hole.net/main/prerequisites/#ports)
[✗] udp:*:53 is in use by (https://docs.pi-hole.net/main/prerequisites/#ports)
[✗] tcp:127.0.0.1:4711 is in use by (https://docs.pi-hole.net/main/prerequisites/#ports)
[✗] tcp:0.0.0.0:80 is in use by (https://docs.pi-hole.net/main/prerequisites/#ports)
[✗] tcp:0.0.0.0:53 is in use by (https://docs.pi-hole.net/main/prerequisites/#ports)
[✗] tcp:[::]:80 is in use by (https://docs.pi-hole.net/main/prerequisites/#ports)
[✗] tcp:[::]:53 is in use by (https://docs.pi-hole.net/main/prerequisites/#ports)
That would suggest that DNS requests are handled by some unknown DNS resolver on that machine.
This is further supported by your debug log showing that DNS resolution is availabe, but no filtering is applied at all:
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] besticam.blogspot.no is blogspot.l.googleusercontent.com.
142.250.74.193 on lo (127.0.0.1)
[✓] besticam.blogspot.no is blogspot.l.googleusercontent.com.
142.250.74.193 on eth1 (192.168.178.199)
[✓] besticam.blogspot.no is blogspot.l.googleusercontent.com.
142.250.74.193 on eth0 (192.168.2.2)
[✓] doubleclick.com is 172.217.18.110 via a remote, public DNS server (8.8.8.8)
You've got to adjust your Synology's configuration to run only Pi-hole as DNS resolver.