Pihole V6 fresh instances are deleting the logs every 2 days

[Bucking_Horn]

@Whisky

I checked the official documentation, I could not find a “here, there are all the parameters you can use”

pihole.toml contains those parameters.
It is fully documented, and beyond editing it, there are quite a few ways to change configurations options, as detailed in Introducing Pi-hole v6 :

@PromoFaux

3. Consolidated Configuration Files

We’ve streamlined configuration management by consolidating multiple settings files into a single, richly commented toml file, making it easier to manage and understand your settings. If you are migrating from v5, your existing configurations will be migrated automatically into this file. It can be found at /etc/pihole/pihole.toml

Configuration can be set in multiple ways:

• Directly editing the toml file
• Via the command line, e.g pihole-FTL --config dns.upstreams 8.8.8.8
• Using the API
• Via the web interface (which uses the API )
• Via environment variables named, e.g FTLCONF_dns_upstreams=8.8.8.8

If setting via environment variables, it should be noted that this effectively makes the setting read-only, as the environment variable will always force the value to match itself. This is the preferred way to configure FTL in the docker container.

---

@Whisky

3. Unfortunatelly, V6 no longer has a dedicated file for the local DNS so you must edit pihole.tom to add them, meaning, if you are doing a restore and the configuration might be the problem, you have to manually edit that file.

You'd had the choice to manually edit files in either case.
With Pi-hole 5, there have been two files to edit, one for A/AAAA and for CNAME records, whereas you only have to edit one file (pihole.toml) in Pi-hole 6.

And just as Pi-hole 5, Pi-hole's UI has a panel for changing Local DNS records, via Settings | Local DNS records.

@Whisky

I swear, I have not changed that even tho it says CHANGED.

@Whisky

3. Restore the backup

That could suggest that your teleporter backup contains those exclusions.
You could check your backup file yourself, or upload it and provide the token for us to take a look:

cat /path/to/pi-hole-teleporter_JJJJ-MM-TT_hh-mm-ss.tar.gz | sudo pihole tricorder

where you substitute /path/to/pi-hole-teleporter_JJJJ-MM-TT_hh-mm-ss.tar.gz with your actual teleporter file as appropriate.