It appears that the site you were visiting has been blocked by the DNSBL. You'll need to create another DNSBL list and add the sites you were visiting that you know to be safe...be sure to set group order to primary and disable logging as shown below. Then add the sites to the DNSBL Custom_List. Then, force reload pfBlockerNG. [image: 1574400957620-screen-shot-2019-11-21-at-11.30.20-pm.png] [image: 1574401029423-screen-shot-2019-11-21-at-11.30.52-pm.png]

I can tell there are many of you dying to know what happened with this. </sarcasm> I rebooted the whole firewall. Botta bing botta boom. Both are blocked now. That didn't cross my mind to do that because you wouldn't think that'd be necessary for such a problem, but...isn't that actually always the answer?

@mh13 said in Can I block IPs of my DNS-based lists?: Automatically? That's the feature we're waiting on you to develop.

@BBcan177 Thanks for your help. It's error was resolved.

I'm using Safari. At least, to view Youtube. I'll try to block outbound DNS not using the resolver on pfSense and disable DoH on Firefox.

@BBcan177 I see. I was hoping there would be a way that I was just ignorant of. Thank you for taking the time to review this. If anyone else has a suggestion beyond manually resolving these domains externally and manually updating the lists, please let us know!

@ryanca said in DNSBL modify default bloked webpage: Thanks, but I would rather go back to the old way with the (GIF Image, 1 × 1 pixels). Could i just upload that gif image to the /usr/local/www/pfblockerng/www/ folder and delete the default html files in there? Or do I need to do something else? Copy the default page and create a new one with your modifications. Then select the new page in the DNSBL Tab.

Does this help: https://forum.netgate.com/topic/129365/bypassing-dnsbl-for-specific-ips

It's running i386, and 2.3.x is the latest version available for that, because we do not support i386 on 2.4.x and later. 2.3.x has been EOL for over a year: https://www.netgate.com/blog/pfsense-release-2-3-x-eol-reminder.html If that hardware is capable of running a 64-bit OS, you can reinstall with the latest 2.4.4-p3 installer and get back up and running. If that hardware is 32-bit only, it will need to be replaced.

@Hurkamurka said in Noobie questions about pfblockerng: I installed pfblockerng (non devel) This reply doesn't answer your question but suggests installing devel version.

@AndrewD I would try clearing your browser cache and may be reboot your pfSense box too. When I did, it took a full day before I could visit the site because I didn't do a force update/reload nor set group to primary.

Hey! Thanks for come by. Yes, i run the latest pfSense. The extra info about the custom lines was hidden way too at the end of the blog, but i've found it after my post, and now i changed my settings according to that. Strange thing, but changing the DNS server to UncensoredDNS, seems now everything working fine. I think i will let Applied Privacy know about this behaviour. Maybe do you have a clue why could i resolve the hostname in the browser, but not in the DNSBL feeds update?

@jward101 said in Feeds not added to 'DNSBL Feeds': Correct. They are also displayed on the DNSBL > DNSBL Feeds interface BUT only after I added a feed manually through that interface. Before I added that manual feed they were not displayed in that location. I have a few like that...I was looking through to post for instance; however, they do show under the feed menu as duplicates though.

AH ... yes, indeed my subnetting skills were lacking here. I resorted to lookups with this tool which helped me better understand what my brain couldn't sort out itself: http://jodies.de/ipcalc?host=216.220.128.0&mask1=17&mask2= Your link to the maxmind database is very helpful. So, thank you for that. Much appreciated. It will come in handy in the future. Thanks for the prompt response.

@Gertjan said in Looks lke its " working ...: The webserver being used by pfBlockerNG is listening to : If i leave it @ 127.0.0.1, my when i try to acces a blocked domain the browser keeps spining. ANd nothing getting logged in DNSBL sockstat -4l | grep 'lighttpd_p' root lighttpd_p 85774 4 tcp4 *:8081 : root lighttpd_p 85774 5 tcp4 *:8443 : root lighttpd_p 85774 6 tcp4 10.10.10.1:443 :

Sorry, wrong subcategory - I'll post it again.

Hello, ok, I disable the DNS forwarder and activate the DNS Resolver. For use the Unbound DNS Resolver I add a NAT redirect rule from here: Netgate Docs redirecting-all-dns-requests-to-pfsense My question, the NAT redirect rule create a LAN rule too, this rule is automatic below the pfblockerNG IP rules, must I move it above, after the Anti-Lockout Rule? Do I need the Blocking DNS Queries to External Resolvers rule too? regards ThomasD

See: https://www.reddit.com/r/pfBlockerNG/comments/ao98u1/dnsbl_certificate_error/ and: https://www.reddit.com/r/pfBlockerNG/search/?q=certificate&restrict_sr=1