Bug ID 493673: DNS record data may have domain names compressed when using iRules

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.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.4.1, 11.5.1, 11.5.2, 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 HF5, 11.5.3, 11.4.1 HF9

Opened: Dec 01, 2014

Severity: 3-Major

Related Article: K12352524

Symptoms

Some DNS record types forbid dns name compression in their record data, e.g., the NAPTR Replacement field. For certain parts of the DNS feature set, some of these record datum may have compressed names, e.g., DNS iRules, DNSSEC, GTM.

Impact

Some clients may expect uncompressed names and may not be able to follow compression pointers. This may cause the client to fail to use the RR.

Conditions

Using iRules.

Workaround

None.

Fix Information

Fields are properly not compressed, e.g., the NAPTR Replacement field.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips