Bug ID 624876: Response Policy Zones can trigger even after entry removed from zone

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2

Fixed In:
13.0.0, 12.1.2 HF1, 11.6.3.3

Opened: Oct 25, 2016

Severity: 3-Major

Symptoms

If an entry (resource record) is removed from a response policy zone it is possible that it may still trigger as a match for RPZ.

Impact

The badzone.example.com entries will continue to be blocked by RPZ, even though the item has been removed.

Conditions

-- An RPZ zone contains an entry, for example badzone.example.com. -- That entry is subsequently removed.

Workaround

Delete /var/db/zxfrd.bin and /var/db/tmmdns.bin and restart the system using the following command: bigstart restart zxfrd. This recreates the databases without the remnants of the deleted entries.

Fix Information

The deleted entries are now properly handled and no longer trigger incorrect matches.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips