Please follow the below template, it will help us to help you!
Expected Behaviour:
Pihole runs fine, until it get queries from the following sites:
1st: current.cvd.clamav.net
2nd: fusion.tvaddons.ag
3rd: default._domainkey.flafnine.com
All this caused a "Resizing /FTL-queries" and stopped the FTL service and I had to reinstall the system from the beginning (in total 3 times now). I blacklisted the sites, but it did not help. I could not even find out, which client caused the queries. What can I do?
Thx for your support, oliaros
This appears to be the root of the problem. One or more clients is making a significant number of queries and these queries are stored in the long term database and some in memory. This overloads the memory and is likely causing the problems you see.
You can run these commands in the Pi terminal to see the top domains and the top requesting client.
@jfb ,
sorry for the late answer, I had to setup the system again yesterday and then had to wait, until the huge number of requests happened again. This time the requests go to current.cvd.clamav.net from 192.168.0.1.
As soon as they add this to dnsmasq, we will incorporate it into FTL. I agree with @jfb that this is a clear misbehavior of your router., however, I also see that your chances at getting this fixed are typically rather low on this level.
Just to highlight this: My suggestion to send a mail to the dnsmasq mailing list was honest. This can very well result in the solution you need / want.
Have you looked through the mailing list archive? It's completely indexed and searchable through your search engine of choice. Mind, I'd anyone thinks similarly, things would never get asked.
@all,
thx for the hints. When I started with PiHole v4.2.1 I had exactly the same problems as I have now. Somewhere in the forum it was suggested to use "pihole checkout ftl tweak/overhaul_overTime" to solve a (maybe completely different) problem. As a total newbee I tried it out and the PiHole ran without any problems for 9 days. Then v4.3.1 was announced and after I updated my PiHole the same problems started again. I tried to use the tweak again, but FTL refused start. It would be great if there was an easy way to downgrade to v4.2.1 to get a running system again. But unfortunately all the suggestions in the forum I could not comprehend.
BTW the problems occur even if Pihole is the only client of the router.
@all,
I reinstalled the system with an edge-image from a different source, then I reinstalled PiHole. The output of uname -a is the same as before:
pi@PiHole:~ $ uname -a
Linux PiHole 4.19.42+ #1219 Tue May 14 21:16:38 BST 2019 armv6l GNU/Linux
Something must be different: PiHole runs like a charme now, no huge number of requests any more.
I hope it stays like this.
Regards and thanks to all of you.
oliaros