Article:  |
Paul Vixie on VeriSign | |
| Subject: | Give verisign what they want | |
| Date: | 2003-09-24 05:28:54 | |
| From: | anonymous2 | |
|
Response to: Give verisign what they want
|
||
| Give me a break. Verisgn has more bandwidth than you could possibly imagine. They aren't going to care, even about billions upon billions of hits. In fact, I bet they'd just love that, since it would allow them to track users more, since they not only get info when they mistype a domain, but even while they are browsing normal sites, that just happen to have a 1x1 image. | ||
Showing messages 1 through 2 of 2.
-
Give verisign what they want
2003-09-25 03:56:24 anonymous2 [View]
-
Give verisign what they want
2003-09-24 06:33:04 anonymous2 [View]
It would take a heck of a lot but their redirect search server appears to have gotten slower. They have also stopped resolving some bogus domain names to the wildcard that they still were resolving to the wildcard ealier yesterday. For instance, verislime.com and a lot of other unfavorable references to verisign that resolved to the wildcard now result in an immediate intentional disconnection from DNS server. Thus, this suggests to me a lot of the hits to their site have been people screwing around checking how it works, working on blocking, and making a comment about versign in the process. The only reason to block it is to reduce the load since they figure these people won't user the search anyway. Here some results. First one that resolved yesterday but doesn't now and another that still does:
$ nslookup www.verislime.com
** server can't find www.verislime.com: SERVFAIL
$ nslookup www.verislime2.com
Name: www.verislime2.com
Address: 64.94.110.11
Any if that doesn't look familar:
$ nslookup 64.94.110.11
11.110.94.64.in-addr.arpa name = sitefinder-idn.verisign.com.
A lot of other unfavorable versign bogus urls not longer resolve too.
It's not that cheap.