pi@raspberrypi:~ $ pihole status
[✓] DNS service is running
[✓] Pi-hole blocking is Enabled
pi@raspberrypi:~ $ nslookup http://www.heise.de IP Pihole
Server: IP Pihole
Address: IP Pihole
Non-authoritative answer:
Name: http://www.heise.de
Address: 193.99.144.85
Name: http://www.heise.de
Address: 2a02:2e0:3fe:1001:7777:772e:2:85
Wenn ich die Blocklisten aktualisiere bekomme ich auch fie folgenden Meldungen.
[i] Target: raw.githubusercontent.com (hosts) [✗] Status: Connection Refused [✗] List download failed: using previously cached list
[i] Target: mirror1.malwaredomains.com (justdomains) [✗] Status: Connection Refused [✗] List download failed: using previously cached list
[i] Target: sysctl.org (hosts) [✓] Status: No changes detected
[i] Target: s3.amazonaws.com (simple_tracking.txt) [✗] Status: Connection Refused [✗] List download failed: using previously cached list
[i] Target: s3.amazonaws.com (simple_ad.txt) [✗] Status: Connection Refused [✗] List download failed: using previously cached list
[i] Target: hosts-file.net (ad_servers.txt) [✗] Status: Connection Refused [✗] List download failed: using previously cached list
[i] Target: adaway.org (hosts.txt) [✗] Status: Connection Refused [✗] List download failed: using previously cached list
Ich sehe auch dass die Anfragen beim Pi hole landen.