Hi Faeren, there was (is) an issue with issuing bulk dns updates for domains managed by PIR (.info/.org) - the way that registry deals with multiple ns updates sent in one API call is hmm.. slighly unorthodox and so the results may be inconsistent in some cases. We've put in a workaround which will be effective with the next cutover (Oct 7?) and that issue should go away then.
Regards, Vlad On Sat, 25 Sep 2004, Faeren Madza wrote: > Hi George, > > Be careful with the [Bulk Domain DNS Changes] function, especially if > you are doing a lot of domains at one time. Preferably try it on some > non-critical domains before using it for real. Here is why: > > I had begun working with someone from OpenSRS many months ago on a > script that did this via API, however, it was quite inconsistent-- > Sometimes it made the changes, sometimes it removed the old, but did not > add the new, sometimes it did nothing. > > I tested it extensively and could not ever get consistent results based > on the same set of criteria. Unfortunately, I have found the same to be > true of the web form they have recently made available. > > > My test process as well as results have been sent to them more than > once, and I have also followed up repeatedly. At one time someone from > there tried to tell me that I did not understand the difference between > 'Assign nameservers' and 'Add nameservers.' Thankfully, I was able to > get past him and although they now admit there is an issue, all I have > gotten in 2 months is "We're looking into it." > > My 2 cents. > > > > > Faeren. > > > On Sat, 2004-09-25 at 08:05 -0700, George Kirikos wrote: > > Hello, > > > > I was just playing with the recently added "Bulk Changes" feature in > > the RWI. It's very powerful, and works great. If folks haven't tried it > > out yet, it can save one a lot of time. > > > > A couple of features that would be nice might include: > > > > a) Text mail option (right now, all the emails sent out are HTML) > > b) The ability in the Bulk Search (and in the regular search) to search > > by Lock Status (i.e. return a list of all unlocked domains, or all > > locked domains). Running a periodic check for all unlocked domains in > > one's account would thus reveal possible insecure domains. > > > > Sincerely, > > > > George Kirikos > > http://www.kirikos.com/ >
