Any workarounds for Verisign .com/.net highjacking?

[Michael Edenfield]

* 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.  

> 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

--Mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20030916/403c45c3/attachment.bin