Hi,
i was wondering why sometimes some pages was reachable, so i decided to include a monitoring check for the pihole.
this check, make a dns lookup with the pihole dns server.
the problem is, that the adlist is not loaded or used every time, but i see no reason for it.
In the querie log, i see, that the pihole use external dns servers for resolving it, but normaly he should use the adlist or not?
best regards
Chris
Pi-hole first checks the gravity list to see if a domain should be blocked. If not, it resolves the domain name to an IP using an external DNS server.
For the domain in question run the following command to see if the domain is on your block list:
pihole -q domainname
Hi,
yes it is:
in my first post in the first picture you can see in the monitoring events, that sometimes it is working.
best regards
Chris
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 the Pi-hole host terminal:
pihole -d
or do it through the Web interface:
Tools > Generate Debug Log
Hi,
https://tricorder.pi-hole.net/PQUWUjGR/
thanks for analyse this issue.
status:
best regards
Chris
@ yubiuser
could you find a reason in the debug log, for my issue?
best regards
Chris
The client IP shown in your above screenshots falls into the 172.16.0.0/12, which often suggests a Docker environment (though Docker's default bridge network usually would start with the more specific 172.17.0.0/16 subnet range).
If you were running your Pi-hole in a Docker container, gravity won't be accessible until shortly after container startup.
Similar may be true for a brief period during gravity updates when database is switched from the previous to the updated one.
If gravity is inaccessible, Pi-hole won't be able to determine whether a given domain request should be blocked.
It would depend on your chosen platform and configuration how brief "brief" actually would be.
In a Docker environment on an RPi Zero with a huge gravity database alongside other software like home automation and a media server, switching databases will certainly be slower than on the same Zero dedicated to a bare-metal Pi-hole installation with just the default blocklists exclusively.
That said, a bare-metal Zero is an adequate platform to run Pi-hole in a home network. I've been using that configuration (with a 400k to 500k strong gravity db) for years now, without ever producing any observations like yours - but maybe I was just luckky enough that my network never was busy during gravity updates.
This behaviour can be changed by adding and adjusting the value for REPLY_WHEN_BUSY in pihole-FTL.conf (In case you run a dockered Pi-hole, make sure you have the proper volumes in place.).
Note that by using any other value than the default ALLOW, you will effectively cut your network from DNS resolution until gravity is accessible again.
Please upload a new debug log and share the token.
could you find a reason in the debug log, for my issue?
best regards
Chris
Response to your answer-post:
Since I can't find a solution, no data at all displayed by Pihole, I set the debug function:
[?] ** FINISHED DEBUGGING! **
[?] Would you like to upload the log? [y/N] y
* Using curl for transmission.
[?] Your debug token is: https://tricorder.pi-hole.net/uOYkt9Yy/
[i] Logs are deleted 48 hours after upload.
root@2GB:/home/pi#
Only Chrome gives this error. My other browsers do not, Safari, AD Blocker, Samsung browser.
Translated with www.DeepL.com/Translator (free version)
Hi,
is there still someone who can help me?
best regards
Chris
Hi, no one?
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.
