I tried a few thing but the DNS/FTL keep dying on me after a few hours... When it's up it work as per design. Can't figure out as to why it keep quitting on me.
DNS/FTL should stay up
DNS/FTL died after a few hours
Your Pi-Hole seems to have quite a lot of activity, which may be exhausting the system resources:
[2020-02-20 00:12:17.908 12009] Resizing "/FTL-queries" from 439812096 to 440008704
What is the output of these commands from the Pi terminal:
echo ">stats" | nc localhost 4711
echo ">top-clients" | nc localhost 4711
echo ">top-domains" | nc localhost 4711
echo ">top-ads" | nc localhost 4711
I did more troubleshooting and I notice a lot of back and forth between my router and the pihole when I had on Conditional Forwarding... I turn it off and it seam to be fine ever since... over 16 hrs and it's still up.
My config was my router is a USG PRO with Primary DNS is the Pihole and Sec is 8.8.8.8. My Pihole is set to 8.8.8.8 and 1.1.1.1.
Since I turn off Conditional Forwarding no more issue... Is this a bug?
Here the display, but I still have conditional formatting turn off....
pi@Rasp-ADSBlocker:~ $ echo ">stats" | nc localhost 4711
domains_being_blocked 125296
dns_queries_today 15822
ads_blocked_today 4728
ads_percentage_today 29.882442
unique_domains 1273
queries_forwarded 8998
queries_cached 2096
clients_ever_seen 2
unique_clients 2
dns_queries_all_types 15822
reply_NODATA 709
reply_NXDOMAIN 1240
reply_CNAME 5840
reply_IP 7324
privacy_level 0
status enabled
---EOM---
^C
pi@Rasp-ADSBlocker:~ $ echo ">top-clients" | nc localhost 4711
0 15773 192.168.1.1
1 51 127.0.0.1 localhost
---EOM---
^C
pi@Rasp-ADSBlocker:~ $
pi@Rasp-ADSBlocker:~ $ echo ">top-domains" | nc localhost 4711
0 1358 ping.ubnt.com
1 887 ips1.unifi-ai.com
2 531 fw-update.ubnt.com
3 512 api-global.netflix.com
4 438 xa.x7.servers-v6.ddns.softether-network.net.localdomain
5 383 get-my-ip-v6.ddns.softether-network.net.localdomain
6 264 push.prod.netflix.com
7 257 connectivity-check.ubuntu.com
8 186 api.us-east-1.aiv-delivery.net
9 165 wpad.localdomain
---EOM---
^C
pi@Rasp-ADSBlocker:~ $ echo ">top-ads" | nc localhost 4711
0 513 s.amazon-adsystem.com
1 406 aax.amazon-adsystem.com
2 228 app-measurement.com
3 224 sdk-ios.ad.smaato.net
4 223 fls-na.amazon.com
5 201 pagead2.googlesyndication.com
6 201 googleads.g.doubleclick.net
7 190 mobile.pipe.aria.microsoft.com
8 156 mobile-static.adsafeprotected.com
9 133 aax-us-east.amazon-adsystem.com
---EOM---
You do not want a second (non Pi-Hole) DNS server here. Clients will be free to use either or both of the DNS available, and some DNS traffic may bypass Pi-Hole.
Not a bug. Depending on the router and network traffic, conditional forwarding can generate a lot of loop traffic.
No problems noted here.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.