pihole.toml
is your one-stop shop for configuring all aspects of your (bare metal) Pi-hole. It can be updated by many different means (see Introducing Pi-hole v6), and it combines various settings previously strewn over different config files in v5 (like setupVars.conf, pihole-FTL.conf and /etc/dnsmasq.d/*).
You've already quoted me pointing out that pihole-FTL
is a tailored fork of dnsmasq
.
As such, it's inheriting everything from its upstream parent, apart from some DNS portions, which our developers customised to allow for speedy blocking and extra features like regex blocking and deep CNAME inspection.
The paragraph you're quoting specifically mentions a dnsmasq
default.
As far as the DHCP server feature is concerned, pihole-FTL
is identical to dnsmasq
.
Thus, all of dnsmasq
's default's apply. As changing them would require to change dnsmasq
code rather than Pi-hole's, it seems fair to keep that reference to dnsmasq
.
As with v5, pihole-FTL
internally still will read dnsmasq
options from a configuration file in pure dnsmasq
syntax, but to better avoid conflicts, v6 moved this /etc/pihole/dnsmasq.conf
, using pihole.toml
to populate it.