Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

My guess is this is just incompetence and not intentionally made to block CloudFlare.

I have one of those routers, and I couldn't use 1.1.1.1 because it was routing to an internal interface on the router. I confirmed this with ping, I was getting microsecond response times from 1.1.1.1.

Under the new firmware, 1.1.1.1 is just dead. So it's probably still connected to the local interface, and nothing is listening.



They started blocking 1.0.0.1 and CF ipv6 DNS too. This has to be intentional.


Hmmm that's a fair point. But then why not also block 8.8.8.8?


Everyone has heard of google, attacking them would cause back lash. Non technical people haven't heard of cloudflare so it is a softer target.


Probably because they know they would never be able to convince anyone that it was a technical bug and not malice. A surprising number of people seem to be convinced this was unintentional.


At least google doesn't block rarbg or thepiratebay. Good riddance to CF.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: