i understand you don't mean legally as in i go to jail.
my question is why do the registrars require a 1 to 1 mapping (if they
even do -- if not, why does opensrs)?
the root servers provide A records for registered nameservers, but not PTR
records. having 2 A records to the same ip works fine.
an example is cr.yp.to's nameservers:
additional: a.ns.yp.to 235171 A 131.193.178.181
additional: b.ns.yp.to 235171 A 131.193.178.181
i can see no technical reasons of why this should be avoided, nor
anything in rfcs that gives this method special consideration against the
norm (and it's "legal" in the norm).
-tcl.
On Fri, 25 May 2001, Jackie Fong wrote:
> i didn't exactly mean legal literally. what i meant was when you register
> a nameserver, it is a 1-1 relationship, 1 name server per IP. that is why
> you got an error when you try to register the second one. the error
> should have said "duplicate name servers" or something similar.
>
> > 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.
> > > >
> > > >
> > >
> > >
> >
>
>
