Bug ID 520405: tmm restart due to oversubscribed DNS resolver

Last Modified: Aug 19, 2026

Affected Product(s):
BIG-IP GTM, LTM(all modules)

Known Affected Versions:
11.5.2, 11.5.2 hf1, 11.5.3, 11.5.3 hf1, 11.5.3 hf2, 11.6.0, 11.6.0 hf1, 11.6.0 hf2, 11.6.0 hf3, 11.6.0 hf4, 11.6.0 hf5, 11.6.0 hf6, 11.6.0 hf7, 11.6.0 hf8, 11.6.1, 11.6.1 hf1, 11.6.1 hf2, 11.6.2, 11.6.2 hf1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3

Fixed In:
12.0.0, 11.5.4

Opened: Apr 28, 2015

Severity: 3-Major

Related Article: K17131

Symptoms

A max-concurrent-queries configuration setting significantly above default can lead to a situation that causes tmm to restart in certain traffic loads.

Impact

tmm is restarted.

Conditions

DNS cache resolver configured with max-concurrent-queries setting significantly above default.

Workaround

Set the max-concurrent-queries configuration value closer to default.

Fix Information

A max-concurrent-queries configuration setting significantly above default no longer leads to a situation that causes tmm to restart in certain traffic loads.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips