Bug ID 879169: RESOLV::lookup @<virtual server name> may not work

Last Modified: Apr 11, 2024

Affected Product(s):
BIG-IP Install/Upgrade, LTM(all modules)

Known Affected Versions:
13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 16.1.0

Fixed In:
17.0.0, 16.1.1, 15.1.4

Opened: Feb 10, 2020

Severity: 3-Major

Symptoms

In v13 later, iRule command RESOLV::lookup @<vs name> does not work

Impact

The DNS virtual is working while iRule RESOVE::lookup does not send request to the virtual.

Conditions

The virtual server targeted by the RESOLV::lookup command is not configured with IP protocol UDP ("ip-protocol udp" in TMSH)

Workaround

Either of these: 1. Modify the target virtual server to specify an IP protocol of UDP 2. Replace the name with IP address to workaround the issue. set hostip [RESOLV::lookup @198.51.100.1 -a $hostname]

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips