Pi-hole randomly stops resolving

Help
1

Please follow the below template, it will help us to help you!

If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx instead of lighttpd, or there is some other aspect of your install that is customised) - please use the Community Help category.

Expected Behaviour:

Latest Pi-hole version running on Debian 10 VM
Ethernet gigabit attached

Actual Behaviour:

Pi-hole randomly stops to resolve my queries and the only way to solve this issue is a reboot.
Thank you

Debug Token:

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

2

Also, note that spaces are illegal in host names, FTL replaced them by ~ and logged this here:

   [2021-02-21 09:17:16.112 12543M] INFO: FTL escaped 3 characters in "home~assistant~bridge~523bf1._hap._tcp.local"

However, this will not have caused the issues you're seeing.

Please add

DEBUG_ALL=true

to the file /etc/pihole/pihole-FTL.conf (create if it does not exist) and run

pihole restartdns

Next time the issues happens, please include the last lines of /var/log/pihole-FTL.log and /var/log/pihole.log. This should help us getting a better picture of where/why exactly the issue happens.

Sorry for the inconvenience and thanks for your assistance!

3

Hello DL6ER,

It's happening right now...

I enabled the DEBUG_ALL and there are my logs files:
piholelogs.zip (3.7 KB)

Debug token: https://tricorder.pi-hole.net/1im2yxd24f

Thanks a lot

4

Something isn't quite right with these logs.

pihole-FTL.log end in the middle of the process:

[2021-02-25 18:08:16.876 6839M] Waiting for lock in _FTL_CNAME() (/root/project/src/dnsmasq_interface.c:342)
[2021-02-25 18:08:16.876 6839M] Obtained lock for _FTL_CNAME() (/root/project/src/dnsmasq_interface.c:342)
[2021-02-25 18:08:16.876 6839M] fra-efz.ms-acdc.office.com is known as not to be blocked

pihole.log shows that this query worked as expected:

Feb 25 18:08:16 dnsmasq[6839]: reply outlook.ha.office365.com is <CNAME> (/root/project/src/dnsmasq/cache.c:493)
Feb 25 18:08:16 dnsmasq[6839]: reply outlook.ms-acdc.office.com is <CNAME> (/root/project/src/dnsmasq/cache.c:493)
Feb 25 18:08:16 dnsmasq[6839]: reply FRA-efz.ms-acdc.office.com is 52.97.200.130 (/root/project/src/dnsmasq/cache.c:493)
Feb 25 18:08:16 dnsmasq[6839]: reply FRA-efz.ms-acdc.office.com is 40.101.80.18 (/root/project/src/dnsmasq/cache.c:493)
Feb 25 18:08:16 dnsmasq[6839]: reply FRA-efz.ms-acdc.office.com is 52.97.188.66 (/root/project/src/dnsmasq/cache.c:493)

... and that FTL continued to work afterwards by serving more queries, like:

Feb 25 18:10:32 dnsmasq[6839]: query[A] vortex.data.microsoft.com from 192.168.1.219 (/root/project/src/dnsmasq/forward.c:1631)
Feb 25 18:10:32 dnsmasq[6839]: forwarded vortex.data.microsoft.com to 84.200.69.80 (/root/project/src/dnsmasq/forward.c:600)

Next, time please also note down the time where you're seeing the issue. Somehow your two log files don't match in this sample.

edit Just to make this clear: We need the log when the issue is ongoing. Not after a restart (where it is working again). Just in case this is what you did here.

5

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.