DHCP Client Systems and Name Services
Oracle Solaris systems support the following name services: DNS, NIS, and a local
file store (/etc/inet/hosts). Each name service requires some configuration before it is usable.
The name service switch configuration file (see nsswitch.conf(4)) must also be set up
appropriately to indicate the name services to be used.
Before a DHCP client system can use a name service, you must
configure the system as a client of the name service. By default, and
unless configured otherwise during system installation, only local files are used.
The following table summarizes issues that are related to each name service and
DHCP. The table includes links to documentation that can help you set up
clients for each name service.
Table 15-1 Name Service Client Setup Information for DHCP Client Systems
If you are using
DHCP to send Oracle Solaris network install information to a client system, you
can use a configuration macro that contains the NISservs
These options pass the IP addresses of NIS servers and the NIS domain
name to the client. The client then automatically becomes an NIS client.
DHCP client system is already running Oracle Solaris, the NIS client is not
automatically configured on that system when the DHCP server sends NIS information to
If the DHCP server is configured to send NIS information to
the DHCP client system, you can see the values given to the client
if you use the dhcpinfo command on the client as follows:
# /sbin/dhcpinfo NISdmain
Note - For DHCPv6, include -v6, and different protocol keywords in the command.
# /sbin/dhcpinfo -v6 NISDomain
# /sbin/dhcpinfo -v6 NISServers
the values returned for the NIS domain name and NIS servers when you
set up the system as an NIS client.
You set up an NIS
client for an DHCP client system in the standard way, as documented in
Chapter 5, Setting Up and Configuring NIS Service, in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).
Tip - You can write a script that uses dhcpinfo and ypinit to
automate NIS client configuration on DHCP client systems.
You must set up the
file for a DHCP client system that is to use /etc/inet/hosts
The DHCP client system's host name is added to its own
/etc/inet/hosts file by the DHCP tools. However, you must manually add the
host name to the /etc/inet/hosts files of other systems in the network. If the
DHCP server system uses /etc/inet/hosts for name resolution, you must also manually add
the client's host name on the system.
If the DHCP client system receives the
DNS domain name through DHCP, the client system's /etc/resolv.conf
file is configured automatically. The
file is also automatically updated to append dns
to the hosts
any other name services in the search order. See System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP)
information about DNS.