Bug ID 1325981: DNS outbound-msg-retry causes TMM crash or core, and changes to outbound-msg-retry do not take effect immediately

Last Modified: Dec 07, 2023

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

Known Affected Versions:
17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3

Fixed In:
17.1.1

Opened: Jul 31, 2023

Severity: 3-Major

Symptoms

TMM crashes when attempting to perform DNS resolution with a DNS resolver or DNS cache, if the outbound-msg-retry configuration value is set to 0. Additionally, modifications to the outbound-msg-retry value do not immediately take effect, and the DNS cache or resolver may continue to function with the previously-configured value.

Impact

Traffic disrupted while tmm restarts.

Conditions

A DNS cache or DNS net resolver with outbound-msg-retry set to 0.

Workaround

Do not set the 'outbound-msg-retry' value for DNS caches and DNS resolvers to a value of 0. If making configuration changes to the 'outbound-msg-retry' value, also change the "use-ipv4" or "use-ipv6" setting (i.e. toggle from "yes" to "no", and then back to "yes").

Fix Information

The DNS cache and DNS resolver outbound-msg-retry setting is now restricted to being a positive integer (i.e. a value greater than 0). Changes to the outbound-msg-retry setting now take effect immediately.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips