This is exactly the case, it is a relatively new registration through
OpenSRS and we are now entering the NSI jungle.
My nameservers (and domains before transfer) were originally registered
several years back at NSI and I see they are still in their database but
using the same query, the ones on the new domain are not.
I gave the client a work-around until he can get them straightened out.
After this hassle he now has no love lost for NSI and an appreciation of the
easy management that OpenSRS provides.
I hope you guys can bring this issue up on a more official with ICANN. The
initial reaction of a client is that his domain registration is somewhat
"less real" than one with NSI. Grrrrr
John Blakney <mailto:[EMAIL PROTECTED]>
Visual Database Systems / Little Rock
> [mailto:[EMAIL PROTECTED]]On Behalf Of Charles Daminato
> Sent: Friday, September 14, 2001 7:17 AM
> To: Robert L Mathews
> Cc: [EMAIL PROTECTED]
> Subject: Re: Nameservers and NSI
>
>
> I've seen this happen a couple of times on "new" nameservers that never
> existed at NSI (as opposed to some that were transfered away from them..)
>
> Basically they have to update their legacy system that forces an "HST"
> record to be present. They updated it *somewhat* - only to the point
> where you cannot create the HST record they are forcing you to use...
>
> You have to basically keep hammering their support services until you find
> someone clueful, or go higher up if you can. Explain that the nameserver
> exists, I only need to use it on NSI domains.
>
> Or... transfer the domains away *smirk*
>
> Charles Daminato
> TUCOWS Product Manager
> [EMAIL PROTECTED]
>
> On Thu, 13 Sep 2001, Robert L Mathews wrote:
>
> > At 9/13/01 8:55 PM, John Blakney wrote:
> >
> > >One of my client's domains which is registered through OpenSRS has two
> > >nameservers registered, also through OpenSRS. These properly
> appear in a
> > >nameserver lookup at Internic.net. Now my client is trying to associate
> > >those nameservers with domains registered through NSI. They
> are giving him
> > >the royal run-around claiming that the nameservers also have to be
> > >registered with NSI, putting him through the depths of hell
> like only NSI
> > >can accomplish. The way it was left today they want a copy of
> his drivers
> > >license.
> > >
> > >My questions are: 1. Is NSI in fact getting away with this policy
> >
> > No. Assuming the nameservers are part of a gTLD (that is, it's in .com,
> > .net or .org), you do not have to (and cannot) register them as hosts at
> > NSI.
> >
> > We frequently have our clients change the nameservers of domains
> > registered at NSI to be the nameservers from our OpenSRS-registered
> > domain, and we've never had any trouble.
> >
> > What error message does your client get if he simply submits the
> > appropriate NSI forms? (Or has he not done so -- perhaps he's only asked
> > NSI on the phone, in which case he's quite likely to be told something
> > false like this?)
> >
> > --
> > Robert L Mathews, Tiger Technologies
> >
> >
>
