[Top] [Prev] [Next] [Contents] [Index]

Using a Name Service

A name service translates between IP addresses and hostnames. Name service is optional, but you must use it if you want to specify hosts by their hostnames instead of their IP addresses. It is simpler and more meaningful to specify hostnames in remote configuration files, Setup menus, and commands. If you try to specify a hostname without using a name service, the terminal cannot find the host.

NCD terminals can use both DNS (Domain Name System) and IEN 116 name services.

Making Sure a Name Service is Running on the Local Network

To make sure DNS is available on the name server host:

To make sure IEN 116 name service is available on the name server host:

Making Sure the Terminal Uses the Name Service

You should always place name service parameters at the beginning of a remote configuration file, before any parameters that use hostnames. In addition, insert an apply command after the name service parameters to make sure the name service is in effect for subsequent parameters that use hostnames.

Selecting the Name Service Protocol

Set the tcpip-name-server-protocol parameter to the name service protocol you are using (Setup -> Change Setup Parameters -> TCP/IP Name Service -> Name Server Protocol).This parameter is saved in NVRAM and takes effect immediately if set interactively.

Table 5-5 tcpip-name-server-protocol Parameter
Possible Values
Result
default ien-116 (If the terminal's NVRAM is set to the factory defaults and the BOOTP/DHCP reply contains DNS name servers, the default value is "dns.")
ien-116 The terminal uses the IEN 116 name service method.
dns The terminal uses DNS.
both The terminal uses both IEN 116 and DNS.

Specifying Name Server Hosts

You can specify as many name server hosts as you need. If you do not specify a name server, the terminal uses the boot host for name service.

Enter the IP addresses of hosts offering name service into the tcpip-name-servers table (Setup -> Change Setup Parameters -> TCP/IP Name Service -> Name Servers). If you enter an address of 0.0.0.0, the boot host is used for name service.

If you use BOOTP/DHCP and specify name servers for this terminal in the bootptab file, those name servers are placed in the table automatically. This parameter is saved in NVRAM.

Table 5-6 tcpip-name-servers Parameter
Table Entry
Possible Values
Result
server default 0.0.0.0
IP address The name server with this IP address is used to map host IP addresses to symbolic names.

For example:


tcpip-name-servers = {
          { 192.43.150.001 }
          { 192.43.150.005 }
          }

Specifying the Default Domain Suffix for DNS

If you are using DNS and set this parameter, you do not have to specify a fully qualified domain name when specifying hostnames. Set the tcpip-dns-default-domain parameter to the default domain suffix to be appended to hostnames in searches (Setup -> Change Setup Parameters -> TCP/IP Name Service -> DNS Default Domain). The suffix is not appended to fully qualified names (names that contain all the components of the domain name).

The default domain suffix is the same as the domain name obtained from the Internet authority. For example, the parameter setting specifying NCD's default domain suffix is:


tcpip-dns-default-domain = ncd.com

Table 5-7 tcpip-dns-default-domain Parameter
Possible Values
Result
default nil
nil No suffix is applied to hostnames in name service searches.
domain suffix The suffix applied to hostnames in name service searches.

Configuring the Name Translation Table (Local Name Cache)

Translations are automatically placed in the local name cache. If your site does not run a name service, you can place translations into the table manually.

The terminal maintains the local name cache in the tcpip-name-local-cache parameter (Setup -> Change Setup Parameters -> TCP/IP Name Service -> Local Name Cache). Table 5-8 lists the entries in each row of the table.

Table 5-8 tcpip-name-local-cache Table Entries
Table Entry
Possible Values
Result
name default nil
hostname Hostname discovered through the name service or added manually.
address default 0.0.0.0
IP address IP address corresponding to the hostname.
lifetime default 0
integer The time (in seconds) (relative to the time the terminal was booted) at which the entry becomes invalid.

By default, case is considered when the terminal searches for a name in the local name cache. To ignore case, set the tcpip-name-cache-ignore-case parameter to "true." (Change Setup Parameters -> TCP/IP Name Service -> Ignore Case on Name Cache Lookups).

To customize the local name cache, you can change the following parameters; however, the defaults work well for most sites.

Setting the Name Cache Entry Lifetime

The tcpip-name-cache-max-lifetime parameter controls the maximum amount of time that an entry in the cache is used before it is deleted automatically (Setup -> Change Setup Parameters -> TCP/IP Name Service -> Name Cache Max Lifetime).

Table 5-9 tcpip-name-cache-max-lifetime Parameter
Possible Values
Result
default 1800
integer The maximum lifetime (in seconds) of the name cache. Range: 0 - 4294967295.

Setting the Name Cache Size

The tcpip-name-cache-max-size parameter sets the maximum number of entries allowed in the name cache (Setup -> Change Setup Parameters -> TCP/IP Name Service -> Name Cache Max Size). When the maximum size is reached, the oldest entry is discarded when a new entry is added. You may want to restrict the size of the cache to save memory for other uses.

Table 5-10 tcpip-name-cache-max-size Parameter
Possible Values
Result
default 32
integer The maximum number of entries in the name cache. Range: 0 - 4294967295 or until all free memory is consumed.

Setting Name Service Timeouts

The tcpip-name-server-retransmission-timeout parameter determines how long the terminal waits before sending a retransmission if the name server does not respond (Setup -> Change Setup Parameters -> TCP/IP Name Service -> Name Server Retransmission Timeout).

Table 5-11 tcpip-name-server-retransmission-timeout
Possible Values
Result
default 2
integer How long to wait (in seconds) before retransmitting a name service request. Range: 1 - 4294967295.

The tcpip-name-server-transaction-timeout parameter determines how long the terminal waits for a response from the name server before failure is declared (Setup -> Change Setup Parameters -> TCP/IP Name Service -> Name Server Transaction Timeout). The value of this parameter should be larger than the retransmission timeout.

Table 5-12 tcpip-name-server-transaction-timeout
Possible Values
Result
default 10
integer How long (in seconds) to attempt a name service request before declaring a failure condition. Range: 1 - 4294967295.

Discovering the Terminal's Hostname when Booting (Reverse Name Request)

The unit-query-for-name-at-boot parameter controls whether, at boot time, the terminal sends a reverse name request to the DNS name servers to find the terminal's host name (Setup -> Change Setup Parameters -> Unit -> Query for Unit Name at Boot).

Table 5-13 unit-query-for-name-at-boot Parameter
Possible Values
Result
default none
none The terminal does not attempt a reverse name query at boot.
tcpip The terminal tries a reverse query to the TCP/IP name servers. If no name servers are defined, the terminal tries the TCP/IP boot server, if the boot server is defined. The name service protocol must be DNS.
ncdnet The terminal tries a reverse query to the MOP boot server, if the boot server is defined.



[Top] [Prev] [Next] [Contents] [Index]

Send comments, suggestions, or questions about this document to the NCD Technical Publications Department by Internet e-mail. Write to us at techpubs@ncd.com.
Copyright © 1997, NCD Inc. All rights reserved.