Last Modified: May 29, 2024
Affected Product(s):
BIG-IP DNS
Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2
Fixed In:
16.1.0, 15.1.7
Opened: Oct 30, 2020 Severity: 3-Major
-- EDNS UDP query against DNS Express zone for larger responses get truncated. --Non-EDNS query against DNS Express zone was truncated completely including the ANSWER section.
No proper DNS responses.
--Configure UDP and TCP listeners with DNS profile that has DNSX enabled and BIND disabled. --Perform EDNS/Non-EDNS queries against the listener.
Perform either of the following workarounds: 1. Enable DNS Express minimal-responses using DB key dnsexpress.minimalresponse. For detailed information, please refer to K41004650: Enable DNS Express minimal-responses for the Authority and Additional Records sections 2. Disable truncating UDP DNS response using DB key dns.udptruncate. For detailed information, please refer to K91537308: Overview of the truncating rule when DNS response size is over 512 Bytes
None