The important thing is NO active information can be changed and cause the
domain to point somewhere else. Even if they change ownership, it will still
have a delay as they will have to go through the channels to try and have it
un-locked. The RSP will know it's not their domain and hopefully notify the
owners of what has happened.... ;)

I am glad to have what we do... Thanks Scott! (And Chuckles when your back
;) Might not be a bad idea to lock the ownership change in the future...


--
Mike Allen, 4CheapDomains.Net
[EMAIL PROTECTED]
http://www.4CheapDomains.Net

----- Original Message -----
From: "Ken Anderson" <[EMAIL PROTECTED]>
Cc: "OpenSRS dev-list" <[EMAIL PROTECTED]>
Sent: Wednesday, March 27, 2002 2:21 PM
Subject: Re: domain locking


> Thanks for pointing out the docs, but they do not answer the "why"
> question.
> Seems to me that a "lock" on a record should at least lock the admin
> contact info as well as the DNS?
> Perhaps this is not possible for some other reason?
> Did I miss another doc?
> Thanks,
> Ken Anderson
> Pacific.Net
>
>
> Ken Joy wrote:
> >
> > As has been fully documented and referred to once or twice on the list
today
> > alone, locking prevents:
> >
> > a) registrar transfers
> > b) RSP2RSP transfers
> > c) DNS changes
> >
> > Please read the documentation before posting questions like this.
> >
> > Thanks,
> >
> > Ken
> >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> > > Behalf Of Ken Anderson
> > > Sent: Wednesday, March 27, 2002 1:46 PM
> > > To: OpenSRS dev-list
> > > Subject: domain locking
> > >
> > >
> > > Okay, so domain locking can protect resellers from domain hijacking of
> > > unknowing customers by NetSol and others, but it seems that it only
> > > locks certain parts of the domain name record. Why is this? Is there
any
> > > granular control over what is/isn't locked?
> > > Thanks,
> > > Ken Anderson
> > > Pacific.Net
>

Reply via email to