@johnpoz Well, honestly ... I would love to use the pfBlocker, as this seems to me 'easier' solution as it is already implemented and working. The shallalist is available there as well ... the only thing I am not sure is how I split the filtering for: parents -> DNSBL, Ads, IP kids -> all the above + categories But let's see, maybe someone else comes with some other views. Thank you.

@johnpoz Actually when some other agency or corporation gets MinMind customer database plus the ISP databases that nowadays you can bet are automatically available... yes then someone could have a complete picture... it amazes me how people don't care about privacy and don't seem to understand that no privacy means no democracy... Do we still value democracy over money or convenience? You don't know what actually MinMind is... so I suggest updating pfblockerng to use another geolocation database and prepare it to accept more easily other options. There's always the possibility of a fork.

I am having this same Errors. Did you ever get yours fixed? @Ronpfs Just Because you do not use some thing, Does not means he should not ? THATS pretty backwards thinking!

DoH feature disable is absolutely great

Turns out it is the semicolon causing the issue. In this post, BBcan177 says there is no parser for the semicolon.

@jeffvogelsang Well, on PFBLOCKERNG/DNSBL page, there is the TOP 1M WHITELIST. You can choose the Cisco or Alexa list and then choose how many down the list from the top you want to whitelist. Then choose what is to be included in TLD whitelist. I see it as a safety net to catch popular domains that could end up as a false positive in the blacklists. I set mine to the top 2k. A real pre-packaged 'whitelist' like the blacklists would be very hard to maintain and would obviously need to be very large to really be useful. Consider that for it to have value, you would have to decide what to do with sites that are not on the whitelist. Do you block them? If you don't then what is the point of the whitelist? Thinking someone can figure out, for all the blacklists out there, what the false positives are and then making a whitelist for them and keeping it up to date would be about as daunting. Think about the maintenance involved, ouch. I rarely have issues where I have to add anything to the whitelist anymore, my list is about 45 domains and some TLD exclusions that have been added over the last couple of years. If I test out a a list and see a large amount of false positives I dump it and use something else.

@maba Thank you. Makes sense. Just found the button to clear out the counters and reset them! [image: 1588385225352-screen-shot-2020-05-01-at-7.06.00-pm.png]

ok i figure it out ... for some obscure reason , the line server:include: /var/unbound/pfb_dnsbl.*conf in dnsresolver was append at the end of my custom options ... it need to be at the top before them... The update of pfblocker have broken that. Hope it stay as it is. edit: and a better solution : my options just miss one line ... My "options" begin with: local-zone: "x.X.X.X.X.X.ip6.arpa" typetransparent i had to add "server:" just before "local-zone" ... so no more crash , "server:include..." can be at the bottom or at top ... it's working. ;) So maybe the bug, one more time, was between the chair and the keyboard ;)))

@Jobee Please wait for package update: https://redmine.pfsense.org/issues/9874#note-8

@manuelgop Did you apply the changes after reordering the rules? They apply in order, though as I said pfBlocker might reorder them.

You mean a IPv4 List you created is now not working? I'm having the same problem with a brand new setup + List. Cant create it, when it tries to update it gives me custom error list!