Name Resolution
B-7
B
nameserver 199.97.127.10
nameserver 199.97.127.20
Some domain name servers support a
search
directive to override the
default order in which domains are searched. Referring to Figure B-2, to
query
acme.com
before the default domain
corp.acme.com
, the
resolv.conf
file would contain the following
search
directive:
search acme.com corp.acme.com
To minimize the impact of introducing DNS, your client systems should, if
possible, be configured to use the Sun Name Server to attempt name resolution
after the usual name resolution schemes have failed.
In small sites, LAN-wide names are resolved by system files, which are copied
among all the machines on the LAN. These files include
/etc/hosts
,
/etc/services
, and
/etc/passwd
, which contain the mappings of host names
to IP addresses, the mappings of service names to TCP and UDP port numbers,
and user information, respectively. All systems use the
/etc/hosts
file if DNS
fails to resolve a host name.
The most popular alternative to DNS is Sun’s Network Information System
(NIS), which is distributed by most Unix vendors. NIS maintains the system
files in synchronization across the networked systems. The files are
administered on one master system and distributed among the slaves by NIS.
An NIS resolver (implemented as part of the
ypserv
program) performs name
mapping.
Depending on your operating system, you can configure systems to resolve
host names using the local
/etc/hosts
file, NIS, and/or DNS in one of the
following ways:
•
Solaris
- Uses a control file,
/etc/nsswitch.conf
, to specify the order in
which the
/etc/hosts
file, NIS, and DNS are queried to resolve names.
Hosts running the Sun Name Server must specify
files
before
dns
in the
/etc/nsswitch.conf
file. For efficiency, Sun recommends that Solaris client
systems also specify
files
before
dns
in the
/etc/nsswitch.conf
file.
B.4 Using the Sun Name Server with APPC
SUNWappc TPRM programs issue the
lu62_open()
call to connect to a server
and local LU. Assuming that the Sun Name Server domain is
sna
and the local
LU is
LUSP1
, the call is issued as follows:
Содержание SunLink SNA 9.1 PU2.1
Страница 14: ...xiv SunLink SNA 9 1 PU2 1 Server Configuration Guide August 1997...
Страница 16: ...xvi SunLink SNA 9 1 PU2 1 Server Configuration Guide August 1997...
Страница 18: ...xviii SunLink SNA 9 1 PU2 1 Server Configuration Guide August 1997...
Страница 26: ...xxvi SunLink SNA 9 1 PU2 1 Server Configuration Guide August 1997...
Страница 48: ...1 22 SunLink SNA 9 1 PU2 1 Server Configuration Guide August 1997 1...
Страница 66: ...2 18 SunLink SNA 9 1 PU2 1 Server Configuration Guide August 1997 2...
Страница 80: ...3 14 SunLink SNA 9 1 PU2 1 Server Configuration Guide August 1997 3...
Страница 110: ...6 12 SunLink SNA 9 1 PU2 1 Server Configuration Guide August 1997 6...
Страница 120: ...7 10 SunLink SNA 9 1 PU2 1 Server Configuration Guide August 1997 7...
Страница 132: ...8 12 SunLink SNA 9 1 PU2 1 Server Configuration Guide August 1997 8...
Страница 226: ...A 10 SunLink SNA 9 1 PU2 1 Server Configuration Guide August 1997 A...
Страница 282: ...F 16 SunLink SNA 9 1 PU2 1 Server Configuration Guide August 1997 F...
Страница 288: ...G 6 SunLink SNA 9 1 PU2 1 Server Configuration Guide August 1997 G...