full-disclosure - Verisign abusing .COM/.NET monopoly, BIND releases new

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3F6809B0.20005@dylanic.de>
From: security at dylanic.de (Michael Renzmann)
Subject: Verisign abusing .COM/.NET monopoly, BIND releases
 new

Hi Brian.

Brian Hatch wrote:
> Is it always returning the same IP address, 

Yeah, seams like that. For example, the (I think) non-existant 
dulladulladulla.net resolves to 64.94.110.11, as well as 
bollabollabolla.net or verisignsucks.net. So blocking any DNS reply 
containing this IP could be a way to prevent that Verisign "commercial 
break".

Did anyone else notice that the host behind this IP seems to be down? No 
ping reply, no answer to http-requests. No, wait: port 25 seems to be 
open (so there is a machine behind that IP). But no http, so no (more) 
commercial from that host.

Bye, Mike