You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I cannot get ECS to work even after this change. Entering the same CDN domain but with one clientIp in Europe and another in the USA, I get the same resolved IP address. This is with both Google's DNS (8.8.8.8) as well as Quad9's ECS-enabled DNS (9.9.9.11).
If I use Resolve-DnsName or dig then the same CDN domain's resolved IP changes depending on the provided subnet / source IP address.
The above is why I've opted to raise an issue and not a PR, as I do not know how to fix the underlying ECS support.
The text was updated successfully, but these errors were encountered:
EDNS Client Subnet support does not work because the call to
resolve
inquery
is malformed.query
https://github.com/song940/node-dns/blob/b2fdf66a1987e2597ad1b1f0948d0ac5c4acbfe2/index.js#L46
resolve
https://github.com/song940/node-dns/blob/b2fdf66a1987e2597ad1b1f0948d0ac5c4acbfe2/client/udp.js#L9
The fixed call should be:
However
I cannot get ECS to work even after this change. Entering the same CDN domain but with one
clientIp
in Europe and another in the USA, I get the same resolved IP address. This is with both Google's DNS (8.8.8.8) as well as Quad9's ECS-enabled DNS (9.9.9.11).If I use
Resolve-DnsName
ordig
then the same CDN domain's resolved IP changes depending on the provided subnet / source IP address.The above is why I've opted to raise an issue and not a PR, as I do not know how to fix the underlying ECS support.
The text was updated successfully, but these errors were encountered: