New pihole v6 install on a freshly built rpi4, all this afternoon. I am not able to get any of the entries I have put in /etc/dnsmasq.d/10-custom.conf file to resolve. I am using Pihole v6 with unbound all running on the same rpi. I have the box checked to enable misc.etc_dnsmasq_d set to true.
I have another pi-hole install, running on an ubuntu host, with the same versions of pi-hole, and same settings, which is working fine with dnsmasq, I copied the entries, from that file. I compared the pihole.toml files in vscode, and the only material differences, are specific to the network adapter being used, eth0 vs ensxxxx.
Expected Behaviour:
Should be getting responses from these domains
Actual Behaviour:
Domains in dnsmasq custom conf file are not being resolved
Your 10-custom.conf does not contain any directly resolvable entries.
The server definitions in there would have Pi-hole forward DNS requests to a DNS server at 10.255.0.1, i.e. it is that DNS server that provides resolution for the related forwarded domains.
In addition, your Pi-hole machine is part of 192.168.254.0/24 via eth0 and 192.168.100.0/24 via wlan0.
Neither of those subnets comprises 10.255.0.1, so you'd have to make sure that your 10.255.0.1 is actually reachable from your Pi-hole machine.
Probably unrelated, but you may want to revisit your local domain choices:
A lot of the domains you forward end in .local.
That .local TLD is reserved for mDNS protocol usage, and should not be used with plain DNS.
If those domains are your invention, you should consider to cease using them and switch to the local domain as propagated by your respective router's DHCP servers.
According to your debug log, at least one of them would distribute localdomain, while Pi-hole would be using lan.
That was it. The subnet was not reachable, I had to add an ACL to my VPN tunnel to access that network, now its working fine, my other Pi-hole already had an ACL entry as it was on a different vlan. Thank you!