Last Modified: Sep 13, 2023
Known Affected Versions:
12.1.0, 12.1.1, 12.1.2, 12.1.3, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 12.1.4, 13.1.0, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 13.1.1, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124
14.1.0, 126.96.36.199, 188.8.131.52, 184.108.40.206
Opened: Sep 17, 2018 Severity: 2-Critical
The dynconfd daemon may crash and restart if an FQDN template node is deleted (by user action or config sync) while ephemeral nodes are in the process of being created, and deleted as the result of new IP addresses being returned by a recent DNS query.
The dynconfd daemon crashes and restarts. Ephemeral nodes may not be updated in a timely manner while the dynconfd daemon is restarting.
This may occur on BIG-IP version 220.127.116.11 (and BIG-IP versions 13.1.x or v12.1.x with engineering hotfixes for ID 720799, ID 721621 and ID 726319), under the following conditions: 1. A DNS query returns a different set of IP addresses for one or more FQDN names. 2. While new ephemeral node(s) are being created (for new IP addresses and deleted (for old IP addresses), an FQDN template node is deleted (either by user action or config sync).
The dynconfd daemon does not crash and restart if an FQDN template node is deleted while ephemeral nodes are in the process of being created and deleted as the result of new IP addresses being returned by a recent DNS query.