Distributed Name Service (DNS) Management Operations Manual

Introduction to Defining DNS Names
Building and Modifying the DNS Database
4–4 31258 Tandem Computers Incorporated
Creating some name definitions is dependent on the preexistence of other definitions,
as listed in Table 4-1. Definitions of some names are building blocks for other
definitions. Because of the multitude of name relationships and dependencies, it is
important that you understand them before creating the DNS database.
Table 4-1. Dependencies for Defining Names
Name Name That Must Already Exist
SSTYPE SS name must exist (added by ZDNS.LOAD at installation)
SSMANAGER SS name must exist (added by ZDNS.LOAD at installation)
SSOBJECT SSTYPE name and SSMANAGER name must exist
COMPOSITETYPE SSTYPE names must exist
COMPOSITE SSOBJECT names and COMPOSITETYPE name must exist
ALIAS REFERENT must exist (SSOBJECT or SSMANAGER)
DNSDOMAIN and GROUP names may be defined at any time. Sometimes domains
and groups are created before their eventual contents. Members of groups and nodes
listed in domains can be created later. The order you choose is up to you.
As samples, below are two possible sequences of defining DNS names that you may
choose to follow.
CHOICE 1 CHOICE 2
SS SS
SSTYPE DNSDOMAIN
SSMANAGER SSTYPE
COMPOSITETYPE ALIASTYPE
ALIASTYPE COMPOSITETYPE
SSOBJECT SSMANAGER
ALIAS SSOBJECT
COMPOSITE ALIAS
GROUP COMPOSITE
DNSDOMAIN GROUP
Figure 4-2 displays how the DNS names relate to one another and the order you must
follow when creating DNS name definitions. For all figures in this section that display
name dependencies and relationships, the following two points apply:
If a name’s existence is required to create another name, the dependent name
appears below the required name.
In an order-restricted relationship, the name from which an arrow originates is
specified in the definition of the name at the arrowhead.