On 25 May 2018, at 18:59 (-0400), Mark E. Jeftovic wrote:
Looks like dnsbl.cyberlogic.net just wildcarded itself to 38.102.67.13
within the last hour or so.
dnsbl.cyberlogic.net returned result 38.102.67.13/32 for 205.210.42.10
dnsbl.cyberlogic.net returned result 38.102.67.13/32 for
205.210.42.30
dnsbl.cyberlogic.net returned result 38.102.67.13/32 for
205.210.42.42
dnsbl.cyberlogic.net returned result 38.102.67.13/32 for
205.210.42.57
dnsbl.cyberlogic.net returned result 38.102.67.13/32 for
205.210.42.58
dnsbl.cyberlogic.net returned result 38.102.67.13/32 for
205.210.42.59
dnsbl.cyberlogic.net returned result 38.102.67.13/32 for
205.210.42.70
dnsbl.cyberlogic.net returned result 38.102.67.13/32 for
205.210.42.80
dnsbl.cyberlogic.net returned result 38.102.67.13/32 for
205.210.42.183
OK, but why would this matter?
To the best of my recollection and as best I can figure out from what's
at archive.org and elsewhere, that was never a public DNSBL. They've
been marked as private at the valli.org site continuously for many
years. Also, any DNSBL tool that is still firing on 'any answer' instead
of requiring 127.0.0.2 or some other specific result really merits
flushing out of the ecosystem by this sort of event.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Currently Seeking Steadier Work: https://linkedin.com/in/billcole
_______________________________________________
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
