Bug ID 1671065: F5SPKEgress incorrect DNS46 subnet translation after subnet change

Last Modified: Jul 31, 2025

Affected Product(s):
BIG_IP_NEXT(SPK) SPK(all modules)

Known Affected Versions:
1.7.11

Opened: Sep 16, 2024

Severity: 2-Critical

Symptoms

BIG-IP Next SPK may exhibit incorrect DNS46 address translation after changing the dnsNat46Ipv4Subnet in the F5SPKEgress Custom Resource.

Impact

Various traffic impacts may occur due to previous address translation being applied to DNS46 traffic depending on other network configuration including but not limited to: - Unroutable traffic - Duplicate IP Addresses - Dropped traffic - No traffic impact, just incorrect/undesired translation addresses

Conditions

- BIG-IP Next SPK is deployed and running - F5SPKEgress Custom Resource is deployed with dnsNat46Enabled - F5SPKEgress Custom Resource is deleted and re-applied with a different dnsNat46Ipv4Subnet.

Workaround

Delete the F5SPKEgress Custom Resource, scale the f5ingress pod to 0 then back to 1.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips