Hi all,
This is definitely an issue we're actively involved in. It's a
dangerous precedent, and I think that sentiment was largely shared
among registrars at the Registrars Constituency meeting during the
recent ICANN conference (Afilias came in to make a presentation on
this new policy). We'll be working closely with the Constituency to
address this issue.
adam
--
Adam Eisner
Product Manager, Domains
Tucows Inc.
On Jul 8, 2008, at 5:43 AM, Simon Waters wrote:
On Tuesday 08 July 2008 09:46:42 George Kirikos wrote:
However, if the registry yanked the domain name itself from its zone,
the website and any services associated with it would go into a black
hole.
Yes, I was merely noting that if the registry yanked our company's
main domain
name, we'd only lose 2 out of 4 name servers for the things that
our DNS
servers do that are probably more important than the company itself.
I think this is the definitive argument for not removing stuff from
the DNS
lightly, is that the consequences are incalculable because there is
no way to
tell what domains have name servers in this domain query (or even
the less
complete queries - tell me what name servers are in this domain -
or what
domains this name server serves).
As such any director of a registry should be asking their insurers
exactly how
bad it could be if they accidently yanked a domain name that had
important
name servers in (say something obscure like co.id), versus what
sort of
liability might be incurred by providing a domain someone else is
choosing to
serve illegal content under. I suspect the answers are "lots" v
"none".
_______________________________________________
domains-gen mailing list
[email protected]
http://discuss.tucows.com/mailman/listinfo/domains-gen
_______________________________________________
domains-gen mailing list
[email protected]
http://discuss.tucows.com/mailman/listinfo/domains-gen
