This is duplicated one to my question in Superuser.
Akamai whoami tools can check whether a DNS resolver support EDNS-client subnet. The following result shows that 18.104.22.168 do support ECS.
[email protected] ~]$ dig +short TXT whoami.ds.akahelp.net @22.214.171.124
However, according to the Cloudflare FAQ, it should not support ECS.
126.96.36.199 is a privacy centric resolver so it does not send any client IP information and does not send the EDNS Client Subnet Header to authoritative servers.
Try another tool provide by Google. It shows that 188.8.131.52 doesn’t support ECS (no any ECS information responded).
[email protected] ~]$ dig +short TXT o-o.myaddr.l.google.com @184.108.40.206
So, is Akamai’s tool wrong? How can I explain the conflict?
This is expected and by design for this single Akamai testing endpoint.
This is expected - this (single) Akamai debug domain has ECS enabled for cross-provider debugging, but we do not send ECS to any of their production domains (such as akamaihd.net or similar).
If our policy on ECS changes, we’ll make an announcement ahead of that so that users are fully informed.
Look right below the part you quoted?
220.127.116.11 is a privacy centric resolver so it does not send any client IP information and does not send the EDNS Client Subnet Header to authoritative servers. The exception is the single Akamai debug domain
whoami.ds.akahelp.net to aid in cross-provider debugging. However, Cloudflare does not send ECS to any of Akamai’s production domains, such as
akamaihd.net or similar.
You even linked to it on your superuser post haha
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.