Bug ID 2257425: Uploading QKview to iHealth using proxy still requires DNS resolution

Last Modified: Apr 24, 2026

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

Known Affected Versions:
17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3, 17.1.3.1, 17.5.0, 17.5.1, 17.5.1.2, 17.5.1.3, 17.5.1.4, 17.5.1.5, 21.0.0, 21.0.0.1

Opened: Mar 24, 2026

Severity: 4-Minor

Symptoms

Even when a proxy server is configured to upload QKviews directly to iHealth (as described in K000135909), the BIG-IP system must still be able to resolve hostnames. This can be achieved in one of two ways: Configure DNS nameservers — Set up name servers under sys dns so the BIG-IP can resolve hostnames automatically. Configure static host entries — As described in K13206, manually define static host entries on the BIG-IP. If using this method, you must add entries for all four hostnames listed in the Additional Information section of K000135909

Impact

Unable to upload QKviews directly to iHealth from the BIG-IP

Conditions

-- Proxy configured as per K000135909 -- no 'sys dns' nameservers defined (capable of performing DNS resolution) OR -- no static hosts defined per K13206 to the four hostnames defined in K000135909 under 'Additional Information' section

Workaround

-- Configure 'sys dns' nameservers capable of performing DNS resolution OR -- Configure static hosts per K13206 to the four hostnames defined in K000135909 under 'Additional Information' section

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips