APM-DHCP Access Policy Example and Detailed Instructions

My regional support contacts at F5 confirmed today that iapp is supported for versions v16 to v17. They have also requested to update the supported versions in the article https://my.f5.com/manage/s/article/K000135007 ("K000135007: Configure dynamic DNS from a DHCP server for BIG-IP APM network access clients") and you can check that the versions v16 to v17 are already shown.

On the other hand comment also as suggested to take into account that if the DHCP windows server is used and you use rfc3011 “subnet selection” or rfc3527 “subnet/link-selection sub-option”, to avoid receiving DHCPACKs it is essential to create in the DHCP windows server a “dummy DHCP Scope” (as in: all addresses excluded) for an IP range covering all possible DHCP relay's source addresses, as it is commented here https://learn. microsoft.com/en-us/archive/msdn-technet-forums/20e50652-5a19-4dee-a6af-4c09f3fcfd1b to prevent the F5 from being considered by the windows DHCP server as a “rogue relay agent”.