Distributed Name Service (DNS) Management Operations Manual

How to Define DNS Names
Building and Modifying the DNS Database
4–28 31258 Tandem Computers Incorporated
Be no more than 32 characters long
Be unique in the DNS database on which they are defined
Defining Composite-Object
Names
While simple objects are managed by one subsystem only, a composite object
(COMPOSITE) is managed by multiple subsystems. The entities controlling the
composite objects are called components. Before you can define a composite object,
you must define a composite type, as described in “Defining Composite Type Names.”
Figure 4-14 displays the relationships and dependencies of composite-object name
definitions.
Figure 4-14. Dependencies and Relationships of COMPOSITE Names
Legend
GROUP
COMPOSITETYPESSOBJECT
COMPOSITE
In an order-restricted relationship, a solid arrow line is used, and the
dependent name appears below the required name. Relationships shown
with dashed arrow lines are not order-restricted. The name from which
an arrow originates is specified in the definition of the name at the arrowhead.
DNSDOMAIN
S8121-024
When you add a composite-object definition, you must specify the name of the
composite and its components:
The composite type, which is a characterizing tag.
The names of the composite object’s component objects.