Bug ID 1026621: DNS cache resolver could not connect to remote DNS server with snatpool if multiple routes exist

Last Modified: Jan 20, 2023

Bug Tracker

Affected Product:  See more info
BIG-IP DNS, GTM, LTM(all modules)

Known Affected Versions:
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, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 17.0.0, 17.0.0.1, 17.0.0.2

Opened: Jun 16, 2021
Severity: 3-Major

Symptoms

DNS query could not be resolved properly.

Impact

Unable to use snatpool for cache resolver.

Conditions

1. dnscache.matchwildcardvip is enabled 2. Multiple possible routes to destination DNS server exist. This can be triggered by either using a gateway pool, or using dynamic routing with multiple equal paths available.

Workaround

Ensure only a single route to destination exists, or disable dnscache.matchwildcardvip NOTE: With dnscache.matchwildcardvip disabled, snatpool will not be used.

Fix Information

None

Behavior Change