1 – clerk
Creates a clerk on the specified node. You can also enter this
command through the NCL interface. This command should not
normally be executed outside of the DECnet startup procedure.
SYNOPSIS
CREATE [NODE node-id] DNS CLERK
Argument
node-id
The name of the node. If you do not specify a node name, the local
node is assumed.
NOTE
To create a clerk on a VMS system, enter the
@SYS$STARTUP:DNS$CLERK_STARTUP command from the VMS system
prompt. You must have the NET$MANAGE rights identifier to
execute this command. You can only use the command locally;
you must be logged into the system where the clerk resides.
PRIVILEGES REQUIRED
You must have the NET$MANAGE rights identifier (VMS systems) or
superuser privileges (ULTRIX systems).
1.1 – example
The following command creates a clerk on node .mfg.umbriel. dns> create node .mfg.umbriel dns clerk
1.2 – known_namespace
Adds a namespace to the list of namespaces cached by a specified
DECdns clerk.
SYNOPSIS
CREATE [NODE node-id] DNS CLERK
KNOWN NAMESPACE name NSCTS nscts
Arguments
node-id
The name of the node. If you do not specify a node name, the local
node is assumed.
name
A simple name for the namespace.
nscts
The value of the namespace creation timestamp (NSCTS) that is
automatically assigned when the namespace is created. The format
of the NSCTS is 14 pairs of hex digits (xx-xx).
PRIVILEGES REQUIRED
You must have the NET$MANAGE rights identifier (VMS systems) or
superuser privileges (ULTRIX systems).
1.2.1 – example
The following command adds the namespace with the name jns and NSCTS value of 08-00-2B-0D-C0-9D-CD-3B-C6-16-EC-3B-94-00 to the list of namespaces cached by the local clerk. dns> create dns clerk known namespace jns NSCTS - _> 08-00-2B-0D-C0-9D-CD-3B-C6-16-EC-3B-94-00
1.3 – manual_nameserver
Creates knowledge in the local clerk's cache about a server that
exists across a wide area network (WAN).
SYNOPSIS
CREATE [NODE node-id] DNS CLERK
MANUAL NAMESERVER name TOWER TowerSet
Arguments
node-id
The name of the node on which the clerk exists. If you do not
specify a node name, the local node is assumed.
name
A simple name for the manual nameserver. The name is used only as a
handle for managing this entity.
TowerSet
The DNA TowerSet address of the server node. (You must use a
continuation character (-) for commands that extend beyond one line
of text, but this only works if it is the very last character on the
line of text.) The format of a TowerSet is:
{([DNA_OSInetwork , nsap-value ])}
Description
This command creates knowledge in the local clerk's cache about a
server that exists across a WAN. It gives the clerk the information
it needs to contact the server across a WAN and cache the other
information that the clerk needs to communicate with that server.
You can also enter this command through the NCL interface.
NOTE
You should not normally enter this command from DNSCP. You can
use the configuration program to accomplish what this command
does.
PRIVILEGES REQUIRED
You must have the NET$MANAGE rights identifier (VMS systems) or
superuser privileges (ULTRIX systems).
1.3.1 – example
The following command informs the clerk on node .mfg.umbriel about
the existence of the server nrl.
dns> create node .mfg.umbriel dns clerk manual nameserver nrl tower -
_> {([ DNA_OSInetwork , 49::00-04:AA-00-04-00-6A-11:20 ])}
2 – server
Creates a server on the specified node. The server software
must be installed on the target node. You can also enter this
command through the NCL interface. This command should not
normally be executed outside of the DECnet startup procedure.
SYNOPSIS
CREATE [NODE node-id] DNS SERVER
Argument
node-id
The name of the node. If you do not specify a node name, the local
node is assumed.
NOTE
To create a server on a VMS system, enter the
@SYS$SSTARTUP:DNS$SERVER_STARTUP command from the VMS system
prompt. You must have the NET$MANAGE rights identifier to
execute this command. You can only use the command locally;
you must be logged into the system where the server resides.
PRIVILEGES REQUIRED
You must have the NET$MANAGE rights identifier (VMS systems) or
superuser privileges (ULTRIX systems).
2.1 – example
The following command creates a DECdns server on the local node. dns> create dns server
2.2 – clearinghouse
Creates a clearinghouse on the specified node. You can specify
the directory version, the initial replica to be stored in the
clearinghouse, and the filename. This command is useful after moving
a clearinghouse or if you have moved the clearinghouse file. You can
also enter this command through the NCL interface.
SYNOPSIS
CREATE [NODE node-id]
DNS SERVER CLEARINGHOUSE clearinghouse-name
[NEW DIRECTORY VERSION version-number,]
[INITIAL REPLICA replica-name,] [FILE filespec]
Arguments
node-id
The name of the node. If you do not specify a node name, the local
node is assumed.
clearinghouse-name
The full name of the clearinghouse.
version-number
The DECdns version number the new directories will have at this
clearinghouse. Specify the value as Vx.y.z, where x defines the
major release number, y specifies the minor version number, and z
specifies an ECO level. This argument is optional. Set the value to
V1.0.0 if you intend to create DNS Version 1 directories. Set it to
V2.0.0 to create only DECdns Version 2 directories. If you omit this
argument, the default is V2.0.0.
replica-name
The full name of the first directory replica to store in the
clearinghouse. This argument is optional. If you omit this argument,
the parent directory of this clearinghouse becomes the initial
replica.
filespec
A file specification that will contain the clearinghouse. This
argument, which is optional, is useful if you have moved an existing
clearinghouse and do not want new default names to be generated
automatically. On ULTRIX systems, the default is /var/dss/dns. On
VMS systems, the default is the default directory for the DNS$SERVER
account.
NOTE
This command is normally executed only by the DECdns
configuration program during the configuration of a
DECdns server in an existing namespace. You should
use this command only to re-create a clearinghouse
whose database files are relocated on another server
system.
ACCESS RIGHTS
The account executing the command needs write access to the
directory in which you want to name the clearinghouse. This
access must be propagated to all members of the directory's
replica set before you enter this command. Otherwise, the
command fails.
PRIVILEGES REQUIRED
You must have the NET$MANAGE rights identifier (VMS systems) or
superuser privileges (ULTRIX systems).
2.2.1 – example
The following command creates a clearinghouse named .sales.ny_ch on node .sales.orion. dns> create node .sales.orion dns server clearinghouse .sales.ny_ch