Does this indicate an issue with EDNS subnet propogation? #1885
CampionLoong
started this conversation in
Potential issues
Replies: 0 comments
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
-
Not sure if this is a server side issue or one on DNSCrypt.
I use Quad9 with anonymization. I also set a custom EDNS subnet to (attempt to) steer supporting CDN to hosts in particular region.
When I query Akamai's whoami service, something like this comes up (addresses scramped):
"ns" "74.63.29.247"
"ecs" "2106:321:15::/48/48"
"ip" "74.63.29.247"
Here's the field's meaning according to Akamai (https://developer.akamai.com/blog/2018/05/10/introducing-new-whoami-tool-dns-resolver-information):
ns = "unicast IP address of the requesting recursive resolver"
ecs = "ECS client subnet included in the query"
ip = "representative ip address selected at random by Akamai’s authoritative nameserver from the ECS client subnet"
Since I set my own ECS subnet addresses with DNScrypt, it's nice to see Akamai receives one of the subnet range I specified.
I would expect the "ip" would be within the "ecs" subnet (as is the case in Akamai's own post above). However, the "ip" matches that of the recursive resolver (i.e. quad9) instead of that of my custom ECS subnet.
Question:
Does it mean Akamai is picking things wrong, or there's something else DNSCrypt need to do to help CDN pick from the custom EDNS in this kind of setup?
Beta Was this translation helpful? Give feedback.
All reactions