\begin{ucsTabbox}{'[DHCP statements]' tab}
\ucsTabentry{Authoritative}
This selection controls the sending of \emph{DHCPNAK} messages to
incorrectly configured clients.

\ucsExclamation\ucsAttention{The \ucsMenuEntry{Yes} setting should
  only be selected if the consequences of this setting can be
  estimated and the DHCP service has been correctly configured!}

  The \ucsMenuEntry{Yes} setting prompts the DHCP service to send a
  \emph{DHCPNAK} message to each incorrectly configured client. If
  this is not done, clients are not in a position after changing
  subnets (e.g., notebooks) to receive a correct IP address until
  their old lease has expired. This can take some time.

  If nothing or \ucsMenuEntry{no} is selected, the DHCP service does
  not send any \emph{DHCPNAK} messages. This is the standard procedure
  for the DHCP service and should avoid any problems with an
  insufficiently or incorrectly configured DHCP service.

  Setting the setting is only practical for physical network
  segments. The setting should be made for a \emph{DHCP shared
  network} or a \emph{DHCP subnet}. The setting should be avoided
  for a \emph{DHCP shared subnet} and \emph{DHCP pool-} and
  \emph{DHCP host} objects!

\ucsTabentry{Boot unknown clients}
If \ucsMenuEntry{True} is selected from the list, the DHCP service
also issues IP addresses to clients which do not have a DHCP computer
entry. The prerequisite for this is that an appropriate pool of IP
addresses is set up. Limits to the issuing of IP address made on the
\ucsName{DHCP pool} object are taken into account here. If the entry
\ucsMenuEntry{False} is selected, the DHCP service does not issue IP
addresses to client which do not have a DHCP computer entry.

This setting is overwritten at DHCP pool level by the settings on the
\ucsMenuEntry{Advanced} tab.

\ucsTabentry{Ping check}
If nothing or \ucsMenuEntry{True} is selected, the DHCP server uses a
ping to check whether an IP address is free before issuing it
dynamically. This delays the reply to the client by a second. If this
represents a problem for the client submitting the request, the
setting \ucsMenuEntry{No} should be selected here. The availability
check via the ping is then not performed and the DHCP server replies
immediately.

\ucsTabentry{Add hostnames to leases}
If \ucsMenuEntry{True} is selected from the lst, the DHCP server
resolves all IP addresses for which this input applies into the
respective computer name in the DNS domain and uses it for the
\emph{hostname} DHCP option. If nothing or \ucsMenuEntry{False} is
selected, the DHCP server does not use the DNS domain names.

\ucsTabentry{Server identifier}
The IP address of the server the clients should use to communicate
with the DHCP server. This field should only be filled out in
justified exceptional cases. It must be ensured that the correct DHCP
server is used if several servers are set in a DHCP service.

\ucsTabentry{Server name}
This name is provided to a client as the name of the server from which
it boots.
\end{ucsTabbox}
