Editing DHCP server configuration - User Guide - Micetro

You can edit the configuration of your DHCP servers in Micetro.

Note: It's not possible to edit server configurations for all types of DHCP servers in Micetro. For example, you cannot edit a Cisco Meraki DHCP server's configuration.

To edit DHCP server configuration:

On the Service management tab of the Admin page, locate the DHCP server in the data grid.
Use either the Action or Row ... menu to select Edit configuration.
In the dialog, edit the server configuration as needed. Some server types include additional properties you can configure. Refer to the following tabs for those server-specific instructions:

On the Properties tab, edit the properties as needed:

Authoritative: Check this box to give the server authority to validate DHCP requests from clients.
DDNS domain name: Specify the DNS domain name used to store the A record for DHCP clients.
DDNS reverse domain name: Specify the DNS reverse domain name for storing the PTR record of DHCP clients.
DDNS update style: Select the method used by the DHCP server to perform DNS updates. Options include:
- None: No dynamic DNS updates are performed.
- Ad-hoc (deprecated): This update scheme is outdated.
- Interim: Recommended method for dynamic DNS updates.
DDNS updates: Check the box to enable DNS updates. This setting is only effective if DNS updates are globally enabled with the DDNS update style setting.
DDNS TTL: Set the Time-To-Live (TTL) value, in seconds, for DNS updates.
Default lease time: Specify the default lease duration, in seconds, for DHCP leases.
Log facility: Select the syslog facility for logging DHCP server messages.
Note: Not all facilities may be available on all systems.
Max/min lease time: Set the maximum and minimum lease durations, in seconds, for DHCP leases.
Get lease hostnames: Check the box to require the DHCP server to perform a reverse DNS lookup for each address assigned to a client and send the result to the client as the hostname option.
One lease per client: Check the box to release existing leases held by a client when requesting a new lease.
Ping check: Check the box to require the DHCP server to send an ICMP echo message to probe an IP address before offering it to a DHCP client.
Ping timeout: Specify the number of seconds the DHCP server should wait for an ICMP echo response when Ping check is active.
Filename: Specify the name of the initial boot file to be used by a client.
Server name: Specify the name of the server from which the client should load its boot file.
Next server: Specify the host address of the server from which the initial boot file (specified by Filename) is to be loaded.

To configure the ISC DHCP server to update zones dynamically, i.e., on MDDS appliances or BIND servers:

Open the Raw configuration in the dialog.
In the editor, add the following statements:
```
key update-key
{
  algorithm hmac-sha512;
  secret "5B1...";
}

zone micetro.com
{
  primary 1.2.3.4;
  key update-key;
}
```
Make sure that:
- The key is not enclosed in double quotation marks.
- Each line contains only one declaration.

On either the Properties for v4 or Properties for v6 tabs, edit the properties for DHCPv4 or DHCPv6, respectively.

Default/Maximum/Minimum valid lifetime: Specify the time after which a lease will expire if not renewed.
Renew timer: Specify the time when a client will begin a renewal procedure.
Rebind timer: Specify the time when a client will begin a rebind procedure.
Next server: Specify the server address to use when clients want to obtain configuration from a TFTP server.
Echo client ID: Check this box if the server should send back client-id options when responding to clients.
Match client ID: Check this box if the server should ignore the client identifier during lease lookups and allocations for a particular subnet.
Decline probation period: Specify a probation time that will be set on addresses that are in use by some unknown entity.
Control socket name: Enter the path to the UNIX socket. Cannot be left empty.
Server tag: An arbitrary string used to associate configuration elements with specific Kea server instances in a configuration database, allowing for shared or unique configurations among multiple servers.

For more specialized configurations, you can define additional properties and edit configuration files directly on the server for both DHCPv4 and DHCPv6 on the Raw configuration tab.

Note: Exercise caution when editing configuration files on the Raw configuration tab, as there is minimal error handling.

In the Edit configuration dialog, edit the server properties as needed:

Conflict detection attempts: Specifiy the number of conflict detection attempts you want the DHCP server to make before it leases an address to a client.
Audit log file path: Specifiy the location of the DHCP server audit log files.
Database path: Specify the location of the DHCP server database.
Backup path: Specify the location for the database backup.

Editing DHCP server configuration - User Guide - Micetro - 25.2.0

Micetro Admin Guide