man i feel like a dumbass...i didnt even check that, i would have expected a 
server error for the wrong key 'sort_order'.  But maybe since it's optional 
depending on the command type, that doesn't return an error.  Thanks for the 
extra set of eyes

Justin

On Wednesday 17 December 2003 5:04 pm, you wrote:
> Is it "sortorder" or "sort_order"?  You've got both in your example.
>
> I can't remember which it is, but I remember this bit me once before,
> so maybe check the API.
>
> - Colin
>
> On 17-Dec-03, at 3:48 PM, Justin Dagen wrote:
> > Okay, I haven't been able to track this same error down anywhere, so
> > here
> > goes:
> >
> > I am working on the 'update nameservers' function and have come upon
> > the
> > following error:
> > [response_text] => Duplicate sortorder detected for ns2.netsville.com
> > [response_code] => 465
> >
> > I'm not sure what the problem is, but here is what is currently
> > returned as
> > the nameserver list: (unimportant parts cut out for brevity)
> >                     [0] => Array
> >                             [ipaddress] => 216.42.80.10
> >                             [sortorder] => 1
> >                             [name] => ns1.netsville.com
> >                     [1] => Array
> >                             [ipaddress] => 216.42.80.11
> >                             [sortorder] => 2
> >                             [name] => ns2.netsville.com
> >
> > And I am trying to test by simply switching the two sortorders:
> > COMMAND:
> >     [action] => modify
> >     [object] => domain
> >     [cookie] => *cookie*
> >     [registrant_ip] => 69.55.64.235
> >     [attributes] => Array
> >             [data] => nameserver_list
> >             [nameserver_list] => Array
> >                     [0] => Array
> >                             [name] => ns1.netsville.com
> >                             [sort_order] => 2
> >                             [action] => update
> >                     [1] => Array
> >                             [name] => ns2.netsville.com
> >                             [sort_order] => 1
> >                             [action] => update
> >
> > And the error from above is returned.  I thought maybe I couldn't add
> > ns1 with
> > sortorder 2 while ns2 was already sortorder 2 so i tried sending them
> > as 4
> > and 3 instead of 2 and 1  (so still switching the sortorder, but to
> > sortorders not already in use), and still got this error.
> >
> > Thanks,
> >
> > Justin
> >
> >
> > --
> > Justin Dagen
> > Systems Administrator
> > Netsville, Inc.
> > http://www.netsville.com

-- 
Justin Dagen
Systems Administrator
Netsville, Inc.
http://www.netsville.com

Reply via email to