Any workarounds for Verisign .com/.net highjacking?

John Polstra jdp at polstra.com
Tue Sep 16 21:09:37 PDT 2003


On 17-Sep-2003 Michael Edenfield wrote:
> * John Polstra <jdp at polstra.com> [030916 21:27]:
> 
>> True, we could probably do it.  I guess we'd have to generate a few
>> random and unlikely queries, try them, and see if all/most of them
>> resolve to the same address.  Or maybe the to the same small set of
>> addresses, depending on how determined Verisign is to make this work.
> 
> "*.net" should work, since they basically added a * A record to .com and
> .net.  

Yep, that should work.

>> I just _love_ how Verisign doesn't even have a reverse DNS record for
>> that address.  Jerks.
> 
> root at basement:/usr/src# host 64.94.110.11
> 11.110.94.64.IN-ADDR.ARPA domain name pointer sitefinder-idn.verisign.com

When I wrote the above, "host 64.94.110.11" didn't return anything.

John


More information about the freebsd-hackers mailing list