Skip to Content.
Sympa Menu

discuss - Re: [opennic-discuss] Seized poker domains

discuss AT lists.opennicproject.org

Subject: Discuss mailing list

List archive

Re: [opennic-discuss] Seized poker domains


Chronological Thread 
  • From: "teamcoltra AT gmail.com" <teamcoltra AT gmail.com>
  • To: discuss AT lists.opennicproject.org
  • Subject: Re: [opennic-discuss] Seized poker domains
  • Date: Wed, 20 Apr 2011 21:40:55 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=HMioX/RFLBQjAQ+3ddM0CkjEjuN2ir24Ttm3x9TQkJB0dWtfqmn+q9LXMZ/fNbjpMY Mvp6DkIMUbblUwwgRte0llXXE36m5cG34N/lmpPqdVdvPyAdAJ3189DU7bWoNzZN7+OH OR1rp5YlGvfLAjKbT0qprb15/QLTbvu2xussA=
  • List-archive: <http://lists.darkdna.net/pipermail/discuss>
  • List-id: <discuss.lists.opennicproject.org>

Option 2 for sure.

Travis McCrea
Sent on-the-go from my mobile

On 2011-04-20 9:32 PM, "Jeff Taylor" <shdwdrgn AT sourpuss.net> wrote:
> OK there are two ways to handle 'protecting' a domain name. I will use
> "torrent-finder.com" as an example. Please submit your opinions for each
> method, along with any additional pros and cons. Once a choice has been made on
> the methodology, I believe we will be ready to put the idea to a vote.
>
> (1) Redirect queries to a temp page. When browsing the web, a user would see a
> page warning that the destination page has come under government control, and
> they are given the option to visit the original page, or the new
> (government-controlled) page. If choosing to visit the original page, the user
> would be redirected to something like "torrent-finder.com.glue" which we create
> to contain NS and/or A records pointing to the original site.
>
> Pros:
> - Users instantly know when a redirect is occurring
>
> Cons:
> - Limits usage to web-only -- all other forms of queries would return the dns
> for the warning page.
> - Requires maintaining additional zone files for each .glue domain created.
> - Poorly-designed website will not functional correctly except from their
> original domains
>
>
> (2) Create our own entries in the root record to point all queries back to the
> original domain. Create a custom build of bind9 which, when queried for
> "torrent-finder.com.icann", will strip off the .icann portion and perform the
> lookup via an icann-based dns server.
>
> Pros:
> - Seamless. To a user, it will be like the original site still exists.
> - No additional zones will need to be created or maintained, although we will
> have to create the .icann TLD.
> - The .icann queries can be distributed between any T1 or T2 servers willing to
> run the modified bind9.
>
> Cons:
> - Users will not be made aware of the redirects. A wiki page will need to be
> created to list all 'protected' domains.
> - Someone will have to create the modified bind9 code.
> - The servers handling the .icann queries will need to be aware of the potential
> for abuse.
> _______________________________________________
> discuss mailing list
> discuss AT lists.opennicproject.org
> http://lists.darkdna.net/mailman/listinfo/discuss



Archive powered by MHonArc 2.6.19.

Top of Page