@SteveITS
This "10.10.10.1" is an option that will get ditched soon.
02a55b89-694c-45ad-a67c-7d61f0de335d-image.png
I use this :
df6fa93f-450e-47ef-a1b4-13b4380d7c94-image.png
A browser on your LAN wants to visit facebook.com
But you, as the pfSense admin, have blocked "facebook.com" (as a DNSBL)
Do you think that a page like this :
f67137b8-6c17-422b-ba7b-9d7c69d443c6-image.png
will pop up to warn the user in its browser that 'facebook' has been blocked ?
Now way ! Because you, me and nobody can't break TLS. Remember, https is used. The browser want to visit facebook.com but it gets an answer back from some guy called "10.10.10.1". That is interception, and that is bad. The browser will bark.
And not showing any pages - no way, it will throw the complex and scary messages on the screen .... (we all know them)
So, the admin that start to understand what TLS (= https) is, doesn't care about what the pfBlockerng web server "10.10.10.1" has to offer.
"10.10.10.1" was nice in the good old http days.
There are no http server anymore, they have been shut down (actually : they are still there doing just one thing : redirecting you to the https counterpart, as http traffic can be redirected.
That's why I "Null log".
Btw : Null logging means : return 0.0.0.0 (means : doesn't exist, don't insist - do nothing)
cf706ddc-954e-4629-9dcb-5e06f7e52b29-image.png
means : return "10.10.10.1" - which is, imho, as I exposed above, pretty useless.