That is one of the main purposes of domain locking. To prevent someone (Hacker) from changing name servers and interrupting your traffic ;)
-- Mike Allen, 4CheapDomains.Net [EMAIL PROTECTED] http://www.4CheapDomains.Net (812) 275-8425 - Office (815) 364-1278 - Fax ----- Original Message ----- From: "Derek J. Balling" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, April 23, 2002 8:55 AM Subject: Locking and Unlocking Domains > I put this out to the community for discussion: > > The manage.opensrs.net web interface does not seem to allow users any > ability to actually change their lock/unlock status, presumably > because not all resellers offer lock, and OpenSRS doesn't want to > have folks locking domains that are with resellers that don't offer > locking. > > However... the manage interface CERTAINLY SHOULD have the ability to > UNLOCK a domain if the domain is locked. > > Consider the case where "reseller goes belly-up", or "reseller has a > password-protected web interface and revokes the domain-holder's > access". In both of those cases, the domain-holder needs to have the > ability, independent of the reseller in question, to free up their > domain to move it elsewhere. > > Also, I noticed that you can't change the nameservers under a domain > if it is in the locked state? Was this mentioned somewhere I didn't > notice? I thought all locking did was prevent "domain slamming", not > also prevent NS changes. > > D > > -- > +---------------------+-----------------------------------------+ > | [EMAIL PROTECTED] | "Thou art the ruins of the noblest man | > | Derek J. Balling | That ever lived in the tide of times. | > | | Woe to the hand that shed this costly | > | | blood" - Julius Caesar Act 3, Scene 1 | > +---------------------+-----------------------------------------+ >
