The issue I am facing:
Hello
I've tried to white-list the subdomain image.ard.de
, but this neither works by adding image.ard.de
directly to the white-list, nor by the Pi-hole generated reg-ex (\.|^)ard\.de$
. A client-side ping
renders in both cases:
ping image.ard.de
PING image.ard.de (0.0.0.0): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host
Request timeout for icmp_seq 0
On the Pi(-hole), same pings render:
pi@raspberrypi:~ $ ping ard.de
PING ard.de (34.120.237.106) 56(84) bytes of data.
64 bytes from 106.237.120.34.bc.googleusercontent.com (34.120.237.106): icmp_seq=1 ttl=59 time=10.7 ms
64 bytes from 106.237.120.34.bc.googleusercontent.com (34.120.237.106): icmp_seq=2 ttl=59 time=11.0 ms
^C
--- ard.de ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 3ms
rtt min/avg/max/mdev = 10.680/10.835/10.990/0.155 ms
pi@raspberrypi:~ $ ping image.ard.de
PING image.ard.de (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.131 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.095 ms
64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.085 ms
64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.090 ms
64 bytes from localhost (127.0.0.1): icmp_seq=5 ttl=64 time=0.130 ms
^C
--- image.ard.de ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 178ms
rtt min/avg/max/mdev = 0.085/0.106/0.131/0.021 ms
I am aware, that image.ard.de
is on these black-lists, yet anything white-listed should be exempt from blocking:
Exact match found in regex whitelist
(\.|^)ard\.de$
Exact matches for image.ard.de found in:
- https://v.firebog.net/hosts/Easyprivacy.txt
- https://v.firebog.net/hosts/RPiList-Malware.txt
- http://sbc.io/hosts/alternates/fakenews-gambling-porn/hosts
I am puzzled . What am I doing wrong or, rather, how do I achieve the expected behaviour from Pi-hole?
Maybe off-topic:
Judging by Mike Kuketz' research, there isn't any apparent reason to block image.ard.de
, rendering this entry very likely to be a false positive.
Details about my system:
Pi-hole v5.16.2, FTL v5.22, Web Interface v5.19
Debug log → https://tricorder.pi-hole.net/DUK0hRMk/
What I have changed since installing Pi-hole:
Nothing. Other than that, Pi-hole works fine.