Last Modified: Feb 03, 2026
Affected Product(s):
BIG-IP DNS
Known Affected Versions:
17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3
Fixed In:
21.0.0.1, 17.5.1.4, 17.1.3.1
Opened: Apr 29, 2025 Severity: 3-Major
DNS64 stats (tmstat table profile_dns_stat) in the TMM behave as follows: dns64reqs - A queries to the server after the AAAA queries fail. Does not include the AAAA queries. dns64fails - Failed AAAA queries to the server. Does not include the subsequent A queries. DNS64 stats (tmstat table dns_cache_resolver_stat) in the cache behave as follows: mesh.dns64reqs - Includes both A and AAAA queries to the server. Includes both successful and failed AAAA queries. mesh.dns64nodata - Includes both A and AAAA query nodata responses (rcode=0 and no records). mesh.dns64error - Includes both A and AAAA query error rcode responses. mesh.dns64timeout - Includes both A and AAAA query timed-out responses.
The current cache resolver stats makes it difficult to diagnose backend DNS64 performance.
-- A DNS resolver cache is enabled on a DNS profile. -- The DNS profile has DNS64 configured.
None
Mesh.dns64reqs behaves like the TMM's dns64reqs (counts only DNS64 A queries to the server.) Additionally, a new stat mesh.dns64fails sums all failures (mesh.dns64nodata, mesh.dns64error, mesh.dns64timeout) and, like the TMM, only counts DNS64 AAAA failures to the server.