Re: Antwort: RE: draft-hollenbeck-grrp-reqs-06 [Was Re: InterimMeeting]

[Sheer El-Showk <sheer@saraf.com>]

There are several (in my opinion, good) reasons that nameservers are
considered seperate entities from the domains in which they are
registered.

The first is related to the way DNS works.  In the zone files of the TLDs
there are entries for each name server (I don't work for any TLD mind you
... I'm just saying this from what I know of DNS, and the details may be
inaccurate) which serve as glue records so that each TLD name server can
find authortiative access for subdomains (the SLDs that actually have real
entries for each domain).  These glue records are non-authoritative, but
necassary and make DNS pretty messy (annoying things can happen if a TLD
glue record is out of sync with the authoritative record of the real name
servers).  Thus it makes sense to have nameservers recorded at the same
level as the domains themselves so that there is a more natural mapping
from the registry to the zone files.

Second, is the requirements registries often put on a domain (at least the
way NSI was).  For a domain to be registered requires at least two valid
nameservers.  This means the nameservers have to be registered before the
domain itself is (as seperate entities).

A third, less technical, reason is minimizing data redundancy and
simplifying domain administration.  As a registrant I may want to register
10,000 domains all on the same physical DNS server.  Rather than
registering 10,000 (or 20,000 for each domain) name servers, I just 
register two for my two main name servers under one of the domains and
then register all the domains under these name servers.  Of course this
can be done if name servers are a domain attribute (you just set the
attributes all to be those two name servers); this is just an argument for
why the domain and the nameserver are not as closely coupled as being a
domain attribute would suggest (and its much more natural for a domain to
refer to another DB entity as an attribute, than to refer to an attribute
of another domain as one of its attributes -- this would be analogous to
refering to another record in a table through a key rather than refering
to a sub-record in another record -- sorry if my convoluted language has
gotten out of hand).

Regards,
Sheer 

On Tue, 6 Feb 2001, [iso-8859-2] Jörg Bauer/Denic wrote:

> On 05.02.2001 20:29 "Brian W. Spolarich" <briansp@walid.com> wrote:
> >
> >   As a registrant, the thing that I care about is that the nameservers
> that
> > I registered with my domain don't change unless I explicity authorize the
> > change.
> >
> >   I'm wondering if the problem here is the idea of having separate
> > nameserver and domain objects.  In my mind, the nameserver is an
> attribute
> > of the domain, and doesn't have any independent identity.  What problem
> does
> > having the nameservers as separate entities solve?
> >
> 
> Thatīs exact the way we do it here in Germany.
> We dontīt know anything about Nameserver Objects and i still canīt see it
> as a requirement.
> 
> --
> ----------------------------------+-------------------------------------------
> 
> Joerg Bauer                       | eMail : Joerg.Bauer@denic.de
> DENIC eG                          | Fon   : +49 69 272 35 180
> Wiesenhuettenplatz 26             | Fax   : +49 69 27235 235
> D-60329 Frankfurt                 |
> ----------------------------------+-------------------------------------------
>