Bug ID 1933357: DNS64 stats between cache resolver and TMM non-cache have inconsistent behavior.

Last Modified: Oct 15, 2025

Affected Product(s):
BIG-IP DNS(all modules)

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

Opened: Apr 29, 2025

Severity: 3-Major

Symptoms

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.

Impact

The current cache resolver stats makes it difficult to diagnose backend DNS64 performance.

Conditions

-- A DNS resolver cache is enabled on a DNS profile. -- The DNS profile has DNS64 configured.

Workaround

None

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips