Actually uh...

This is a long standing, known issue.  It's always been that way, and is as
a result of the way in which .info domains are "locked".  It's a seperate
"bug", if anything.

To explain:

.info provides us several "flags" for domain names.  Two important ones are:

updateprohibited - cannot change nameservers, cannot renew
transferprohibited - cannot transfer

In order to "mimic" verisign's LOCK, we decided (for .info) to enable
"Update/TransferProhibited" flags.  This had the unfortunate (and unrealized
until much later) effect of also preventing renewals on locked .info
domains.  We haven't quite made it to the point of asking you guys which is
more important from a "LOCK" perspective - denying transfers, preventing
nameserver changes, or both.

I can guess what the answer to that is... (this will be addressed in the
relatively near future)

Now... for .ORG:

PIR has provided us the SAME commands we have for Verisign's .org
implementation.  Which means we can only "LOCK" or "UNLOCK" the domain (no
minor differentiations like we have currently for .info).  Which means WE
can't actually fix this (per se), it's a Registry issue that we're
escalating and attempting to resolve.

We may put in a "unlock-renew-lock" mechanism, but this is VERY expensive (4
or 5 commands per renewal - we have to try, unlock, renew, lock, and ensure
we actually locked it).  So we're trying to work with the registry first.

--
Charles Daminato                  Life is not holding a good hand;
OpenSRS Product Manager           Life is playing a poor hand well.
Tucows Inc. - [EMAIL PROTECTED]    - Danish proverb

> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Doug Friend
> Sent: January 29, 2003 11:23 AM
> To: discuss-list
> Subject: Renewals for .info
>
>
> Hi all,
>
> Just found that renewals for .info domains also require unlocking
> before they
> can be renewed.
>
> OpenSRS is also now aware of this situation & adding it to the
> bug report on
> this issue.
>
>
>
> Thanks,
>
> Doug.
>
> --
> Doug Friend
> http://register4less.com

Reply via email to