Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Administration: IP Services Oracle Solaris 11 Information Library |
1. Planning the Network Deployment
2. Considerations When Using IPv6 Addresses
3. Configuring an IPv4 Network
4. Enabling IPv6 on the Network
5. Administering a TCP/IP Network
7. Troubleshooting Network Problems
11. Administering the ISC DHCP Service
12. Configuring and Administering the DHCP Client
Differences Between DHCPv4 and DHCPv6
How DHCP Client Protocols Manage Network Configuration Information
How the DHCPv4 Client Manages Network Configuration Information
How the DHCPv6 Client Manages Network Configuration Information
Enabling and Disabling a DHCP Client
ipadm Command Options Used With the DHCP Client
Setting DHCP Client Configuration Parameters
DHCP Client Systems With Multiple Network Interfaces
DHCP Client Systems and Name Services
13. DHCP Commands and Files (Reference)
14. IP Security Architecture (Overview)
16. IP Security Architecture (Reference)
17. Internet Key Exchange (Overview)
19. Internet Key Exchange (Reference)
20. IP Filter in Oracle Solaris (Overview)
Part IV Networking Performance
22. Integrated Load Balancer Overview
23. Configuration of Integrated Load Balancer (Tasks)
24. Virtual Router Redundancy Protocol (Overview)
25. VRRP Configuration (Tasks)
26. Implementing Congestion Control
Part V IP Quality of Service (IPQoS)
27. Introducing IPQoS (Overview)
28. Planning for an IPQoS-Enabled Network (Tasks)
29. Creating the IPQoS Configuration File (Tasks)
30. Starting and Maintaining IPQoS (Tasks)
31. Using Flow Accounting and Statistics Gathering (Tasks)
By default, the DHCPv4 client does not supply its own host name, because the client expects the DHCP server to supply the host name. The DHCPv4 server is configured to supply host names to DHCPv4 clients by default. When you use the DHCPv4 client and server together, these defaults work well. However, when you use the DHCPv4 client with some third-party DHCP servers, the client might not receive a host name from the server. If the DHCP client does not receive a host name through DHCP, the client system checks the value that is set in the config/nodename property in the svc:/system/identity:node service for a name to use as the host name. If the file is empty, the host name is set to unknown.
If the DHCP server supplies a name in the DHCP Hostname option, the client uses that host name, even if a different value is placed in the value that is set in the config/nodename property in the svc:/system/identity:node service. If you want the client to use a specific host name, you can enable the client to request that name. See the following procedure.
Note - The following procedure does not work with all DHCP servers. Through this procedure you are requiring the client to send a specific host name to the DHCP server, and to expect the same name in return.
However, the DHCP server does not have to respect this request and many do not. They simply return a different name.
The steps to perform depend on whether an IP interface already exists with a DHCP address.
# ipadm delete-addr -r dhcp-addrobj
# ipadm create-addr -T dhcp -h hostname dhcp-addrobj
# ipadm create-ip interface
# ipadm create-addr -T dhcp -h hostname dhcp-addrobj