(cc list trimmed (they're all on the discuss-list anyway :))
Easy enough to hijack if needed; just change your 'default' nameservers
to whatever the client is currently using.
As for the legal implications for having this kind of functionality, they
are exactly the same whether you roll-your-own, or it's provided by
Tucows.
Mark.
On Fri, 7 Sep 2001, Peter Kiem wrote:
> > You can easily code this into the reg_system.cgi script, by taking
> > some code from the manage.cgi script, right after the registration is
> > successful, have it send a login command, and then the create sub user
> > command.
> >
> > (Yes, my typical, "there is a way you can do this yourself" solution)
>
> Yes but as Charles has pointed out there maybe legal implications in doing
> that. I doubt my customers would care but I don't want to go there.
>
> Frankly, if the domain is delegated to *MY* nameservers I should have the
> ability to maintain that information. If the domain is not pointing at *MY*
> nameservers then fair enough, I shouldn't be able to change them.
>
> How about this? Each reseller gives default DNS servers that the domain is
> registered under. If the domain's current nameservers MATCH EXACTLY the
> defaults set in the RSI then we have the ability to change them?
>
> That way if the customer changes them themselves then we cannot change them
> back, hold them hostage etc. But if the nameservers are own settings then
> we can change them if needed.
>
> Regards,
> +-----------------------+---------------------------------+
> | Peter Kiem | E-Mail : <[EMAIL PROTECTED]> |
> | Zordah IT | Mobile : +61 0414 724 766 |
> | IT Consultancy & | WWW : www.zordah.net |
> | Internet Hosting | ICQ : "Zordah" 866661 |
> +-----------------------+---------------------------------+
>
>
>
