1 – clerk
Deletes the DECdns clerk on the specified node. You must disable a clerk before you delete it (see the disable command). You can also enter this command through the NCL interface. SYNOPSIS DELETE [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. PRIVILEGES REQUIRED You must have the NET$MANAGE rights identifier (VMS systems) or superuser privileges (ULTRIX systems).
1.1 – example
The following command deletes a clerk running on node .mfg.umbriel. dns> delete node .mfg.umbriel dns clerk
1.2 – known_namespace
Removes a namespace from a specified clerk's list of known namespaces. SYNOPSIS DELETE [NODE node-id] DNS CLERK KNOWN NAMESPACE identifier Arguments node-id The name of the node. If you do not specify a node name, the local node is assumed. identifier The identifier of the namespace. This is a required argument. You can use one of the following: name The name of the namespace. The name argument may be different from the nickname if the nickname is ambiguous. nscts The value of the namespace creation timestamp (NSCTS) assigned to the specified namespace when it was created. The format is 14 pairs of hex digits (xx- xx). NOTE You are not permitted to delete the known namespace that is currently the default namespace (that is, the one shown by show dns clerk default namespace). PRIVILEGES REQUIRED You must have the NET$MANAGE rights identifier (VMS systems) or superuser privileges (ULTRIX systems).
1.2.1 – example
The following command removes the namespace with the name jns from the clerk's list of known namespaces. dns> delete dns clerk known namespace jns
1.3 – manual_nameserver
Removes the knowledge of a server that exists across a WAN from the local clerk's cache. You can also enter this command through the NCL interface. SYNOPSIS DELETE [NODE node-id] DNS CLERK MANUAL NAMESERVER name 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 The simple name of the manual nameserver entity you want to delete. PRIVILEGES REQUIRED You must have the NET$MANAGE rights identifier (VMS systems) or superuser privileges (ULTRIX systems).
1.3.1 – example
The following command removes knowledge of server nrl from the clerk cache on node .mfg.umbriel. dns> delete node .mfg.umbriel dns clerk manual nameserver nrl
2 – server
Deletes the DECdns server on the specified node and reclains all server resources except clearinghouses, which remain. You must disable a server before you can delete it. You can also enter this command through the NCL interface. SYNOPSIS DELETE [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. PRIVILEGES REQUIRED You must have the NET$MANAGE rights identifier (VMS systems) or superuser privileges (ULTRIX systems).
2.1 – example
The following command deletes the DECdns server from node .mfg.polaris. dns> delete node .mfg.polaris dns server
2.2 – clearinghouse
Deletes a clearinghouse on the specified node. You must disable a clearinghouse before you can delete it. You can also enter this command through the NCL interface. This command also automatically deletes all read-only replicas from the clearinghouse when executed. DECdns does not permit you to delete a clearinghouse that contains a master replica. SYNOPSIS DELETE [NODE node-id] DNS SERVER CLEARINGHOUSE clearinghouse-name 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. ACCESS RIGHTS You must have delete access to the directories in the clearinghouse as well as to the clearinghouse. PRIVILEGES REQUIRED You must have the NET$MANAGE rights identifier (VMS systems) or superuser privileges (ULTRIX systems).
2.2.1 – example
The following command deletes a clearinghouse named .sales.ny_ch from the node .sales.orion. dns> delete node .sales.orion dns server clearinghouse .sales.ny_ch