Warning... this is a rambled and unstructured response...
Is response to the recent discussion about mass changing of tech contacts, name server
entries, among others, and also selective mass changing of same, heres my thoughts on
the subject...
First and foremost, I think a single 'change all' function for resellers is required.
- We recently acquired a new secondary DNS server, but haven't updated the current 250
odd domains we have as we haven't had time to go through each and every one.
Next of importance is a 'change all' for each profile - for resellers with clients who
register many domains. This is possible for contact information, but not for
nameserver information - that still appears to be one-by-one.
Logically, the next is 'change all' for one domain only, which of course, is 'change
one', and which we have in place.
By 'change all' I mean, change all tech contact, change all dns, or whatever.
The other options are the selective changes
Suggestions are 'change from list' for resellers and 'change from list' for each
profile. i.e. you select from a list which domains to apply the change to.
More funky searches to generate a list are options, but they are luxury options.
Yes, selecting all that contain 'monkey' and 'drunk' is useful, especially when you've
thousands of domains to go through, but it's not the highest priority.
If it works on a 'list all, select some, submit once' basis, then more advanced
searching is just cosmetics.
You mention maintaining several RSP tech contact profiles - I don't think this is
necessary. The tech contact for resellers should be the person with overall technical
responsibility for their opensrs client implementation.
It should not be taken to have anything to do with the domains been hosted through the
system. Now, I know that often it will be, but that's coincidence, not a standard.
For profiles, each domain can already have individual information, so the question is
made redundant.
The only relevance I can see is for people either using register.cgi instead of
reg_system.cgi, or for people not using client software at all, and doing it all
through the resellers site. In these cases, I would advise a stance of, 'well, that's
what ya get...'. Otherwise, what's the point of client software...
Summary: Put in place global changing for resellers and profiles, and 'select from
list of all' for resellers and profiles. Then think about (cosmetic) searches. And
there is no need for multiple RSP tech contacts.
-Feargal.
--
Feargal Reilly,
Systems Administrator,
The CIA.
+353-86-8157621
> 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]
>
>
