We do not have a reliable realtime method of verifying nameserver, unless
they are 'created' under OpenSRS - and that's a limited set mostly. The
Registry (normally) either accepts or denies the attempted nameserver
entity.
Charles Daminato
TUCOWS Product Manager
[EMAIL PROTECTED]
On Mon, 2 Apr 2001, Matt Prigge wrote:
> True, but that is far from reliable enough to be used in automatically
> validating nameservers through the full-access implementation. Although
> crsnic whois is more reliable than most, the lag on that whois server is
> sometimes enough to time-out a whois client (I have seen this happen quite a
> few times). I think a DNS or, ideally, OSRS API, implementation would be
> much more reliable.
>
> - Matt
>
> ----- Original Message -----
> From: "Charles Daminato" <[EMAIL PROTECTED]>
> To: "Matt Prigge" <[EMAIL PROTECTED]>
> Cc: "WebWiz" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Monday, April 02, 2001 4:27 PM
> Subject: Re: Failing Registrations
>
>
> > You can perform a whois query against whois.crsnic.net and if registered
> > an entry will appear:
> >
> > $ whois -h whois.crsnic.net ns1.ihigh.com
> >
> > Server Name: NS1.IHIGH.COM
> > IP Address: 208.184.21.13
> > Registrar: NETWORK SOLUTIONS, INC.
> > Whois Server: whois.networksolutions.com
> > Referral URL: www.networksolutions.com
> >
> > Charles Daminato
> > TUCOWS Product Manager
> > [EMAIL PROTECTED]
> >
> > On Mon, 2 Apr 2001, Matt Prigge wrote:
> >
> > > An OpenSRS guy let me know offlist that there was a problem with the way
> the
> > > two nameservers I was looking for were stored in the OpenSRS database.
> He
> > > said that he cleared up the problem. Im not really sure what could cause
> > > this, but as long as its fixed, I suppose Im happy.
> > >
> > > Speaking of this issue, does anyone know of a reliable way of verifying
> > > registered nameservers? My best idea so far is doing a DNS lookup
> against
> > > the gTLD root nameservers, but this would only work for gTLDs (if you do
> an
> > > nslookup for a registered nameserver, youll get the servers glue A
> record in
> > > response, if you do one for a non-nameserver, youll likely get a
> referral).
> > > You would need to carry a list of the root servers for all of the TLDs
> you
> > > supported in order for that to work for all TLDs. Doing a whois against
> > > CRSNIC is not reliable enough for reasons we all have seen lately. Since
> the
> > > software does allow one to enter their own custom nameserver (if you
> choose
> > > to set it up that way) it seems to me that you should be able to verify
> that
> > > information before the order takes place. Ideally that should be done
> > > through the API, but I wont hold my breath for that. Any thoughts on
> this
> > > are welcome.
> > >
> > > - Matt Prigge
> > >
> > >
> > > ----- Original Message -----
> > > From: "WebWiz" <[EMAIL PROTECTED]>
> > > To: <[EMAIL PROTECTED]>
> > > Sent: Monday, April 02, 2001 11:07 AM
> > > Subject: Re: Failing Registrations
> > >
> > >
> > > > My guess is that there's a connectivity problem between
> > > > OpenSRS and the root servers. OpenSRS tried to do a query
> > > > to verify that the nameservers are legit, failed to get
> > > > a response from the registry before timing out, and
> > > > reported this as "non existent name servers".
> > > >
> > > > Just speculation, mind you, but I did notice that
> > > > www.crsnic.net was VERY SLOW to resolve these names
> > > > when I tried it (as far as that goes, it was slow to resolve
> > > > my nameserver names, too).
> > > >
> > > > Regards,
> > > > Eric Longman
> > > > Atl-Connect Internet Services
> > > >
> > > > +-------------------------------------------------------+
> > > > | Atl-Connect Internet Services http://www.atlcon.net |
> > > > | 3600 Dallas Hwy Ste 230-288 770 590-0888 |
> > > > | Marietta, GA 30064-1685 [EMAIL PROTECTED] |
> > > > +-------------------------------------------------------+
> > > >
> > > > ----- Original Message -----
> > > > From: "Matt Prigge" <[EMAIL PROTECTED]>
> > > > To: <[EMAIL PROTECTED]>
> > > > Sent: Monday, April 02, 2001 1:41 PM
> > > > Subject: Failing Registrations
> > > >
> > > >
> > > > Hi All,
> > > > I suspect this problem may be happening to others, so I wanted to
> > > bring
> > > > attention to it quickly. A customer recently (within the hour) tried
> to
> > > > register a domain name with ns1.ihigh.com and ns2.ihigh.com. The
> server
> > > > (API) rejected both of them with the following error:
> > > >
> > > > <domain>: Registration Failed: ns1.ihigh.com does not exist.
> Nameserver
> > > > ns2.ihigh.com does not exist.
> > > >
> > > > Both of these servers resolve correctly in DNS and also are listed
> > > correctly
> > > > in the root whois server. So, as far as I can tell, this should not be
> > > > happening. If anyone has any ideas as to why this would happen, please
> let
> > > > me know. Thanks!
> > > >
> > > > - Matt Prigge
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
