[dns-operations] Delegation checking (was: Re: Some DNSSEC trivia)
jrhett at svcolo.com
Wed Jan 9 20:22:28 UTC 2008
Yes, too true. I'm sorry, I actually misread registry for registrar
when I said what I did. Sorry for the red herring.
*shrug* In this case, notification to registrar who has
responsibility (and thus liability) to inform the registrant.
On Jan 9, 2008, at 11:20 AM, Andrew Sullivan wrote:
> On Wed, Jan 09, 2008 at 11:05:49AM -0800, Jo Rhett wrote:
>>> registries attempt to enforce this rule without the ability to
>>> registrants that their names are going dark.
>> People keep saying this, but the registration agreement as far back
>> at 1993 (earliest I have) says that it's the registrant's
>> responsibility to keep their contact information up to date.
> That doesn't matter. Registries aren't allowed to contact the
> registrants directly. They have to go through the registrars. This
> isn't that surprising: retailers don't like retail customers to be
> talking to wholesalers generally. So if the registry performs an
> action on a domain, and it causes the domain to go dark, there is the
> potential of the registrant quite correctly complaining that s/he
> wasn't informed of the action by the registry.
> This is the reason, I expect (but IANAL, &c.) that ICANN's pages and
> just about every registry's tech support will tell registrants to
> talk to their
> registrar about problems _first_: the registrar is supposed to be the
> only point of contact between the DNS and the registrant.
> I understand why people of a technical bent think the above state of
> affiars is inefficient and prone to needless points of failure. But
> if you look at it as a piece of social engineering designed to work
> around an old state of affairs (a single registry company with control
> over several important TLDs, and anxiety on the part of the community
> about same), it makes a certain amount of sense.
> Andrew Sullivan 204-4141 Yonge Street
> Afilias Canada Toronto, Ontario Canada
> <andrew at ca.afilias.info> M2P 2A8
> jabber: ajsaf at jabber.org +1 416 646 3304 x4110
Silicon Valley Colocation
Support Phone: 408-400-0550
More information about the dns-operations