On Mon, 11 Dec 2000, at 04:33 [=GMT-0800], [EMAIL PROTECTED] wrote:
> > What should I think of this message:
> >
> > "Registration attempt for chinadirect.net failed: Request failed
> > validation: Nameserver pan.bijt.net does not exist in the registry."
>
> I sometimes see that when OpenSRS cannot get a response from the registry.
> It doesn't matter if it's a new domain, transfer domain, a domain at
> OpenSRS or a domain elsewhere. Trying again in a few minutes, the error
> goes away.
So, it has nothing to do with the transfer in progress? I am
relieved. Thank you!
It was strange that a.root-servers.net still knew about it anyway, if
something was seriously wrong :-)
Anyway, now I have a feature request then. Turn this nameserver
validation off. There are times when there is no time to try again
after a few minutes, as when a name is released.
I do not object to procedures to see that there are proper nameservers
for domains. On the contrary, this could be much stricter. But this
check of the nameservers against the registry can be fatal when
'grabbing' a domain name. And it doesn't mean a thing, as anyone can
just enter what he likes, e.g. mydomain.com's nameservers, even if
they know nothing about the domain and never will.
If turning this off generally is not possible, maybe on a reseller
basis? Or a possibility to register without nameservers? Even though
it is wrong?
Thanks.
--
Marc Schneiders (rest in header)
