DNSSEC And Wildcarding Available In Pi-hole Core 2.12 / Web 2.4
We are happy to release another new version of Pi-hole (Core and Web). Your support and contributions have helped it become a reality. This release includes several fixes and tweaks, which you can read about on changes.pi-hole.net. We have also added some new features.
DNSSEC
You requested it and we implemented it. Once enabled, there is a link you can click that will check to see if it is working.
Wildcard Blacklisting
This has been an oft-requested feature, and may prove useful for blocking YouTube ads. You can use this new blacklisting feature with the pihole -wild option. So if you wanted to block all of bannerflow.com:
pihole -wild bannerflow.com
pihole -wild -d bannerflow.comRelated Feature
You can also now paste in space-delimited domains to be added to the white/black from the Web interface.
logrotate
We implemented a new flushing routine using the logrotate command for pihole.log with the following options:
daily(rotate the log once per day)copytruncate(copy the existing file to the new place and truncate the original file afterwards)rotate 5(keep 5 days/manual flush cycles)compress+delaycompress(compress files older than 1 day)notifyempty(do not rotate the log if it is empty)nomail(don’t mail old log files to any address)
If for some reason logrotate is not found, it will fallback to the old flushing routine.
Multiple Upstream DNS Servers
You can now specify multiple upstream servers to use via the Web interface.
Pi-hole Teleporter
This feature was called takeout for a while, but teleporter seemed more appropriate and didn’t make us as hungry. This feature came as a request from the community so you can now export your Pi-hole lists to a .zip file.
A Joke For The Networking Folks
Taertox 
telekrmor 
bob 
Itsme
Wildcards are a beautiful beautiful thing
I guess I was worrying that without some sort of delimiter, it would start blocking everything with the word online in it.
We’ve thought of that and have protection against something like a regex match for blocking more than you intended.
Possible issue with the pihole web interface v2.4 and wildcard blocking
Hello! I’m using the notracking domain list for wildcard blocking. I’ve adapted the list for pihole wildcard blocking, moved it to “/etc/dnsmasq.d/03-pihole-wildcard.conf”, and it works fine. The problem is with the web interface v2.4. It becomes very slow or unresponsive. It seems that it can’t handle a large wildcard list.
How to solve this problem?
This list add more than 50 000 entries to the wildcard list. Neither the black- nor the whitelist features of Pi-hole are designed to be use with such a vast amount of entries. Also, the blacklist page doesn’t make much sense when it is just extraordinary long. I suggest moving your manually created file to another filename so your Pi-hole will drag it in, but won’t use it for displaying. In this way you can still use the wildcard blacklisting manually for creating additional entries.