4 ms·
Unrelated but there are some shenanigans involving Google's 8.8.8.8/8.8.4.4 dns servers and Spotify's service for podcasts https://traffic.megaphone.fm https://
by xaduha 4y ago
Unrelated but there are some shenanigans involving Google's 8.8.8.8/8.8.4.4 dns servers and Spotify's service for podcasts https://traffic.megaphone.fm https://traffic.megaphone.fm, Spotify redirects traffic.megaphone.fm to noop.megaphone.fm for people in Russia which resolves to 127.0.0.1, but doesn't affect Clouflare's 1.1.1.1
- giuliomagnifico 4y agoUhm weird. I don’t know, if Google is redirecting to 127.0.0.1 the users shouldn’t be able to listen anything. Maybe Google is doing it As a form of sanction, a lot of sites are blocking Russian users. By the way, I’m out of these DNS trouble since I started using Unbpund (recursive DNS).
- xaduha 4y agoI'm really not sure who to blame for this, because it also happens when using Cloudflare's Warp app and it might depend on the provider. But on the other hand why would noop.megaphone.fm even exist if Megaphone/Spotify are not involved in this? Most likely it's censorship and pressure put on these companies, even though Spotify is officially out they might still have something to lose by not complying. Or maybe there's some banal technical explanation like a long TTL so this redirect got cached and still persists for some servers. EDIT: tested Cisco OpenDNS servers which also resolve to 127.0.0.1, while Quad9's 9.9.9.9 resolve to proper ones. I think what is going on here is that if server supports geo-based responses, then it resolves to 127.0.0.1, even Cloudflare's 1.1.1.1 does, but depending on the provider it breaks. But if it doesn't support that, then it resolves to actual servers.