Nope, SME uses isc-dhcpd and dnscache (from djbdns)
Yes; thanks; I (finally) figured that out. For some reason I regularly confuse dnscache and dnsmasq, waste 30 - 45 minutes looking for the wrong stuff, then figure out my mistake.
Since I have a pi at home, I went ahead and installed pi-hole on it for testing.
I reconfigured SME to use the pi-hole server (192.168.200.18) as the domain-name-server in dhcpd.conf as follows:
mkdir -p /etc/e-smith/templates-custom/etc/dhcpd.conf
cd /etc/e-smith/templates-custom/etc/dhcpd.conf
echo -e " option domain-name-servers\t{ \$dhcpd{'DomainNameServers'} || \$LocalIP };" > 25DomainNameServers
#
# replace 192.168.200.18 with the LAN IP of your pi-hole server...
config setprop dhcpd DomainNameServers 192.168.200.18
expand-template /etc/dhcpd.conf
sv t dhcpd
Note that the code above for creating 25DomainNameServers includes some escape chars.
Here is what the file should look like when you're done:
option domain-name-servers { $dhcpd{'DomainNameServers'} || $LocalIP };
If things go wrong, these customizations can be completely removed using:
'rm' /etc/e-smith/templates-custom/etc/dhcpd.conf/25DomainNameServers
expand-template /etc/dhcpd.conf
sv t dhcpd
I've created an NFR in bugzilla to make "DomainNameServers" a standard db entry for dhcpd:
Bug 10657 - NFR: Template dhcpd.conf domain-name-servers setting