Better DNS response for Reddit CDN (Fastly)?
Hello,
I've finally found the issue causing images and videos to load very slow on Reddit (sometimes it can take 7-8 seconds for a video to even start playing on a lowest quality with a 100 Mbit/s connection). The NextDNS servers for any of the following:
www.redditmedia.com, www.redditstatic.com, preview.redd.it, v.redd.it, i.redd.it
always give me the same response:
199.232.137.140
After checking here:
https://dnschecker.org/#A/i.redd.it
https://dnschecker.org/#A/v.redd.it
It looks like the Cloudflare, Google, OpenDNS and many more providers return the following IP addresses instead:
151.101.129.140
151.101.65.140
151.101.1.140
151.101.193.140
Indeed, after switching to Cloudflare and Google for testing purposes, videos and images on Reddit are loading almost instantly. Then I switched back to NextDNS and the issue came back again.
My diagnostics:
https://nextdns.io/diag/d6e3add0-6294-11ec-a5e2-d5cbdc939c6f
Is there any way to get the better (for me) 151.101.*.* DNS responses in this case while using NextDNS?
19 replies
-
I also have this problem, it's really slow reddit with nextdns, will be great to get it resolved
on the main reddit page, the images don't load and I get this message "Sorry, we couldn't load posts for this page."
-
What do you get for https://www.fastly-debug.com with nextdns?
-
Olivier Poitrey it's now "Collecting data please wait" for 15 minutes, should I let it run a few hours?
-
Miguel it should be almost instant.
-
Olivier Poitrey If the question was for me, then here are my results (hint for others - disable adblocker if fastly-debug does not complete):
-
Chris NextDNS I have the same issue than Chris
-
Paweł Kowalik based on this report, you are getting the best fastly region for your network.
-
NextDNS after unblocking the site fastly-analytics.com, it now works fine, what do you wanted to see from the site fastly-debug.com ?
-
Miguel same as the screenshot above.
-
NextDNS Exactly, but somehow for Reddit which uses Fastly, I still get the response with the slower 199.232 IP addresses pool instead of the faster 151.101 one when using NextDNS. Do you think I should escalate this problem to Reddit or Fastly instead?
-
Paweł Kowalik please show traceroute both IPs. It should probably be escalated to fastly yes.
-
NextDNS
The much slower one:
Common 1-6 hops skipped
7 16 ms 15 ms 16 ms 195.149.239.46
8 33 ms 47 ms 33 ms orange.com.pl [80.81.196.254]
9 33 ms 32 ms 33 ms fra2.decixfra.fastly.net [80.81.195.55]
10 33 ms 32 ms 32 ms 199.232.137.140
The much faster one:
Common 1-6 hops skipped
7 28 ms 29 ms 28 ms win-b2-link.ip.twelve99.net [62.115.152.92]
8 33 ms 56 ms 32 ms win-bb4-link.ip.twelve99.net [62.115.114.182]
9 34 ms 35 ms 33 ms ffm-bb2-link.ip.twelve99.net [62.115.138.22]
10 * * 33 ms ffm-b11-link.ip.twelve99.net [62.115.124.119]
11 32 ms 32 ms 33 ms fastly-ic328449-ffm-b11.ip.twelve99-cust.net [213.248.87.111]
12 38 ms 37 ms 39 ms 151.101.13.140
It looks like it's not a latency issue, as even the better route has 2 more hops. I also find something that might be interesting - both 199.232.137.140 (slow Reddit CDN server) and 194.45.101.249 (resolver recognized by fastly-debug when using NextDNS) points to the Germany - Frankfurt by checking their geolocation. -
NextDNS As a workaround, I added the following custom reponses in the NextDNS settings and it seems to work for now. I attached my current configuration, so maybe it will help someone else too. Please note that you'll probably need to use different IP address than mine (you can use dnschecker.org to find the best one for you). Anyway, thanks for help to anyone involved here!
-
-
it's now "Collecting data please wait" for 15 minutes
While I don't seem to have issues with Reddit, I also see this status never finishing.
-
I've been experiencing this exact same issue, and I can't believe it's been going on for almost 3 years! It doesn't appear to be a NextDNS specific issue. Even my ISP's own DNS resolver has the same issue.
Server: dnsr1.sbcglobal.net Address: 68.94.156.1 Non-authoritative answer: Name: reddit.map.fastly.net Address: 146.75.41.140 Aliases: i.reddit.comHitting that Fastly IP in a browser shows that it's a node in Seattle (BFI is the Seattle airport code).
Details: cache-bfi-kbfi7400100-BFI (146.75.41.140)I'm in the midwest using the Chicago and Kansas City NextDNS resolvers, so it makes no sense for Fastly to route me to their Seattle POP.
Additionally, Fastly seems to experience congestion with some of their POPs depending on the time of day.
You can use https://www.fastly-debug.com/ to get some statistics on your Fastly connection, though it may not route you to the same POP as Reddit. However you can rewrite "fastly-debug.com" using NextDNS to the same IP that i.reddit.com is resolving to, and get statistics on that specific POP.
The BFI server above was showing sub-1mbps bandwidth, 100ms ping, and >30 retransmits for a few hours this evening.
I also sometimes get routed to the Kansas City (MCI) Fastly POP, which is also performing poorly this evening:
For comparison, the 151.101.*.140 IPs returned by Cloudflare/Google/Quad9 seem to be anycast IPs that route to a nearby POP (in my case Columbus, Ohio) which performs much better.
So rewriting i.reddit.com to one of these IPs does work around the issue nicely.
I wish some Fastly customers would start pushing them for a resolution to this, though. It's a combination of poor geolocation routing and congested peering on Fastly's part. I am curious what Cloudflare/Google/Quad9 are doing differently that causes them to return the 151.* anycast IPs though.
Content aside
-
2
Likes
- 2 mths agoLast active
- 19Replies
- 1035Views
-
9
Following