Don't if you're still on NCUC list? anyway here goes...<div><br></div><div><meta http-equiv="content-type" content="text/html; charset=utf-8">On Sat, Nov 27, 2010 at 7:34 AM, Robin Gross <span dir="ltr"><<a href="mailto:robin@ipjustice.org">robin@ipjustice.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
<div style="word-wrap: break-word; ">The latest info that I've seen is <span style="font-family: 'lucida grande', tahoma, verdana, arial, sans-serif; color: rgb(51, 51, 51); font-size: 11px; ">that Verisign assigned new DNS servers at the Registry level, and then locked the domain so that even the Registrar can't update it. So now it looks like it may have been VeriSign who "seized" them. No word on ICANN's role in this situation, if any. </span><div>
<span style="font-family: 'lucida grande', tahoma, verdana, arial, sans-serif; color: rgb(51, 51, 51); font-size: 11px; "><br></span></div><div><div><div></div><div class="h5"><span style="font-family: 'lucida grande', tahoma, verdana, arial, sans-serif; color: rgb(51, 51, 51); font-size: 11px; "><br>
</span><div><div><br></div><div>On Nov 26, 2010, at 8:29 PM, Marc Perkel wrote:</div><br><blockquote type="cite"><div bgcolor="#ffffff" text="#000000">So was it ICANN that actually did the seizing?<br></div></blockquote></div>
</div></div></div></div></blockquote><br><div class="gmail_quote">On Sat, Nov 27, 2010 at 7:13 AM, McTim <span dir="ltr"><<a href="mailto:dogwallah@gmail.com">dogwallah@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Morning Alex,<br>
<br>
I find this very curious.<br>
<br>
We all know (or should know) that ICANN or more properly (the IANA)<br>
cannot physically make this change, as they do not have access to the<br>
.com zone file to physically make this change.<br>
<br>
So, either GoDaddy is lying aboout ICANN making the change, or they<br>
meant that the order came from ICANN, which, as we all know is not the<br>
way things should be done. If GoDaddy has an order from ICANN, I<br>
would love to see it, more likely, GoDaddy got an order from a court<br>
ordering them to do this.<br>
<br>
There is another possibility, this is possibly a hoax, or social<br>
engineering attack.<br>
<br>
Looking in the DNS I see that whois shows that the original<br>
registrant, torrent finder still owns the domain, so the domain was<br>
not "seized", but the DNS was redirected seemingly by a private<br>
company whose domain (seized Domain.com) was registed on 24 Nov,<br>
seemingly by a private company. If you lok at the IP address whois,<br>
that block is registered to another private company, so there is no<br>
evidence that this was done by a USG body....very curious indeed.<br>
Does the USG outsource "seizures" of this kind?? I would think they<br>
would use their own IP ranges and web servers. It looks very fishy to<br>
me!!<br>
<br>
anyway here is the DNS and whois data:<br>
<br>
dig <a href="http://torrent-finder.com" target="_blank">torrent-finder.com</a><br>
<br>
; <<>> DiG 9.3.2 <<>> <a href="http://torrent-finder.com" target="_blank">torrent-finder.com</a><br>
;; global options: printcmd<br>
;; Got answer:<br>
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 168<br>
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2<br>
<br>
;; QUESTION SECTION:<br>
;<a href="http://torrent-finder.com" target="_blank">torrent-finder.com</a>. IN A<br>
<br>
;; ANSWER SECTION:<br>
<a href="http://torrent-finder.com" target="_blank">torrent-finder.com</a>. 15089 IN A 74.81.170.110<br>
<br>
;; AUTHORITY SECTION:<br>
<a href="http://torrent-finder.com" target="_blank">torrent-finder.com</a>. 15089 IN NS <a href="http://ns2.torrent-finder.com" target="_blank">ns2.torrent-finder.com</a>.<br>
<a href="http://torrent-finder.com" target="_blank">torrent-finder.com</a>. 15089 IN NS <a href="http://ns1.torrent-finder.com" target="_blank">ns1.torrent-finder.com</a>.<br>
<br>
;; ADDITIONAL SECTION:<br>
<a href="http://ns1.torrent-finder.com" target="_blank">ns1.torrent-finder.com</a>. 15089 IN A 74.81.170.109<br>
<a href="http://ns2.torrent-finder.com" target="_blank">ns2.torrent-finder.com</a>. 15089 IN A 74.81.170.108<br>
<br>
;; Query time: 234 msec<br>
;; SERVER: 196.200.16.2#53(196.200.16.2)<br>
;; WHEN: Sat Nov 27 06:41:35 2010<br>
;; MSG SIZE rcvd: 120<br>
<br>
dig @<a href="http://ns1.torrent-finder.com" target="_blank">ns1.torrent-finder.com</a> ANY <a href="http://torrent-finder.com" target="_blank">torrent-finder.com</a><br>
<br>
; <<>> DiG 9.3.2 <<>> @<a href="http://ns1.torrent-finder.com" target="_blank">ns1.torrent-finder.com</a> ANY <a href="http://torrent-finder.com" target="_blank">torrent-finder.com</a><br>
; (1 server found)<br>
;; global options: printcmd<br>
;; Got answer:<br>
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1312<br>
;; flags: qr aa rd; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 2<br>
<br>
;; QUESTION SECTION:<br>
;<a href="http://torrent-finder.com" target="_blank">torrent-finder.com</a>. IN ANY<br>
<br>
;; ANSWER SECTION:<br>
<a href="http://torrent-finder.com" target="_blank">torrent-finder.com</a>. 86400 IN A 74.81.170.110<br>
<a href="http://torrent-finder.com" target="_blank">torrent-finder.com</a>. 86400 IN SOA <a href="http://torrent-finder.com" target="_blank">torrent-finder.com</a>.<br>
noreply.seizeddomain. 2010111801 86400 3600 604800 10800<br>
<a href="http://torrent-finder.com" target="_blank">torrent-finder.com</a>. 86400 IN NS <a href="http://ns2.torrent-finder.com" target="_blank">ns2.torrent-finder.com</a>.<br>
<a href="http://torrent-finder.com" target="_blank">torrent-finder.com</a>. 86400 IN NS <a href="http://ns1.torrent-finder.com" target="_blank">ns1.torrent-finder.com</a>.<br>
<br>
;; ADDITIONAL SECTION:<br>
<a href="http://ns1.torrent-finder.com" target="_blank">ns1.torrent-finder.com</a>. 86400 IN A 74.81.170.109<br>
<a href="http://ns2.torrent-finder.com" target="_blank">ns2.torrent-finder.com</a>. 86400 IN A 74.81.170.108<br>
<br>
;; Query time: 437 msec<br>
;; SERVER: 74.81.170.109#53(74.81.170.109)<br>
;; WHEN: Sat Nov 27 06:42:34 2010<br>
;; MSG SIZE rcvd: 176<br>
<br>
<br>
C:\Documents and Settings\Administrator>whois -h <a href="http://whois.arin.net" target="_blank">whois.arin.net</a> 74.81.170.110<br>
#<br>
# Query terms are ambiguous. The query is assumed to be:<br>
# "n 74.81.170.110"<br>
<br>
<br>
CaroNet Managed Hosting, Inc. CI-74-81-170-0-23 (NET-74-81-170-0-1)<br>
74.81.170.0 - 74.81.171.255<br>
Carolina Internet, Ltd. CARO-NET-ARIN-4 (NET-74-81-160-0-1)<br>
74.81.160.0 - 74.81.191.255<br>
<br>
<br>
#<br>
# ARIN WHOIS data and services are subject to the Terms of Use<br>
# available at: <a href="https://www.arin.net/whois_tou.html" target="_blank">https://www.arin.net/whois_tou.html</a><br>
#<br>
<br>
<br>
C:\Documents and Settings\Administrator>dig @<a href="http://ns1.torrent-finder.com" target="_blank">ns1.torrent-finder.com</a><br>
ANY <a href="http://SEIZEDSERVERS.COM" target="_blank">SEIZEDSERVERS.COM</a><br>
<br>
; <<>> DiG 9.3.2 <<>> @<a href="http://ns1.torrent-finder.com" target="_blank">ns1.torrent-finder.com</a> ANY <a href="http://SEIZEDSERVERS.COM" target="_blank">SEIZEDSERVERS.COM</a><br>
; (1 server found)<br>
;; global options: printcmd<br>
;; Got answer:<br>
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 740<br>
;; flags: qr aa rd; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 2<br>
<br>
;; QUESTION SECTION:<br>
;<a href="http://SEIZEDSERVERS.COM" target="_blank">SEIZEDSERVERS.COM</a>. IN ANY<br>
<br>
;; ANSWER SECTION:<br>
<a href="http://SEIZEDSERVERS.COM" target="_blank">SEIZEDSERVERS.COM</a>. 86400 IN A 74.81.170.110<br>
<a href="http://SEIZEDSERVERS.COM" target="_blank">SEIZEDSERVERS.COM</a>. 86400 IN SOA <a href="http://SEIZEDSERVERS.COM" target="_blank">SEIZEDSERVERS.COM</a>.<br>
noreply.seizeddomain. 2010111801 86400 3600 604800 10800<br>
<a href="http://SEIZEDSERVERS.COM" target="_blank">SEIZEDSERVERS.COM</a>. 86400 IN NS <a href="http://ns1.SEIZEDSERVERS.COM" target="_blank">ns1.SEIZEDSERVERS.COM</a>.<br>
<a href="http://SEIZEDSERVERS.COM" target="_blank">SEIZEDSERVERS.COM</a>. 86400 IN NS <a href="http://ns2.SEIZEDSERVERS.COM" target="_blank">ns2.SEIZEDSERVERS.COM</a>.<br>
<br>
;; ADDITIONAL SECTION:<br>
<a href="http://ns1.SEIZEDSERVERS.COM" target="_blank">ns1.SEIZEDSERVERS.COM</a>. 86400 IN A 74.81.170.109<br>
<a href="http://ns2.SEIZEDSERVERS.COM" target="_blank">ns2.SEIZEDSERVERS.COM</a>. 86400 IN A 74.81.170.108<br>
<br>
;; Query time: 500 msec<br>
;; SERVER: 74.81.170.109#53(74.81.170.109)<br>
;; WHEN: Sat Nov 27 06:53:13 2010<br>
;; MSG SIZE rcvd: 175<br>
<br>
<br>
<br>
<br>
whois -h <a href="http://whois.networksolutions.com" target="_blank">whois.networksolutions.com</a> <a href="http://SEIZEDSERVERS.COM" target="_blank">SEIZEDSERVERS.COM</a><br>
<br>
Registrant:<br>
immixGroup IT Solutions<br>
ATTN <a href="http://SEIZEDSERVERS.COM" target="_blank">SEIZEDSERVERS.COM</a><br>
care of Network Solutions<br>
PO Box 459<br>
Drums, PA. US 18222<br>
<br>
<br>
Domain Name: <a href="http://SEIZEDSERVERS.COM" target="_blank">SEIZEDSERVERS.COM</a><br>
<br>
<br>
Administrative Contact, Technical Contact:<br>
immixGroup IT Solutions<br>
<a href="mailto:ha3cf8td8vj@networksolutionsprivateregistration.com">ha3cf8td8vj@networksolutionsprivateregistration.com</a><br>
ATTN <a href="http://SEIZEDSERVERS.COM" target="_blank">SEIZEDSERVERS.COM</a><br>
care of Network Solutions<br>
PO Box 459<br>
Drums, PA 18222<br>
US<br>
570-708-8780<br>
<br>
<br>
Record expires on 24-Nov-2011.<br>
Record created on 24-Nov-2010.<br>
Database last updated on 26-Nov-2010 22:38:17 EST.<br>
<br>
Domain servers in listed order:<br>
<br>
<a href="http://NS1.SEIZEDSERVERS.COM" target="_blank">NS1.SEIZEDSERVERS.COM</a> 74.81.170.109<br>
<a href="http://NS2.SEIZEDSERVERS.COM" target="_blank">NS2.SEIZEDSERVERS.COM</a> 74.81.170.108<br>
<br>
<br>
<br>
--<br>
Cheers,<br>
<font color="#888888"><br>
McTim<br>
"A name indicates what we seek. An address indicates where it is. A<br>
route indicates how we get there." Jon Postel<br>
_______________________________________________<br>
AfrICANN mailing list<br>
<a href="mailto:AfrICANN@afrinic.net">AfrICANN@afrinic.net</a><br>
<a href="https://lists.afrinic.net/mailman/listinfo.cgi/africann" target="_blank">https://lists.afrinic.net/mailman/listinfo.cgi/africann</a><br>
</font></blockquote></div><br><br clear="all"><br>-- <br>regards,<br><br>Alex Gakuru<br><a href="http://www.mwenyeji.com" target="_blank">http://www.mwenyeji.com</a><br>Hosting, surprise yourself! <br>
</div>