Pihole is running on a Raspberry Pi 4 with 4GB RAM, attached via Cat6 Eth cable to ISP router (Fritzbox 7590). ADSL is a 200/30 Mbit FTTC working very well. Upstream DNS is Google's 8.8.8.8 as I measured to be consistently slightly faster than 1.1.1.1 or opendns.
Pihole usually works like a charm, filters about 12% of the IPs and all clients work very well with it. For reasons I do not understand SOMETIMES (like 3-4 times a day) the browsers stall in the "resolving" state for 10 maybe even 15 seconds and after that long wait usually resolve and the rest of the protocls load pages correctly.
Thank you VERY much for the wonderful software and for helping me find if I did some misconfiguration or explanation.
Maybe you've created a DNS loop somewhere.
What upstream DSN server(s) are configured on Fritzbox ?
Usually these upstream DNS settings can be found in the Internet or WAN section of the router settings.
Yes this happens on my mac as well as my wife's mac and iphone.
Tailing the logs to catch the bug is very hard since this might happen only every few hours
dmesg | grep -i voltage does not return anything.
filesystems are all quite empty
bob@rpibuster:~ $ free -h
total used free shared buff/cache available
Mem: 3.9Gi 763Mi 1.2Gi 18Mi 1.9Gi 3.0Gi
Swap: 99Mi 0B 99Mi
bob@rpibuster:~ $ uptime
10:26:25 up 16:43, 1 user, load average: 1.31, 2.12, 2.08
bob@rpibuster:~ $ timedatectl
Local time: Fri 2020-05-01 10:27:35 CEST
Universal time: Fri 2020-05-01 08:27:35 UTC
RTC time: n/a
Time zone: Europe/Rome (CEST, +0200)
System clock synchronized: yes
NTP service: inactive
RTC in local TZ: no
bob@rpibuster:~ $ ip r | grep default
default via 192.168.1.254 dev eth0 proto dhcp metric 100
default via 192.168.1.254 dev eth0 src 192.168.1.18 metric 202
Have you configured "Conditional forwarding" in the Pi-hole settings and how is this configured ?
Do you run anything else on the Pi besides Pi-hole ?
Intermittent issues are always the hardest to troubleshoot.
I would still advice to check those logs when the issue occurs.
Keep an SSH session running or on console.
Or use the less command to browse those logs.
I am puzzled by the short uptime ... this Pi4 is always on (save for when electricity loss in the house) ... ideas on how to look for potential accidental reboots in the logs?
Conditional forwarding is disabled; Upstream DNS in pihole is only Google and IPV4; also have never forward non-FQDN and private IP ranges enabled; DNSSEC and Conditional forwarding are disabled;
Fritzbox gets its DNS server upstream delivered by the ISP (Fastweb Italy)
Choice is :"Use DNSv4 servers assigned by the internet service provider" (recommended)
and they are
Server DNS preferito: 85.18.200.200.
Server DNS alternativo: 89.97.140.140.
While doing a tail -f pihole.log not witnessed a slow resolution
Looks like you dont have a loop.
If you know the Pi is up for 16 hours, check same logs as posted previously around that time.
EDIT: Ow sometimes the logs rotate after reboot so syslog becomes syslog.1 etc.
And logs whith extension .gz can be viewed with:
bob@rpibuster:~ $ sudo journalctl --no-pager -u network-manager | tail -20
-- Logs begin at Thu 2020-04-30 17:17:01 CEST, end at Sat 2020-05-02 10:19:52 CEST. --
-- No entries --
bob@rpibuster:~ $ hostnamectl | tail -3
Operating System: Raspbian GNU/Linux 10 (buster)
Kernel: Linux 4.19.97-v7l+
Architecture: arm
Disabled network manager, rebooted and so far system seems ok.
Suggestions for a next step?
Thank you very very much for your help my unknown virtual friend.
Next step, fingers crossed.
But I suspect those two network manglers running simultaneously was causing the issue.
One still configured to acquire IP details via DHCP and the other trying to keep a static IP.
Many thanks to you too and all others in medical care!
