Distributed Name Service (DNS) Management Operations Manual

Introduction to Defining DNS Names
Building and Modifying the DNS Database
31258 Tandem Computers Incorporated 4–3
Figure 4-1. Group Hierarchy Example
OREGON_ATMS
PORTLAND_ATMS MEDFORD_ATMS SALEM_ATMS EUGENE_ATMS
NORTHWEST_ATMS
PORT_NORTHEAST_ATMS
PNE_ATM1
PNE_ATM2
PNE_ATM3
030
Introduction to
Defining DNS Names
When you define an object, type, alias, group, or other name to DNS, you define its
attributes, assign it a name, and add the definition to the DNS database. In fact, the
name whose definition you are adding is included in the command syntax. In the
following example, MIDWEST is the name of the DNS domain being added.
ADD DNSDOMAIN MIDWEST, SYSTEMS (\dallas, \chicago, \omaha)
The next few subsections include information about defining DNS names, such as
name dependencies, the parts of a name, and shortcuts for building name definitions.
Name Dependencies and
Relationships
To some extent, DNS names must be defined in a specific sequence. In most
installation sites, the most necessary and primary definitions are done for you at DNS
initialization. The subsystem name and subsystem-object type name definitions are
loaded as discussed under “Initializing and Starting DNS configurations” in Section 3.