I only have:
/etc/dnsmasq.d/01-pihole.conf
...there is no such file as:
/etc/dnsmasq.d/99-ipbinding.conf
Does this file need to be created, and the following content placed within it:
except-interface=lo
listen-address=192.168.xx.xx
bind-interfaces
My Pi-hole is on 192.168.0.9, so would I supplement that instead of the xx.xx in the above example?
Additionally, the 01-pihole.conf file explicitly declares the following:
###############################################################################
# FILE AUTOMATICALLY POPULATED BY PI-HOLE INSTALL/UPDATE PROCEDURE. #
# ANY CHANGES MADE TO THIS FILE AFTER INSTALL WILL BE LOST ON THE NEXT UPDATE #
# #
# IF YOU WISH TO CHANGE THE UPSTREAM SERVERS, CHANGE THEM IN: #
# /etc/pihole/setupVars.conf #
# #
# ANY OTHER CHANGES SHOULD BE MADE IN A SEPARATE CONFIG FILE #
# WITHIN /etc/dnsmasq.d/yourname.conf #
###############################################################################
So, I would gather that I'd need to create a new file as guided for the changes to survive and persist beyond any update:
/etc/dnsmasq.d/yourname.conf
Would you agree? Or do I put the 99-ipbinding.conf content into yourname.conf instead? (Obviously, yourname is changed to something meaningful).
The following output for setupVars.conf looks broadly similar to yours and seems setup to me:
$ cat /etc/pihole/setupVars.conf
WEBPASSWORD=
PIHOLE_INTERFACE=eth0
IPV4_ADDRESS=192.168.0.9/24
IPV6_ADDRESS=
QUERY_LOGGING=true
INSTALL_WEB_SERVER=true
INSTALL_WEB_INTERFACE=true
LIGHTTPD_ENABLED=true
BLOCKING_ENABLED=true
DNSMASQ_LISTENING=single
PIHOLE_DNS_1=1.1.1.1
PIHOLE_DNS_2=1.0.0.1
DNS_FQDN_REQUIRED=true
DNS_BOGUS_PRIV=true
DNSSEC=false
CONDITIONAL_FORWARDING=false
But the following output for pihole-FTL.conf is very different to yours:
$ cat /etc/pihole/pihole-FTL.conf
PRIVACYLEVEL=0
You will note it is missing all of the following suggested content:
MAXDBDAYS=2
DBINTERVAL=10.0
DBIMPORT=yes
IGNORE_LOCALHOST=yes
I'm not clear what most of this suggested content does, but I guess I could just add the IGNORE_LOCALHOST line, so that my finished file looks as such:
$ cat /etc/pihole/pihole-FTL.conf
PRIVACYLEVEL=0
IGNORE_LOCALHOST=yes
I absolutely cannot break this, as it is a critical 24/7 system, which also happens to be running my Pi-hole. Until I'm more confident with this, I'm just going to have to disable the Pi-hole completely and bypass it at the router, until I can be sure of a way to stop the local Pi-hole from using itself for its own DNS resolution.
Thanks.