Bug ID 510638: [DNS] Config change in dns cache resolver does not take effect until tmm restart

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.4.1, 11.6.0, 11.6.1, 11.6.2, 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, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.6.0 HF6, 11.5.3 HF2, 11.4.1 HF9

Opened: Mar 04, 2015

Severity: 3-Major

Related Article: K37513511

Symptoms

Config change in DNS cache resolver does not take effect until tmm restart.

Impact

Changes made to DNS cache resolver are not in effect until tmm restarts. For example, changes to the DNS cache resolver's parameters Max. Concurrent Queries and Allowed Query Time do not load into the system until tmm restarts.

Conditions

Make changes to LTM DNS cache resolver.

Workaround

Restart tmm after making changes, or create a new DNS cache profile.

Fix Information

Config change in DNS cache resolver now take effect immediately and no longer require tmm restart.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips