Hi there, I’ve just done the switch from NextDNS to PiHole. Simply because I want to test it out + self-host my DNS. I set up PiHole+Unbound two days ago, and yesterday the amount of “Queries blocked” was much higher that it is now. But this morning the number was down back to 100ish. Is this normal behaviour, is it supposed to reset the counter? I’d rather it didn’t. Let me know if this is my fault or a setting I’ve managed to miss.

Thank you.

  • @sazey@lemmy.worldEnglish
    6•2 months ago

    Although not exactly what you are looking for (ie custom counters on the landing page), you can view counters you are after on another page under ‘Long-term Data > Query Log’

  • @RandomPancake@lemmy.worldEnglish
    18•2 months ago

    Make sure you’re also blocking all other outbound DNS at your firewall. Many “smart” devices (and presumably some apps, though I have no way to check this) are hard coded to use 8.8.8.8 regardless of what DCHP says to use.

  • SolidGrueEnglish
    36•2 months ago

    That counter, I believe, for the last 24 hours. It will fluctuate up and down across your active daily periods

    • Sunny' 🌻OPEnglish
      6•2 months ago

      Oh okay good to know, is there a way to change this though? Would be “cooler” to see the total amount imo.

      • SolidGrueEnglish
        14•2 months ago

        So, like a running sum? No, I don’t think so, not in Pi-hole at least.

        Pi-hole does have an API you could scrape, though. A Prometheus stack could track it and present a dashboard that shows the summation you want. There are other stats you could pull as well. This is a quick sample of what my home assistant integration sees

          • SolidGrueEnglish
            17•2 months ago

            Ah, well if you know differently then please do share with the rest of us? I think the phrasing in my post makes it pretty clear I was open to being corrected.

    • SolidGrueEnglish
      13•2 months ago
      #### MAXLOGAGE=24.0
Up to how many hours of queries should be imported from the database and logs? Values greater than the hard-coded maximum of 24h need a locally compiled `FTL` with a changed compile-time value.

      I assume this is the setting you are suggesting can extend the query count period. It still will only give you the last N hours’ worth of queries, which is not what OP asked. I gather OP wants to see the cumulative total of blocked queries over all time, and I doubt the FTL database tracks the data in a usable way to arrive at that number.

        • SolidGrueEnglish
          3•2 months ago

          No worries, the other poster was just wasn’t being helpful. And/or doesn’t understand statistics & databases, but I don’t care to speculate on that or to waste more of my time on them.

          The setting above maxes out at 24h in stock builds, but can be extended beyond that if you are willing to recompile the FTL database with different parameters to allow for a deeper look back window for your query log. Even at that point, a second database setting farther down that page sets the max age of all query logs to 1y, so at best you’d get a running tally of up to a year. This would probably at the expense of performance for dashboard page loads since the number is probably computed at page load. The live DB call is intended for relatively short windows vs database lifetime.

          If you want an all-time count, you’ll have to track it off box because FTL doesn’t provide an all-time metric, or deep enough data persistence. I was just offering up a methodology that could be an interesting and beneficial project for others with similar needs.

          Hey, this was fun. See you around.

          • Sunny' 🌻OPEnglish
            1•2 months ago

            I will try that one next to see how it compares. Thanks for letting me know 👍