David Iyoha wrote:
> Hello Scott,
>
> I like the general architecture.
>
> The only aspect I disagree with is the ability of the RSP to manually
override
> the renewal notice after it has become due. I think at that point since the
> customer is in danger of permanently loosing their domain name the admin and
> tech contact have to be contacted to give them a chance to save it.
>
> ie The RSP may have incorrectly (accidentally) configured the renewal
> information, or is intentionally trying to make the customer lose the domain
etc
No, I think it's a needed feature. In my database I'm allowing the customer to
say that "no, I don't want to renew this domain." So they select that option
for a domain and then I continue sending them "WARNING! your domain is about to
expire" messages, I'm basically spamming them.
There are plenty of other ways that an RSP can mess-up their customers. But
really, an RSP has no economic interest in bungling up renewals... in fact the
RSP has an economic interest in doing the renewals correctly... the RSP wants
to collect the renewal fees.
If you really want, make the "no, I don't want to renew a domain so don't warn
me when it expires" attribute customer settable for each domain through the
customer management interface. And also allow the RSP the ability to control
this attribute in the reseller login. This allows the customer to see any
mistakes that the RSP might have made.
David Harris
President, DRH Internet Inc.
[EMAIL PROTECTED]
http://www.drh.net/
