"Disable query logging" not working

[valfr]

In raising this issue, I confirm the following: {please fill the checkboxes, e.g: [X]}

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated.
• The issue I am reporting isn't a duplicate (see FAQs, closed issues, and open issues).

How familiar are you with the the source code relevant to this issue?:

2

Expected behavior:

In admin panel under Settings, clicking on "Disable query logging" should be not logging clients request.

Actual behavior:

clients request are still logged, under dashboard we see all requests

Steps to reproduce:

Upgrading with 5.1.1, clicking on "Disable query logging"

Debug token provided by uploading pihole -d log:

n8c1ehirdr

[valfr]

Hello,
After checking "no query instructions" are correctly applied to files /etc/pihole/setupVars.conf & /etc/dnsmasq.d/01-pihole.conf.
However logging is still available ...

[queeup]

Same here. I can't disable query logging.

[queeup]

My sdcard wearing out. Please do something about it.

[dschaper]

Buy a less crappy SDCard.

[jfb-pihole]

Queries are logged in two places.
(1) The dnsmasq log at /var/log/pihole.log. This is controlled by the "query logging" toggle.
(2) The long term database at /etc/pihole/pihole-FTL.db. Logging to this database is controlled by your privacy settings and your setting for MAXDBDAYS in file /etc/pihole/pihole-FTL.conf. Data from the long term database is used to repopulate the query log on FTL restart. If you disable the database but don't increase your privacy settings, within 24 hours the query log will be fully repopulated and the information stored in memory only.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Please comment or update this issue or it will be closed in 5 days.

[yubiuser]

This is not an issue about a malfunction but about interpreting the button. It's basically a duplicate of #1151