@tibere86 said in Null blocking SERVFAIL:
When I have NULL BLOCK enabled, DNSBL v6 returns SERVFAIL instead of ::
Hummmm.
I just tested with "006.freecounters.co.uk" which is part of DNSBL_ADs_Basic.
When I test with
ca23059c-ccd3-441a-9434-b918db763d10-image.png
I saw also a "ServFail".
Then I started to "play" with the python script ... and now I see :
(adding logs lines on what I think are interesting places ), like on line 1614:
log_info("{} Blocked {} Returned IP {} {}".format(q_name, b_ip, q_type_str, q_type))
I saw :
<30>1 2025-01-29T17:56:09.484605+01:00 pfSense.hf.tld unbound 13346 - - [13346:0] info: 006.freecounters.co.uk Blocked :: AAAA 28
98421505-6341-4765-9a80-f261744be26f-image.png
... But then humm again.
If unbound return "::" then what can the browser do with this ?
It should be the, to be useful, an IPv6 GUA of pfSense .....
And &@/{#, as I'm in null blocking mode ...
Done. back to Web server mode.
Now I see :
info: 006.freecounters.co.uk Blocked ::10.10.10.1 Returned IP AAAA 28
But https://[::10.10.10.1]:443 doesn't really work.
Also : https://serverfault.com/questions/698369/what-is-the-ipv6-equivalent-of-0-0-0-0-0
