Hello Charles,
Monday, February 26, 2001, 12:19:20 PM, Charles Daminato wrote:
> The short answer is no, and no.
> You can get your clients to change things instead of logging in for them (I
> know the logistics of that sucks).
> There's not an easy way to do this systematically. If you've registered
> (for example) 10 names, and 3 of your users have already altered DNS to
> point to another system - THEN we do a mass update, it could break these
> domain names.
> Yes, a handle type system could fix this. It's something we're working on
> (we say that often, don't we? *grin*).
It would be somewhat trivial for someone to write a quick function to
make a change to a customers nameservers, and to have that appear in
the customer's manage domains interface as a button they click to make
the change once they have logged in.
This function would make the necessary nameserver or other changes.
Add this to the template:
<form method=post action="/manage.cgi">
<input type=hidden name=action value="do_modify_nameservers">
<input type=hidden name="fqdn1" value="ns1.userfriendly.com">
<input type=hidden name="fqdn2" value="ns2.userfriendly.com">
<input type=submit name=submit value="Click here to Approve this
change">
You make it very simple, they don't need to know the actual addresses
of the nameservers, they login and click the button.
--
Best regards,
William mailto:[EMAIL PROTECTED]
