We have an active Prolexic mitigation policy for a /24 subnet, confirmed in the Akamai portal. However, our origin server logs (nginx) continue to show requests from the blocked source IPs. The mitigation appears to be bypassed.
Our configuration:
- Prolexic is deployed in DNS-based (CNAME) mode.
- Origin servers are configured to only accept traffic from Akamai's published CIDR ranges.
- The mitigation rule targets TCP/80 and TCP/443, rate-based.
Example log entry from origin (real IP obfuscated):
```
123.45.67.89 - - [21/Oct/2024:15:22:01] "GET /api/v1/test HTTP/1.1" 200
```
This suggests the traffic is not being proxied through Akamai's scrubbing centers. Has anyone encountered this with DNS-based deployment? The most likely culprit seems to be DNS propagation or a misconfigured ACL, but the origin ACLs are correct. Looking for specific troubleshooting steps beyond the standard checklist.