The system is excessively picky about the names sever specification. I have forgotton all the problems / bugs -- I now just copy a previous (successful) registration so I can avoid the problem..
If memory serves; The problem typically goes away if you specfiy DNS server in lower case (UDNS1.ULTRADNS.NET & UDNS2.ULTRADNS.NET are the ones that get me all the time) and the servers must be valid and specified. For example I often register .INFO's and then have to manually delete the DNS servers via the manage interfaces (names that I'm purchasing for future use but want to avoid having domain speculators mine the ZONE for and monitor what I'm doing).
I really feel the interface should be more forgiving about what you enter. Perhap just a warning versus complete failure. I feel pretty strongly about this as it's very frustrating to manually enter an order and then have the entier order lost because of a single typo -- This really needs to be fixed!
On Fri, 21 Nov 2003 00:57:00 -0800 "Mike" <[EMAIL PROTECTED]> wrote:
Hi,
I'm receiving a 400: Fatal Server Error Occured when trying to add a
name server to a domain on the test system via the API.
I can update and remove name servers fine- I only get the error when
adding one.
I went through the archives and saw a few other related messages, but
didn't see any solutions- maybe I missed them.
I'm passing the command as:
Array ( [action] => modify [object] => domain [cookie] => 659305612:391169 [attributes] => Array ( [data] => nameserver_list [nameserver_list] => Array ( [name] => ns2.domaindirect.com [action] => add ) )
[registrant_ip] => 10.0.1.2 [protocol] => XCP )
as far as I can tell from the documentation, that's correct.
Any help would be appreciated.
On a side note- "Occurred" (in the error message) has two r's :)
Cheers,
Mike Pultz [EMAIL PROTECTED]
