Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP APM
Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2
Fixed In:
12.1.0, 12.0.0 HF3
Opened: Jul 13, 2015 Severity: 3-Major
If a Network Access-connected client changes their local dns setting while connected, all DNS requests end up going to the Network Access DNS server
Client DNS requests will always go through the Network Access DNS servers.
Network Access DNS Relay installed on the client APM has a DNS network access resource configured which uses some address space End user manually changes their resolver.
There are two workarounds: 1) In DHCP client environments, if a DHCP lease expires and changes their local DNS settings, this works properly. This only happens if manual changes are made on the client machine. 2) The client can be rebooted, which will clear the problem.
If a client manually changes their local DNS settings while connected via Network Access, DNS requests that do not match the Network Access policy will not be routed to the Network Access DNS server.