You may wish to post this question to dev-list as it's more geared towards the nitty-gritty and "guts" of the system and API
You should refresh your nameserver list with a GET (and thus the sortorder variables) each time you do a command to ensure you've got things ok... Charles Daminato OpenSRS Product Manager Tucows Inc. - [EMAIL PROTECTED] > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Andy Coates > Sent: July 26, 2002 9:19 AM > To: [EMAIL PROTECTED] > Subject: Nameservers sortorder > > > Hey, > > I've got a bit of a puzzle regarding the sortorder flag when modifying a > domain to change the nameserver_list > > When you issue the 'remove' action, you specify the sortorder to remove, > i.e. if you had nameservers with 4 entries, having sortorders 1 through > 4 and you removed 3, you'd end up with 1,2, and 4 sortorder values. If > you then go on to add a nameserver, it will be added as 5 ending up with > sortorders 1,2,4,5. > > Does this mean that whenever a delete occurs, we should also issue a > modify to re-order the sortorders? > > It doesn't explicitly say what the sortorder is actually for from what > I've read, but I presume it's the order in which they are shown in whois > output? If that's the case, how does one go about inserting a > nameserver at, for example, sortorder 1? Do you have to add a > nameserver, then modify the rest of the nameservers to be the right > order? > > Its confusing the hell out of me, maybe because I don't have a clear > understanding on why its used - so if anyone can explain that'd be > great. > > Thanks, > Andy. >
