PfBlockerNG (Not devel) DNSBL not blocking all domains in a custom feed
-
DNSBL not blocking all domains in a custom feed, I've tried CRON and reload.
PFSENSE VERSION: 2.6.0 -
@diamondcreeper75
That version is very old. This means probably no one is using is any more.
What about removing that version, and install the far superior one : pfBlockerNG-devel 3.1.0_1 ? -
@gertjan I was using PfBlockerNG-devel, but I wasn't getting this message on any blocked site.
-
@diamondcreeper75 Well, this means that it was working.
Going back to the non devel version is useless.The intercept page fails ssl verification, since ssl was designed to do this.
-
@diamondcreeper75
De activated that redirection of an DNSBL. It won't work.
Select :
If the webserver, the one used by pfBlockerNG, had a certificate that says it marketplace.google;.com, then that page would have been trusted by your browser.
Or, you have not that certificate. Actually, from all the DNSBL you have listed in the DNSBL feeds, you have none.
Conclusion : Yes, it's true, even the sites that serve add pages and such, use all https these days.This web server page stating that you visited a page blocked by DNSBL works well for plain http sites. These do not exist any more.
