Wow, AT&T of all people should know better. I mean, I understand the attraction to that address for customer setup reasons, and bypassing different configured NAT address ranges (i.e. 10/8, 172.16/12, and 192.168/16 networks), but surely a customer who configures a custom address range would be capable of finding the new address.
Here's hoping that as IPv6 becomes ubiquitous, this is replaced broadly with something standard, possibly based on ND.
Less junk traffic, less latency for folk behind CGNAT on IPv6-only mobile networks, no chance of collision with poorly a configured network equipment.
I'll try it again in another year.
Some AT&T users are having issues because of such fuckery.
Usually if I don't have dns access I don't have an easy way to access twitter I think? I could be wrong about this. Is this meant to be used by text messages?
Now you can get to Twitter in the case of a resolver being down. Woo!
It also might help APNIC establish how much of the traffic to 188.8.131.52 is due to Cloudflare running a popular public DNS service, vs. how much is due to the address by subtracting the 184.108.40.206 traffic from the 220.127.116.11 data.
Am I missing any use case here?
Info on 18.104.22.168: https://blog.cloudflare.com/announcing-1111/