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

From https://en.wikipedia.org/wiki/1.1.1.1#Criticism_and_problems :

Technological websites noted that by using 1.1.1.1 as the IP address for their service, Cloudflare created problems with existing setups. While 1.1.1.1 was not a reserved IP address, it was and is used by many existing routers (mostly those sold by Cisco Systems) and companies for hosting login pages to private networks, exit pages or other purposes, rendering the use of 1.1.1.1 as a manually configured DNS server impossible on those systems. Additionally, 1.1.1.1 is blocked on many networks and by multiple ISPs because the simplicity of the address means that it was previously often used for testing purposes and not legitimate use. These previous uses has lead to a huge influx of "garbage" data to Cloudflare's servers.



What kind of demented person uses 1.1.1.1, a routable public address since 2010, for internal addresses. What's wrong with 10.0.0.0/8 or 192.168/16?


I'm gonna guess they valued the aesthetics over the problems / conditions.


You'd think in that case they'd have gone with 10.10.10.10. Silly people.


10.10.10.10?


10.11.11.10?


10.00.00.01?


That’s intentional, from what I remember. All non-DNS traffic is analyzed for research purposes (not by Cloudflare though).

A wake-up call for all those (ab)users of public address space is also desperately needed. All IPv4 addresses will soon be allocated. Failure to use only private address spaces will cause problems, very soon.


That's not a valid criticism; that's an excuse.

CloudFlare likely did this on purpose, because so many people can't get their heads out of their own asses and follow spec. Now there's a big spotlight on the people purposefully breaking the network. And it will be fixed, eventually, whereas previously, AT&T would have just said "take a hike".




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

Search: