North American Network Operators Group|
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
Re: Blocking certain terrorism/porn sites and DNS
- From: Abhishek Verma
- Date: Thu Aug 18 05:56:18 2005
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=nYX0S1Rca8Dz3CMt/9vIy1UKnksBu7JuyXYbRLDUDMHMxK8VVixnaxWD+WUQqXJwEMhTLrB2Vz2HkyBZaoWMWM2hJkR0J8m/opjz2ioDp46dQ4YsxNSqBO1+aFrXFfLCfCQOByyUykraBTze6cNc/+Oy0+hHQP5kxLNUQbg3iCI=
> If we, is the US department of commerce, the answer is probably yes.
> The only operational significance, is that there is no way easy way of
> estimating in advance the effect of removing valid DNS information from the
> system, unless you are the administrator of the system concerned (and even
> then mistakes happen - not when I do it of course<cough>).
> i.e. It may be that a nameserver called "ns1.example.com" supports domains in
> a completely different TLD, like "example.co.uk", which belongs to an
> important organisation or service.
Okay, so i am not talking about blocking or removing a name server. I
am talking of removing that offending entry (like www.abc.com) from
the whois database or whereever the central database is mantained.
> That said spammers routinely have domains, and nameservers, removed with very
> little if any damage to legitimate Internet users.
> The real question is should we, words don't kill people, people kill people.
Class of 2004
Institute of Technology, BHU