>AFAIK dnsmasq (which Pi-hole uses) doesn't support wildcards. There seems to be conflicting information about wildcards but I thought the feature was added th

>AFAIK dnsmasq (which Pi-hole uses) doesn't support wildcards. There seems to be conflicting information about wildcards but I thought the feature was added this year: https://github.com/pi-hole/pi-hole/pull/1065 https://github.com/pi-hole/pi-hole/pull/1065 >However Pi-hole does import hugely extensive lists of domains so you'll unlikely to need wildcard matching anyway. I liked the power of wildcards because the ad and malware networks always add new subdomains faster than the updating and propagating of static hosts lists. Example might be: 0.0.0.0 ads.zedo.com 0.0.0.0 c1.zedo.com 0.0.0.0 c2.zedo.com 0.0.0.0 c3.zedo.com 0.0.0.0 c4.zedo.com 0.0.0.0 c5.zedo.com 0.0.0.0 c6.zedo.com 0.0.0.0 c7.zedo.com 0.0.0.0 c8.zedo.com 0.0.0.0 d2.zedo.com 0.0.0.0 d3.zedo.com If zedo.com adds new subdomains "c9.zedo.com" and "d4.zedo.com", the static list lets the ads through until I update the lists. Wildcards such as "* .zedo.com" are an elegant syntax to stop that loophole. >cannot comment about the Win 10 telemetry data. Btw, I mentioned MS Win 10 because Microsoft added code at the kernel level that ignores manual entries edded to /etc/hosts file so it can still phone home. Therefore, only a firewall device that lives outside of Win 10 can block it. (https://www.petri.com/windows-10-ignoring-hosts-file-specific-name-resolution https://www.petri.com/windows-10-ignoring-hosts-file-specifi...)