@netboy
Things you can test :
Leave pfBlockerng enabled, but :
Remove all IP lists.
De activate all DNSBL lists : you can do that by un checking :
[image: 1762169315597-16b7ab6f-b38d-4c9b-8201-07756bb1a081-image.png]
Btw : You use the "Unbound Python mode", right ?
When DNS fails to work for your LAN devices, check 'manually' :
C:\Users\Gauche>nslookup google.com
Serveur : pfSense.bhf.tld
Address: 2a01:cb19:907:dead:beef:92ec:77ff:fe29:392c
Réponse ne faisant pas autorité :
Nom : google.com
Addresses: 2001:4860:4802:32::78
216.239.38.120
This tells me my LAN (windows) device was using the pfSense LAN IPv6 = 2a01:cb19:907:dead:beef:92ec:77ff:fe29:392c (for IPv4 this would be 192.168.1.1) - so I know that my device is using pfSense, the resolver, as it DNS source.
I got an answer, so I know the resolver did its work.
If no answer, go console or SSH of pfSense and check there :
[25.07.1-RELEASE][root@pfSense.bhf.tld]/root: dig @127.0.0.1 google.com +short
216.239.38.120
This shows me that @127.0.0.1 (pfSense localhost) answered, as the resolver listens on every LAN interface and also localhost.
This :
[25.07.1-RELEASE][root@pfSense.bhf.tld]/root: dig @192.168.1.1 google.com +short
216.239.38.120
as my pfSense uses the default 192.168.1.1/24 LAN IP.
If no answer : then the resolver isn't running, and that's 'not normal'. Starting it :
[image: 1762169873517-560068d3-a229-4bde-8701-0d05a0b31cd9-image.png]
would resolve the issue right away.
Left to discover : why does your revolver (unbound) process dies ?
edit :
Also logical : we all use the same 'code' :
[image: 1762169997506-667f8b72-cc12-4959-bbf3-660d23e9b5cf-image.png]
( I'm using 25.07.1 on a 4100 )
'all' is probably a couple of hundred thousand pfBlockerng users using 2.8.1 or 25.07.1 and the latest pfBlockerng version.
The only thing that is different for all of us : our settings ...
This requalifies the problem from : "is something wrong with pfBlockerNG?" to a more mangeable "is something wrong with my pfBlockerNG?".
And as it is already known that we all use the same "pfBlockerNG", the issue reduces further to "What wrong with my (pfBlockerNG) settings?".
So : tell us all about your pfBlockerNG and DNS (!) settings, and we might be able to tell you what's wrong