database
Click on the red underlined text to get to the source
... hierarchy roughly corresponding to organizational structure, and names
using "." as the character to mark the boundary between hierarchy
levels. A design using a distributed database and generalized resources
was described in [RFC-882, RFC-883 ...
... The sheer size of the database and frequency of updates
suggest that it must be maintained in a distributed manner,
with local caching to improve performance ...
... with local caching to improve performance. Approaches that
attempt to collect a consistent copy of the entire database
will become more and more expensive and difficult, and hence
should be avoided. The same principle holds for the structure
...
... transactions that need the
reliability (e.g., database updates, long transactions); other
systems will use virtual circuits ...
... system derives from some assumptions
about the needs and usage patterns of its user community and is designed
to avoid many of the the complicated problems found in general purpose
database systems.
...
... The size of the total database will initially be proportional
to the number of hosts using the system, but will eventually
...
... The administrative boundaries used to distribute
responsibility for the database will usually correspond to
organizations that have one or more hosts. Each organization
...
... In any system that has a distributed database, a particular
name server may be presented with a query ...
... functions. For example, a resolver on the same machine as a name server
might share a database consisting of the the zones managed by the name
server and the cache managed by the resolver.
...
... address or any other resource type. Inverse queries
are primarily useful for debugging and database maintenance activities.
...
...
Name servers are the repositories of information that make up the domain
database. The database is divided up into sections called zones, which
are distributed among the name servers. While name servers can have
...
... Name servers are the repositories of information that make up the domain
database. The database is divided up into sections called zones, which
are distributed among the name servers. While name servers can have
several optional functions and sources of data, the essential task of a
...
... How the database is divided into zones ...
...
The domain database is partitioned in two ways: by class, and by "cuts"
made in the name space ...
... The class partition is simple. The database for any class is organized,
delegated, and maintained separately from all other classes ...
... domain name was in a separate zone or so that
all nodes were in a single zone. Instead, the database is partitioned
at points where a particular organization wants to take over control of
a subtree ...
... delegations of name space control.
In some cases, such divisions are made purely to make database
maintenance more convenient.
...
... service unless asked via RD, since this interferes with trouble shooting
of name servers and their databases.
...
... configuration file, since it
probably lacks the sophistication to locate it in the domain database.
The user also needs to verify that the listed servers will perform the
recursive service ...