Ok...
Turns out there's a small logic problem. When we're checking for
nameservers, if we don't get an "OK" response, we give this error. So, if
we get NO response (the .us registry is intermittent, we're working on
stabilizing that from you and your customer's POV) this error gets spit
out...
We're altering that logic, keep trying :)
Charles Daminato
OpenSRS Product Manager
Tucows Inc. - chuck@tucows.com
> -----Original Message-----
> From: owner-discuss-list@opensrs.org
> [mailto:owner-discuss-list@opensrs.org]On Behalf Of Phillip Beazley
> Sent: April 25, 2002 1:11 PM
> To: Charles Daminato
> Cc: discuss-list@opensrs.org
> Subject: RE: .US Launch
>
>
> Heeeeeeeelp. :)
>
> For awhile I was getting this error about half the time
> (resubmitting from
> Pending worked fine) but now it's constant.
>
> Order XXXXXXX (xxxxxxxxx.us) not registered: Request failed validation:
> Name server 'ns1.futuresights.com' is not found at the registry. This may
> be a temporary error.Please double check the nameserver and
> re-submit. Name
> server 'ns2.futuresights.com' is not found at the registry. This may be a
> temporary error.Please double check the nameserver and re-submit. Name
> server 'ns3.futuresights.com' is not found at the registry. This may be a
> temporary error.Please double check the nameserver and re-submit. .
>
>
> --
> Phillip Beazley
> FutureSights -- Website Hosting, Development & E-commerce
> Visit http://www.futuresights.com/ or call 727-578-9600.
>
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:37:10 EDT