Very slow with Akamai

dash-dns
dns-resolver
#1

Hi !

I’m an user of a french service named Molotov.tv and it doesn’t work with 1.1.1.1
It seems that Molotov uses Akamai, and when I test with 1.1.1.1 activated, the results are very bad (test with this url : http://secure-cdn3-live-mlflux-net.akamaized.net.t1.re)

Do you have this problem too ?
Thanks !

#2

Probably the client-subnet EDNS issue. Cloudflare does not support that for privacy reasons and you probably get directed to a default server which has a higher latency for you.

1 Like
#6

secure-cdn3-live-mlflux-net.akamaized.net.t1.re resolves to the same IP address globally https://dnschecker.org/#A/secure-cdn3-live-mlflux-net.akamaized.net.t1.re. How is Cloudflare’s DNS service impacting the performance?

#7

The entire setup appears to be somewhat peculiar *).

That host does resolve to one single address globally, however a request to that host immediately redirects to a randomly generated CNAME for secure-cdn3-live-mlflux-net.akamaized.net. That host, in turn, appears to be another CNAME for a1767.dscw16.akamai.net and this where the fun starts, https://dnschecker.org/#A/a1767.dscw16.akamai.net


*) Not only because of the DNS chains but also because of how it uses the randomly generated hosts.