Technical data

Configuring the DHCP Server
7.2 DHCP Server Components
Example 7–1 (Cont.) Sample SERVER.PCY File
name_service dns
# Specify whether the name service is dynamically updateable.
# NIS and NIS+ are dynamically updateable, but the system
# administrator may choose to disable this capability. In
# both cases the server must be in the same domain as the
# name server, and the JOIN server’s key must be in the
# public database. NIS also requires the creation of
# a pseudo map, "join", and the installation of the file
# "updaters" in /var/yp on the name server. See manual
# for further details. This option can be enabled for DNS.
# The default is not to permit dynamic updating.
name_service_updateable
# Name policy
# The name may be choosen according to three possible policies:
# assign_name_by_hwaddr:
# A particular client (identified # by its hardware address)
# always has the same name wherever possible. This option
# may only be choosen if the name service is updateable.
# assign_name_by_ipaddr:
# The client gets a name from the IP address which was
# assigned to it, as found in the name service. This
# option is incompatible with assign_name_by_hwaddr.
# accept_client_name:
# This toggle is valid only when the policy is
# assign_name_by_hwaddr. When "on" the server will use
# the name suggested by the client and bind it to the
# IP address delivered by the DHCP protocol. This is
# true even if the client in question already has a name
# in the server’s DB which is not the name suggested.
# The old name continues to be "owned" by the client
# and may have a valid IP address bound to it.
# When this toggle is "off" the server will return to
# client a pre-existing name bound to the client identifier
# or hardware address, regardless of the name the client
# suggests to the server.
#
# If no name can be found by the application of one or more of
# these policies, the server will generate a name for the domain
# by using the name prefix in the "namepool" database.
# assign_name_by_ipaddr
#
# Note: The following two settings are most appropriate when you are using
# dynamic DNS updates. To set this up on the DHCP server side uncomment these
# lines and delete the line above with "assign_name_by_ipaddr".
assign_name_by_hwaddr
accept_client_name
# When the naming policy is assign_name_by_hwaddr the server will
# not allow a client to use a name which is "owned" by some other
# client. I.e. A name that is already bound to a different Client
# identifier or MAC address. When this toggle is on, this prohibition
# is lifted and the name will be re-assigned
#ignore_name_owner
# Bootp.
# Remove this line if the server is not to support old-style Bootp
(continued on next page)
Configuring the DHCP Server 7–7