This section describes DHCP properties that apply to both IPv4 and IPv6. It includes the following sections:
When you configure the appliance as a DHCP server, the appliance supports UTF-8 encoding of hostnames that are encoded with Microsoft Windows code pages. You can configure the DHCP services on the appliance to convert these client hostnames to UTF-8 characters. The appliance stores the UTF-8 encoded hostnames in the database. If you also configure the DHCP services on the appliance to perform DDNS updates, the appliance sends the UTF-8 encoded host names in the DDNS updates. You can configure the UTF-8 encoding of host names at the Grid DHCP service and member DHCP service levels. For information on UTF-8 encoding, see .
The appliance displays the host names in their original characters in the following:
To configure UTF-8 encoding for hostnames:
You can associate IPv4 and IPv6 networks with DNS zones to limit the zones that admins can use when they create DNS records for IP addresses in the networks. When a network is associated with one or more zones and an admin creates a DNS record for one of its IP addresses, Grid Manager allows the admin to create the DNS record in the associated zones only. For example, if you associate the 10.1.0.0/16 network with the corpxyz.com zone, admins are allowed to create DNS records in the corpxyz.com zone only for IP addresses in the 10.1.0.0/16 network; or if you associate the 2001:db8:1::/48 network with the corp200.com zone, admins are allowed to create DNS records in the corp200.com zone only for IP addresses in the 2001:db8:1::/48 network.
This feature applies to A, AAAA and host records only. It does not apply to records in a shared record group. If you are creating a host record with multiple IP addresses in different networks, the networks must be associated with the zone of the host record.
If a network is not associated with a zone, admins can create DNS records for its IP addresses only in zones with no network associations as well.
You can associate a network with any authoritative zone whose primary server is a Grid member or a Microsoft server, or is unassigned. You cannot associate networks with zones that have external primary servers.
You can associate a network with multiple zones, and associate a zone with more than one network. You can associate IPv4 and IPv6 network containers and networks with zones. When you associate a network container with zones, its networks inherit the zone associations. You can override the zone associations at the network level.
If you split a network, the resulting subnets inherit the zone associations. If you join networks, the resulting network retains the zone associations of the network that you selected when you performed the join operation. You can override the inherited zone associations of individual networks. Subzones do not inherit the network associations of their parent zones.
When you import data into a zone that is associated with a list of networks, the imported A, AAAA and host records must have IP addresses in the associated networks. Grid Manager does not allow you to import A, AAAA and host records with IP addresses in unassociated networks.
When you associate a network with a zone, the DNS records created before the association are not affected. But if you edit an A, AAAA or host record after the association, Grid Manager does not allow you to save the record if its IP address is not in an associated network.
To associate an IPv4 or IPv6 network with a zone:
5. Save the configuration or click the Schedule icon at the top of the wizard to schedule this task. In the Schedule Change panel, enter a date, time, and time zone. For information, see Scheduling Tasks.
You can view the IPv4 or IPv6 networks associated with a zone from the zone editor. The tab to display network associations in zone editors is visible only if the primary server is a Grid member, a Microsoft server, or unassigned.
To view the network associations of a zone:
The Network Associations table lists the networks and their corresponding comments. You cannot change the network associations in this editor. Navigate to the DHCP Network editor of the network, to change the zone associations.
You can configure the DHCP server to store leases in a deleted DHCP range for up to one week after the leases expire. When you add a new DHCP range that includes the IP addresses of these leases or assign the DHCP range to another member within the Grid, the appliance automatically restores the active leases. You can configure this feature for the Grid, and override the configuration for members, networks, and DHCP ranges.
To keep active leases in a deleted DHCP range:
You can configure the DHCP server to capture the hostname and lease time of a fixed address when you assign an IPv4 or IPv6 fixed address to a client. The appliance displays the hostname, and the start and end time of each fixed address lease in the Current Leases panel in Grid Manager.
You can set this at the Grid level only for IPv4 and IPv6 leases.
The accumulation of free and backup DHCPv4 leases; and free, expired, and released DHCPv6 leases results in unnecessary growth of database objects. The DHCP lease scavenging feature enables member DHCP servers to automatically delete free and backup IPv4 leases; and free, expired, and released IPv6 leases that remain in the database beyond the specified period of time, thus reducing the number of database objects.
When you enable this feature for DHCPv4 leases, the appliance permanently deletes the free and backup IPv4 leases, and you can no longer view or retrieve the lease information. This option can be enabled globally at the Grid level, and more specifically for a member, shared network, network, network container, DHCP range, network template, DHCP range template.
When you enable this feature for DHCPv6 leases, the appliance permanently deletes the free, expired, and released IPv6 leases, and you can no longer view or retrieve the lease information. This option can be enabled at the Grid level, and overridden at the member level.
The period of time that you specify is the duration after the expiration date of a lease, not its release date. For example, you specify a time period of 5 days when you enable this feature. If the lease time of an IP address is 10 days, but the lease is released after five days, the appliance still deletes the lease from the database after 15 days because the IP address has been leased.
If you plan to enable this feature after upgrading from a previous NIOS version, Infoblox recommends that you enable it during off-peak hours, as it may impact DHCP services.
To enable scavenging of IPv4 and IPv6 leases:
In the Network editor for IPv4 lease scavenging, click Toggle Advanced Mode if the editor is in basic mode, and then click IPv4 DHCP Options -> Advanced.
Complete the following:
3. Save the configuration.
DHCPv6 ranges are usually large and the DHCPv6 server randomly selects a new lease each time a client requests for a lease. The client can use the lease until it expires. After its expiration, the lease stays in the database with an expired state. These expired leases eventually lead to the increase in the number of database objects, because the probability of expired IPv6 leases getting reused is low.
Infoblox provides a DHCPv6 lease affinity feature that allows you to reuse expired IPv6 leases for DHCP clients. When you enable this feature, the DHCPv6 server automatically renews the expired leases. A DHCP client can retrieve the same lease from the DHCPv6 server after it expires and retains the same IP address. This feature helps reduce the amount of IPv6 leases in the database as the DHCP server issues the same lease multiple times for the same client.
The appliance ignores expired leases that are older than the specified period. Such leases are scavenged. Note that the grace period you define for lease scavenging is applicable for DHCPv6 lease affinity also. The minimum time period is six hours, maximum is 180 days and the default is set to seven days. For more information about scavenging leases, see Scavenging Leases.
The DHCPv6 server offers the same lease for a DHCP client, identified by DUID, after the lease expires and before the end of the grace period. The appliance removes the expired leases that are older than the grace period from the database.
DHCPv6 lease affinity and DHCPv6 lease scavenging are complementary features. For example, consider a scenario in which a visiting user gets an IPv6 lease that is retained for days, weeks, or months depending on the needs and then the user leaves. If the user returns and the lease is still within the grace period, the user gets the same IPv6 lease. This is lease affinity. When the user leaves, the IPv6 lease becomes inactive. This lease is scavenged after the grace period.
Note the following about DHCPv6 lease affinity:
To enable DHCPv6 lease affinity:
Complete the following:
The appliance stores the leases, which are either deleted or removed, in the recycle bin. These leases then become free and are automatically dissociated from their clients. For example, if you delete a range accidentally and restore it again, the IPv6 leases associated with the respective range are no longer associated with the same set of clients.
3. Save the configuration.
This page has no comments.