Hi Robert,
Unfortunately I don't think I can do that. Our client is built on quite a few
different layers & pulling this part of it out would not be a simple task.
I'll see what I can send you off list however. Monday okay?
Thanks,
Doug.
Quoting Robert <[EMAIL PROTECTED]>:
> Sorry - pressed the button too quick....
>
>
> What I meant to ask was, would you care to share your perl script? Although
> I have about 50 individual domains to change, so perhaps this 'batch' mode
> wont do the trick?
>
> cheers
> robert
>
> > Hi Russ,
> >
> > I have a Perl script I use for doing multi DNS updates like this, and it
> runs
> > about one update every second or two. The guts of this are the call:
> >
> > my $xcp_request = {
> > action => "modify",
> > object => "domain",
> > attributes => {
> > domain => $domain,
> > reg_username => $ref_userinfo->{reg_username},
> > reg_password => $ref_userinfo->{reg_password},
> > data => "nameserver_list",
> > nameserver_list => \@ns_data,
> > },
> > };
> >
> > You'll of course require the username & password for the client profile to
> run this.
> >
> > Enjoy :)
> >
> > Doug.
> > Quoting Russ Goodwin <[EMAIL PROTECTED]>:
> >
> > > Hi-
> > >
> > > I had a client with 400 domains in one profile call today to have their
> > > nameservers changed (they are moving to another ISP). I know about the
> > > 2.0.1-multidns version of the client which is supposed to do this, but
> > > found it was processing at a rate of about 1-2 domains per minute (400
> > > domains @ 1/min = almost 7 hours!). I hacked up a wrapper that POST'ed
> to
> > > my manage.cgi one domain at a time, and ran it with batches of 10
> domains
> > > at a time. I was able to get up to 5-8 domains per minute this way, but
> > > any gains were lost in the time it took to set up 40 batches.
> > >
> > > It doesn't seem like there is a good answer to this question in the
> > > archives, so I'll ask it: does anyone have a good solution for bulk or
> > > mass nameserver changes? (aside from the multidns client code)
> > >
> > > -Russ
> > >
> > >
> > >
> >
> >
> > Thanks,
> >
> > Doug.
> >
> > --
> > Doug Friend
> > http://register4less.com
> >
>
>
>
Thanks,
Doug.
--
Doug Friend
http://register4less.com