Hello Doug,
Sunday, June 17, 2001, 1:41:38 AM, Doug Sisk wrote:
> This is just an asinine policy!
> All it does is create work for the RSP. It obviously wasn't originally
> intended to work that way - why would you even define an admin contact
> in the api if you were never going to allow RSP's to set it.
The admin contact can be whomever the owner chooses.
However, that person has the authority to completely change, transfer
ownership, cause a deletion, etc.
The role of the admin contact is effectively as the owner of the
domain name. This is a historical role.
I've said for years that any ISP who registers names for clients and
puts themselves down as Admin contact is at a very minimum committing
a very questionable act, and at worst an unethical one, bordering on
illegal when they use their position as admin contact to prevent the
registrant from making a change that they seek to the domain (Such as
switching providers, changing the contacts, changing the nameservers).
If I had a $1 for every domain I've seen held hostage by an
unscrupulous ISP or webhost who made themselves the admin contact for
customer domains, either because they believed they had the right to
because the customer owed them money (which they don't have the right
to do), or for some other imagined reason.....
I really see no reason why the registrant should not be listed as the
admin contact 100% of the time. For their own protection. Managing a
domain name, especially an OpenSRS registered domain, is simple
enough.
On that note, one thing I've been thinking about is adding context
sensitive help links to the various portions of the same OpenSRS
client interface. (You know, the little "?" links that pop-up a help
window)
Anyone interested in helping to come up with the text for the various
sections?
--
Best regards,
William X Walsh <[EMAIL PROTECTED]>
Userfriendly.com Domains
The most advanced domain lookup tool on the net
DNS Services from $1.65/mo
