Um, thats going to be a problem for some people. There has been widespread use of 220.127.116.11 for wireless gateways/login pages, for sync links between firewall and many other things. You don’t have to use this DNS of course but the address has been used for internal purposes for many years.
Cloudflare’s mission is to help build a better Internet and today we are releasing our DNS resolver, 18.104.22.168 – a recursive DNS service. With this offering, we’re fixing the foundation of the Internet by building a faster, more secure and privacy-centric public DNS resolver. The DNS resolver, 22.214.171.124, is available publicly for everyone to use – it is the first consumer-focused service Cloudflare has ever released.
For IPv6, we have chosen 2606:4700:4700::1111 and 2606:4700:4700::1001 for our service. It’s not as easy to get cool IPv6 addresses; however, we’ve picked an address that only uses digits.
DNS-over-TLS (Transport Layer Security) RFC7858,
DNS-over-HTTPS protocol DoH,
Link: Introducing DNS Resolver, 126.96.36.199 (not a joke) – https://blog.cloudflare.com/dns-resolver-1-1-1-1/
Link: Announcing 188.8.131.52: the fastest, privacy-first consumer DNS service – https://blog.cloudflare.com/announcing-1111/
Useful Tool for testing
Link: jedisct1/dnsblast: A simple and stupid load testing tool for DNS resolvers – https://github.com/jedisct1/dnsblast
Tom Hollingsworth blogged about the problems:
As it turns out, 1/8 is a pretty bad address space for two reasons. 184.108.40.206 and 220.127.116.11. These two addresses are responsible for most of the inadvertent announcements in the entire 1/8 space. 18.104.22.168 is easy to figure out. It’s the most common example IP address given when talking about something. Don’t believe me? Google is your friend. Instead of using 192.0.2.0/24 like we should be using, we instead use the most common PIN, password, and luggage combination in the world. But, at least 22.214.171.124 makes sense.
Reclaiming 126.96.36.199 For The Internet | The Networking Nerd : https://networkingnerd.net/2018/04/05/reclaiming-1-1-1-1-for-the-internet/