Last Modified: Jun 28, 2025
Affected Product(s):
BIG-IP Install/Upgrade, TMOS
Known Affected Versions:
17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.5.0, 17.5.1
Opened: May 29, 2025 Severity: 3-Major
Zones with over 100 records of the same type trigger an error during loading after upgrading to 17.1.2 or higher release, similar to the following: error: dns_master_load: db.external.example.f5.com.:378: record1.example.f5.com.: too many records zoneload: error: zone example.f5.com/IN/external: loading from master file db.example.f5.com. failed: too many records zoneload: error: zone example.f5.com/IN/external: not loaded due to errors.
BIND refuses to load zones, resulting in service disruption for affected zones.
Occurs when "max-records-per-type" in a zone exceeds the default limit of 100. Upgrading to 17.1.2 or higher release, given the BIND version upgrade that comes along with it, especially if configured for a single GTM pool with more than 100 members or cumulative pools exceeding 100 members. Configuration changes to "max-records-per-type" won’t be accepted prior to the upgrade given that new BIND version (9.18.28) is not yet installed.
After upgrading to v17.1.2 or higher, increase the max-records-per-type value as required. For instructions on how to do that, follow the steps documented in this article: https://my.f5.com/manage/s/article/K000150564
None