Currently we're in the process of creating a spec that has all this
information, unfortunately for now the only provision is in the code.
This information will not be changed, as our database is built this way
and those regexp's haven't changed since their inception (except the
addition of + to the phone number fields).
There's size definitions in the README file included with the client code,
the rest is the run of the mill a-z/A-Z/0-9 type stuff.
The only way for an RSP to verify a nameserver is to try it, or use a
'test' style domain and attempt to modify its nameservers on the live
system with manage.cgi style commands.
david2@amandine.nfrance.com wrote:
>
> On Tue, May 16, 2000 at 07:02:33AM -0400 or thereabouts, Charles Daminato wrote:
> > The regexp only exist currently in the Perl code available online. Some
> > is contained in each cgi, some is in OpenSRS.pm (and shared by all the
> > code).
> >
>
> I don't have the time to read again the cgi provided in the client
> and I don't want to read it each time a new version is released.
> What I want is a small page that describe what the server needs for each
> field. Cause all registration are queued, if we do not check correctly
> what the user provide, when we will proceed queued orders some of them
> will be refused without notifying the user. We would like to avoid this
> by keeping sync our regexp verifications with the regexp used by server.
> Maybe the better solution for us (client developper) is to add a small
> flag 'test' in the register_domain command and when test is set the
> server only check the template but do not perform the domain.
>
> > The verification of a name server is done via the root registry. While
> > doing a whois will verify the existence of an HST record created at
> > InterNIC, it wont show the existence of name servers created by other
> > ICANN accredited registrars.
> >
> > This functionality is done automatically by the server when you attempt to
> > add a name server for a server :)
> >
>
> I'm not talking about adding nameserver, I would like to know the way to
> verify if a nameserver will be accepted by the opensrs server while
> ordering a new domain. It cannot add it automatically cause the register
> command does not allow me to specify IP address.
>
> Thanks again :)
>
> > On Tue, 16 May 2000 david2@amandine.nfrance.com wrote:
> >
> > > Hi,
> > > we wrote our cgi client from scratch and we need to sync template
> > > verification with your server (eg: field contains only blank spaces)
> > > Where can I find the list of all valid regexp I have to apply to
> > > each field?
> > > We need to know what the server is waiting for.
> > > It would be great if you could maintain a small page like:
> > > last name [required]: regexp
> > > Org [required]: regexp
> > > address1 [required]: regexp (At least 1 letter.)
> > > address2 [optionnal]: regexp (At least 1 letter.)
> > > ...
> > >
> > > ChangeLog is great but I can't find all info I need in it.
> > >
> > > Another question:
> > > I test the ns existance by connecting to whois.crsnic.net:whois and
> > > I ask "nameserver $ns", is this test valid?
> > >
> > > Thanks
> > >
> > > --
> > > David Causse
> > > david2@nfrance.com
> > >
> > >
--Charles Daminato OpenSRS Technical Operations chuck@opensrs.org
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:35:31 EDT