Bug ID 717306: Added ability to use VIP-targeting-VIP with DNS Cache server-side connections

Last Modified: Jan 12, 2024

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

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 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.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 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, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4

Fixed In:
15.1.0, 14.1.4.2

Opened: Apr 27, 2018

Severity: 2-Critical

Symptoms

A VIP-targeting-VIP setup for DNS Cache is not possible, as unbound connections do not match existing VIPs.

Impact

Unable to perform VIP-targeting-VIP configurations with DNS Cache connections.

Conditions

Virtual Server with same IP address as outbound DNS Cache server-side connections.

Workaround

None

Fix Information

Added the ability to have DNS Cache server-side connections match to VIPs for VIP-targeting-VIP scenarios with the DB Variable DNSCache.MatchWildcardVip. With this feature, BIG-IP might use multiple IP/port combinations from the snatpool for one DNS request.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips