Not to sound silly, but very useless.
If a customer has changed their technical contact to be someone else,
you can't tromp over their manually-input data.
If a customer is using their own custom DNS servers as opposed to the
defaults we provide, you can't tromp over their data.
Maybe something with checkboxes...
__ foo.com
__ bar.com
[Apply These Changes to Checked Domains]
or something like:
__ foo.com
__ bar.com
[Apply These Changes to Checked Domains]
[Apply These Changes to All Domains with Default Data]
so the RSP can say "ok, change everything that hasn't been changed",
or if its a small qty, "just change these few".
D
At 8:15 AM -0400 8/11/00, Scott Allan wrote:
>This is on our list - I can appreciate the inconvenience of this
>function not yet existing.
>
>Seems like there is good demand for it - I will make it a higher priority.
>
>FWIW, to help us spec this out, how useless would the feature be if
>it could only be applied to all names in a reseller profile? I think
>ultimately when it is implemented RSP's should be able to:
>
>: either maintain several different RSP profiles for tech contact
>info and be able to apply changes globally
>: make changes against search results, or a matching info query
>
>I would appreciate your feedback so I can determine if perhaps it is
>worth implementing this function in a two step process, with a first
>version that offers only wholesale changes for all names managed by
>an RSP.
>
>Regards,
>
>sA
>
>At 10:13 PM 8/10/00 -0700, you wrote:
>>At 8/10/00 9:56 PM, Phillip Beazley wrote:
>>
>>>I've got the same problem and another similar question.
>>>
>>>I need to add another nameserver record to all the domains we host. Other
>>>than going into every domain's account (impossible), how would I go about
>>>this?
>>
>>Hate to be a "me-toobie", but me too. I need to change the tech contact
>>information on 300 domains, none of which I have the passwords for.
>>
>>--
>>Robert L Mathews, Tiger Technologies
>
>Scott Allan
>Director OpenSRS
>[EMAIL PROTECTED]
