[image: 1548273583259-screenshot_2019-01-23-pf100se-ici-firewall-pfblockerng-resized.png]
Did you disable pfblockerNG before removing the package?
You could try to uncheck both, save, then remove the package.
Thanks for the reply, Johnpoz. Turns out that some of the firewalls/antiviruses in the Mac are messing with the DNS. Everything is working fine on systems that don't have that junk.
Install Cron package and then you could run a cron shell job 15 min before PfblockerNG Cron Update that download and process the list to a local file to be ready for processing.
So I should edit my port forward rules in NAT to add the a network alias for pfBlocker_NA IPv4 and IPv6.
Like this
Alias
[image: 1547228457863-fpblocker-network-alias-resized.jpg]
Port Forward rule
[image: 1547228503526-forwardrule-resized.jpg]
@bbcan177 said in Why is so difficult to block this specific website when using mobilephone's Chrome App?:
d its not possible to block that easily since its not on port 53.
so gettin you right
for optimal filter (pfB / DNSBL) experience it will be wise to
not redirect to port 53 (as i mentioned in the work around)
thanks for input ... makes totally sense
br from snowLand
CoinBlocker feed is on gitlab.io, so maybe that is being blocked? Can you get to that domain?
The Dyre feed is down. Not sure when it will return. The other Abuse feeds came back online tho:
https://www.reddit.com/r/pfBlockerNG/comments/a6zs1u/abuse_sslbl_is_back_online/