[discuss] Domain name (was: discuss Digest, Vol 3, Issue 67)

Don Blumenthal dblumenthal at pir.org
Fri Feb 21 22:25:53 UTC 2014

A caution that we should be careful to terms when discussing these issues.
Relevant technical, legal, and political issues will vary.

A domain name "seizure" involves a court order that transfers ownership of
the domain. All services under the domain are affected insofar as someone
tries to use them via the DNS. A ³takedown² or ³block² involves denial of
access to given content sources.  Other services still may be available
via the domain name.


On 2/21/14, 2:09 PM, "S Moonesamy" <sm+1net at elandsys.com> wrote:

>Hi Christian,
>At 02:35 21-02-2014, Christian de Larrinaga wrote:
>>Is there a general principle in the US that a court should make an order
>>as specific to the LE target as possible? Is that what keeps this in the
>>box you describe?
>Please note that I am using a ".com".  If I argue that ".com" is bad
>the argument would lack credibility [1].
>There are some articles about domain name seizures at:
>I don't think that it is possible to keep this in the box.
>>LE action is not an issue that is specific to the US. Any root server
>Yes (see above links).
>>located around the world  could potentially be subjected to some kind of
>>local LE action.  Any Root Server falling out of sync is going to impact
>>the entire Root Server Network if the aim is to keep domain names unique
>>and resolvable over the whole Internet.
>I don't think that a (DNS) Root server problem would have an impact
>on every network.  A (DNS) Root server issue in a country can have an
>impact on networks in other countries [2].
>Any root server in the world can be subject to legal action from the
>relevant government(s).  Would the government carefully consider the
>potential collateral damage before taking that action?  A few years
>ago, I might have said "yes".  Nowadays, it is an "unknown".  The
>trust has been broken.
>S. Moonesamy
>1. the quality of being believed or accepted as true, real, or honest
>2. See the case of i.root-servers.net

More information about the discuss mailing list