Specifications

8-13
TCP/IP Network Characteristics
You can use a relative domain name if you are defining a local name server for the
default domain only.
Configuring a Name Server for a Different Domain
To enter a locally defined name server for a domain other than the access server
default domain, follow these steps:
Name Resolution and Gateways
The access server uses the learned name servers to perform name resolution when
using REMOTE or ORDERED name resolution modes. The list of learned name
servers for a given domain are, in general, a superset of those explicitly entered
with the CHANGE INTERNET NAMESERVER command. The access server
primes the cache for the server’s default domain by sending queries to the
configured name servers. The queries request the names of all authoritative name
servers for the default domain.
The access server may not be able to reach a learned name server because of
subnet access restrictions on the access server itself. In this case, the access server
flags the unreachable name server and stops using it for name resolution. The
access server cannot reach a name server if it is not in the same subnet or there is
no gateway to it.
If the access server cannot reach a learned name server because of gateway
restrictions outside the server, it does not flag the unreachable name server. This
can often cause name resolution to time out and fail. In this configuration use
either the STUB or SLAVE name resolution mode.
Step Action
1 Use the SET INTERNET NAME RESOLUTION DOMAIN command
to change the access server default domain name temporarily.
Note:
Temporarily changing the default name affects the ability of other
users in resolving relative domain names.
2 Use the SET/DEFINE/CHANGE INTERNET NAMESERVER
domain-name ADDRESS n.n.n.n LOCAL command to add the name
server.
3 Change the access server default domain name back to the original
domain name.