Jim, Occasionally a domain gets into an inconsistent state which makes it give the "Domain not yet officially registered". The short answer is, we locally store domain data (most of it), including nameservers. When we try to update a domain but have an incorrect local nameserver we get a specific error which means (in some cases) the domain isn't fully registered (in other cases it means we're out of sync). This clears itself shortly (as we try to sync with the registry from time to time when performing operations on domains).
We're also working on better recognizing this state and handling it better (as part of an enhancement initiative). Let me know if you're still having this problem with the domain (offlist) and I'll dig deeper (as it usually resolves itself after a short while) Charles Daminato TUCOWS Product Manager [EMAIL PROTECTED] On Wed, 29 May 2002, Jim Carey wrote: > I have been trying to update a customers nameservers and get this error message: > > Unable to update nameservers: Modification Failed. Domain not yet officially >registered. > > the nameservers are: > > bne001n.server-dns.com > wic001n.server-dns.com.au > > both of which are pingable and both of which act as nameservers for the >server-dns.com domain ? > > cheers > > > > Jim Carey > www.OZbcoz.com discount domain registration > >
