additional: a.ns.yp.to 234740 A 131.193.178.181
additional: b.ns.yp.to 234740 A 131.193.178.181
is the .to registry simply more lenient (read: smarter) than the
com/net/org gtld registry?
if that's the case, how about this: is there any way to get new
registrations to only use 1 nameserver instead of requiring 2? the
opensrs client interface allows me to strip it down to 1 afterwards
anyway...
-tcl.
On Fri, 25 May 2001, Charles Daminato wrote:
> Two things,
>
> 1) Please do not cross post
>
> 2) The registry imposes a limit on how many nameserver hosts can be
> associated with a single IP, and that limit is one.
>
> Charles Daminato
> TUCOWS Product Manager
> [EMAIL PROTECTED]
>
> On Fri, 25 May 2001, tc lewis wrote:
>
> >
> > how is it not legal?
> >
> > while irrelevant, one of the reasons is so all the domains i have using
> > nameserver x and nameserver y are effectively both using nameserver x.
> > they already are -- i don't see the need to waste ip space and various
> > other resources.
> >
> > -tcl.
> >
> >
> > On Fri, 25 May 2001, Jackie Fong wrote:
> >
> > > tcl,
> > >
> > > I don't think it's 'legal' to have two nameservers with the same IP. Why
> > > do you want to do that anyway? I don't see any reasons to do this...
> > >
> > > > the manage client interface (action=manage_nameserversmeservers) doesn't
> > > > seem to allow me to create 2 nameservers with the same ip:
> > > >
> > > > Unable to create nameserver: Registry error, nameserver creation failed
> > > > [Attribute value not unique]
> > > >
> > > > is there any technical reason for this? is this just an extra step of
> > > > user error prevention? any way to get around it?
> > > >
> > > > -tcl.
> > > >
> > > >
> > >
> > >
> >
> >
>
>
