Read through for some comments... Charles Daminato TUCOWS Product Manager [EMAIL PROTECTED]
On Tue, 26 Feb 2002, Robert L Mathews wrote: > At 2/26/02 2:02 PM, George Kirikos wrote: > > >What would the side effects be? > > Well, the two already mentioned: it doesn't allow you a grace period to > unlock the domain if you realize you forgot to do it before transferring > (meaning you have to go back and resubmit the order from scratch at the > other registrar), and it doesn't allow you to change the nameservers > without unlocking it and remembering to relock it afterwards. > A *possible* enhancement could place an error message when changing nameservers, and then give the registrant the choice to have the system automatically unlock/change/lock. Like: "This domain is currently locked. Would you like me to unlock the domain, make these nameserver changes, and lock the domain for you?" Of course, that could be written by a savvy programmer, as that's all client side ;) > It would be nice if registrar transfer systems (including the OpenSRS > client) would detect that a domain name is locked at the registry during > the transfer lookup phase, if that's possible (can registrars find out if > a domain is locked by doing a query?). Unfortunately this isn't possible. A registrar cannot place any kind of query on a domain name if it's not the sponsoring registrar. All we can determine is if the domain exists (not the expiry date to prevent transfer attempts < 60 days, nor prevent domains from being transfer attempted if on lock *sad*). This, unfortunately, is a[nother] registry limitation > > -- > Robert L Mathews, Tiger Technologies > > "The trouble with doing something right the first time is that nobody > appreciates how difficult it was." This applies to older siblings too! ;)
