Zepto-LON gets geolocated to Helsinki by Cloudfront
# dig +short +https @ipv4-zepto-lon-1.edge.nextdns.io www.amazon.com
tp.47cf2c8c9-frontier.amazon.com.
d3ag4hukkh62yn.cloudfront.net.
13.32.143.198
# dig +short +https @ipv4-zepto-lon-1.edge.nextdns.io -x 13.32.143.198
server-13-32-143-198.hel50.r.cloudfront.net.The same happens for download.epicgames.com that also uses Amazon Cloudfront
4 replies
-
Not it is geolocated to Marseille. Is the issue on the NextDNS or Cloudfront side?
$ dig +short +https @ipv4-zepto-lon-1.edge.nextdns.io www.amazon.com tp.47cf2c8c9-frontier.amazon.com. d3ag4hukkh62yn.cloudfront.net. 3.160.199.130 $ dig +short +https @ipv4-zepto-lon-1.edge.nextdns.io -x 3.160.199.130 server-3-160-199-130.mrs52.r.cloudfront.net. -
This server IP is correctly geo-located in London. It is probably an error in cloudfront geo db.
I'm not sure why you mentioned Marseille, are you geo located in Marseille but steered to London by us and in turn steered to a Helsinki by Cloudfront?
-
Apologies, I should have spelled *Now* it is geolocated to Marseille.
Let me clarify. I am steered correctly to the London NextDNS server. But Cloudfront believes zepto-lon is somewhere in France and gives out a Marseille IP address.
Both anexia-lon and vultr-lon are fine and correctly return London IP addresses for the same hostname.
-
The issue is resolved now. The ticket can be closed.
Content aside
- 5 mths agoLast active
- 4Replies
- 52Views
-
2
Following