...
Mobility: The DHCID is unique to each client and is usually based on the MAC address or DUID of the interface. Devices such as laptops that connect to both wired and wireless networks have different MAC addresses or DUIDs and different DHCID values for each interface. In this scenario, after either one of the network interfaces inserts a DNS record, updates are allowed from that interface only. This results in a disruption of service for DDNS updates when roaming between wired and wireless networks.
Migration: The second problem occurs during migration from non-ISC based systems to ISC systems. For example, if the user is migrating from a Microsoft-based system, the clients have A or AAAA and PTR records in the DDNS updates. As a result, new DDNS updates fail after the migration.
Mixed Environments: The final problem occurs in mixed ISC and non-ISC environments. For example, assume that both Microsoft and ISC DHCP servers update DNS records on the appliance. In a mixed environment, since the Microsoft DHCP server does not insert the DHCID, DDNS updates from ISC-based systems fail while updates from the Microsoft DHCP server are committed into the database.
BloxOne Universal DDI offers four modes to handle DDNS updates as described in the DDNS Update Verification Mode table :
...
If you are migrating from NIOS, the equivalent DDNS update verification modes are as follows:
DHCID Update Mode (BloxOne Universal DDI) | DDNS Update Method (NIOS) |
|---|---|
Update DNS if DHCID values match | Standard ISC |
Update DNS if DHCID record exists (match not required) | Check TXT only |
Update DNS and add or update DHCID records | ISC Transitional |
Update DNS without checking for or creating DHCID records | No TXT record |
| Note |
|---|
If you are migrating from NIOS to BloxOne Universal DDI, ensure that the DDNS Update Method in NIOS is configured as Standard so that DHCID records are created. |
...