Bug ID 440425: SOCKS and HTTP Explicit Proxy Profiles require DSN Resolver

Last Modified: Apr 10, 2019

Bug Tracker

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

Known Affected Versions:
11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 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.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9

Fixed In:
11.6.0

Opened: Dec 11, 2013
Severity: 5-Cosmetic

Symptoms

The SOCKS and HTTP Explicit Proxy profiles require a DNS Resolver. You must create the resolver before configuring the profile. You can create the resolver by navigating to Network :: DNS Resolvers in the GUI. Once the resolver is created, it appears in the list of DNS Resolvers when configuring the SOCKS or HTTP Explicit Proxy profiles.

Impact

If you do not create and specify a DNS Resolver, SOCKS and HTTP Explicit Proxy Profiles do not work.

Conditions

This is new functionality with version 11.5.0.

Workaround

You must create the resolver before attempting to create the SOCKS or Explicit Proxy profiles.

Fix Information

In this release, there is a button to add a DNS resolver directly in the SOCKS and HTTP Explicit profiles.

Behavior Change