[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Full-Disclosure] Verisign abusing .COM/.NET monopoly, BIND releases new
- To: full-disclosure@xxxxxxxxxxxxxxxx
- Subject: Re: [Full-Disclosure] Verisign abusing .COM/.NET monopoly, BIND releases new
- From: Christopher Kruslicky <anub-full.disclosure.200309@xxxxxxxxxxxx>
- Date: Wed, 17 Sep 2003 19:28:02 -0400
On Wednesday 17 September 2003 03:13, Michael Renzmann wrote:
> 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".
And just to make the whole thing a little funnier, they've decided not to
resolve verisignsucks.com anymore =)
$ host verisignsucks.com
Host verisignsucks.com not found: 2(SERVFAIL)
$ host verisignsucksdonkeyballs.com
verisignsucksdonkeyballs.com has address 64.94.110.11
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html