I have also sent the following to [EMAIL PROTECTED] However, I thought I would seek advise/comment here from other developers. Are my observations (noted below) regarding the change in server-side response accurate? Am I correct that no error return codes are generated when invalid name servers are supplied or am I missing something? How are others handling situations where the name is pended and the customer thinks the name has been successfully registered to the name servers they supplied, but in fact are not? Rich ==================================== I'm encountering a problem with the action taken by the server-side script when invalid name servers are specified. During our testing (on both the test server and the production server) the action taken when an invalid name server was specified was to return an error. However, now when an invalid name server is specified, the following happens: (1) The domain is placed in the "Pending" area. (2) The customer is provided a domain confirmation registration number! (3) The customer receives a confirmation email informing him or her that their domain was successfully registered. (4) The client-side script receives a response indicating that the domain has been successfully registered. Questions: Is my observation correct that the action taken by the server with respect to invalid name server entries has changed? If the action has changed, what was the rationale for making the change? Why would a change be made that would remove from the reseller any and all control over what action is taken with respect to invalid name server entries? Can the server-side response be modified so the client-side script can "know" that the domain has been pended? Thanks. Rich Shockney RS Marketing
