Reddit.com is not working on Spectra DNS

  • Thread starter Thread starter Sushubh
  • Start date Start date
  • Replies Replies 9
  • Views Views 2,394
It's just some DNS issue, just use Google DNS or Cloudflare DNS and it works just fine. I had posted last night about the same in the other thread. The IP address returned when using Spectra default DNS server goes through some weird routing. (Similar when using Jio DNS)

broadband.forum

Reddit.com is not working on Reliance Jio | Privacy Security Rights

Reddit finally blocked on Jio Gigafiber! : india
broadband.forum broadband.forum

[root@varkey-minipc ~]# dig +short www.reddit.com @180.151.151.151
reddit.map.fastly.net.
151.101.157.140
Click to expand...

X6O4VlN.webp
 
Last edited by a moderator:
Every freaking service having issue seems to be powered by Fastly. Imgur issues on Excitel is also due to connectivity with Fastly.
 
I have said time and again r/India has a tendency of overreaction and somehow they always convince themselves that the Government is out to get them.

Most of the times Reddit didn't used to work for me either, i changed my DNS. It still has outages for some time but it always works after some time.
 
Source


Dude's post has nothing about overreaction. If ISPs dns is not loading a particular domain, it is as good as blocked.
 

not sure if reddit can do anything if spectra/vodafone/jio owned dns servers are misconfigured. 😕
 
Well, Reddit (fastly in this case) controls what IP addresses are returned when a query is made to their name servers. And as I had posted earlier, that response changes depending on who is asking the fastly name servers.

When Spectra's DNS resolver queries the record, fastly returns an IP address which isn't properly routable on that network. Now who's fault is that? When Google DNS servers queries, fastly says go elsewhere, and when Cloudflare asks, it says go to another place altogether.

Clearly fastly here is trying to optimise the path so that we get pointed to their closest edge location. That mechanism could have very well gone wrong, or they may have tie up with carriers and the required configuration changes weren't propagated.

My point is, this is a special case, and I wouldn't put the blame on the ISPs entirely as things can go wrong at either places.
 

Top