If you're getting this message consistently its likely the nameservers do not exist at the registry, and you can add them through the Registry nameservers link from the RWI.
Tanya Charles Daminato wrote: >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. - [EMAIL PROTECTED] > >>-----Original Message----- >>From: [EMAIL PROTECTED] >>[mailto:[EMAIL PROTECTED]]On Behalf Of Phillip Beazley >>Sent: April 25, 2002 1:11 PM >>To: Charles Daminato >>Cc: [EMAIL PROTECTED] >>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. >> > >
