we are using AWS Route53’s Geolocation feature to direct users to our closest server.
When we run
dig @22.214.171.124 mydomain.tld from a server in Singapore, we do not get the response configured in Route53 for Asia; instead we get the response configured for North America.
I understand that 126.96.36.199 does not support ECS. However,
188.8.131.52 is 0.7 ms away, thus also in Singapore, so I would still expect that Route53 sees the DNS request coming from Cloudflare as originating from Singapore.
This thread confirms that this is how it should work, and when it does not work, it is probably a wrong entry in some (AWS’s?) geo location database that misplaces Cloudflare’s IPs.
How can I debug whether this is the case? How can I get it fixed? If the problem is in Route53, how can I determine from which IP 184.108.40.206 will make the request to Route53, so that I can report it to AWS support?
Currently our users are sent around half the globe when they use 220.127.116.11, which leads to a bad experience.