lb._dns-sd._udp.clients.MyDomain.net and b._dns-sd._udp.clientsMyDomain.net (where MyDomain.net is the name of my domain and clients were my clients devices are...)
if I click on white list I'm getting an error:
Domain lb._dns-sd._udp.clients.MyDomain.net is not a valid domain.
Added 0 out of 1 domains
Jan 4 19:28:43 dnsmasq[31518]: query[PTR] lb._dns-sd._udp.0.10.168.192.in-addr.arpa from 192.168.10.196
Jan 4 19:28:43 dnsmasq[31518]: forwarded lb._dns-sd._udp.0.10.168.192.in-addr.arpa to 8.8.4.4
Jan 4 19:28:43 dnsmasq[31518]: query[PTR] lb._dns-sd._udp.clients.MyDomain.net from 192.168.10.196
Jan 4 19:28:43 dnsmasq[31518]: config lb._dns-sd._udp.clientsMyDomain.net is NXDOMAIN
Jan 4 19:28:49 dnsmasq[31518]: query[PTR] lb._dns-sd._udp.0.10.168.192.in-addr.arpa from 192.168.10.205
These are DNS Discover Service queries, frequently associated with the Apple Bonjour protocol.
When these are forwarded to an upstream DNS resolver (in your case Google DNS), that resolver is unable to resolve them if they are not defined on an authoritative nameserver (and they are not).
@anon55913113 is right, this bug is about you being authoritative for MYDomain.net and a cosmetic issue in Pi-hole displaying such domains as (regex) blocked when they don't exist. This bug will get fixed by the PR referenced in this other thread.
Thanks,
I also see on the block list a search from my Windows devices of "WPAD.clients.MYDomain.net" I guess it's for the Web Proxy Auto-Discovery ...? it's display as blocked also on the Query Log in the interface...