I just did a test but the configuration seems to be ignored and it keeps listening on 0.0.0.0
For completeness this is the conf file:
root@vps:~# cat /etc/dnsmasq.d/02-pihole-my.conf listen-address=::1,127.0.0.1,10.10.0.1 root@vps:~# ls -la /etc/dnsmasq.d/ total 60 drwxr-xr-x 2 root root 4096 Aug 16 12:27 . drwxr-xr-x 83 root root 45056 Aug 14 19:07 .. -rw-r--r-- 1 root root 1522 Aug 14 19:07 01-pihole.conf -rw-r--r-- 1 root root 64 Aug 16 12:27 02-pihole-my.conf
Actually I used the "listen-address=" directive on previous pihole versions to achieve my goal. On v4.0, however, the standard dnsmasq installation seems to be dropped and embedded in pihole-FTL. In fact I totally uninstalled dnsmasq from the system and pihole set-up does not install it anymore.
Moreover pihole-FTL seems to read only its dedicated conf file (no mention of dnsmasq config files in logfiles):
root@vps:~# egrep 'conf' /var/log/pihole*.log /var/log/pihole-FTL.log:[2018-08-16 12:28:25.689] Starting config file parsing (/etc/pihole/pihole-FTL.conf) /var/log/pihole-FTL.log:[2018-08-16 12:28:25.689] Finished config file parsing /var/log/pihole-FTL.log:[2018-08-16 12:28:25.690] Successfully accessed setupVars.conf /var/log/pihole-FTL.log:[2018-08-16 12:30:24.137] Starting config file parsing (/etc/pihole/pihole-FTL.conf) /var/log/pihole-FTL.log:[2018-08-16 12:30:24.138] Finished config file parsing /var/log/pihole-FTL.log:[2018-08-16 12:30:24.148] Successfully accessed setupVars.conf root@vps:~# egrep '/etc/dnsmasq' /var/log/pihole*.log root@vps:~#
Was it too early for me to switch to v4.0?