5 ms·

We (Cloudflare and APNIC) knew exactly what we were getting in to. We knew this was the only way that we'd be able to reclaim the space to be usable. And, in ab

We (Cloudflare and APNIC) knew exactly what we were getting in to. We knew this was the only way that we'd be able to reclaim the space to be usable. And, in about a month, we've gone from 1.1.1.1 being routable by only 92% of networks to 98.7% of networks — and climbing. Don't accept that you can't change the status quo.

dogecoinbase 8y ago
The space is allocated for research. To what end do you imagine it will be "usable", and for whom?
- yjftsjthsd-h 8y ago
  Well, it appears to be usable to 98.7% of networks for DNS lookups;)
- jhall1468 8y ago
  No it was not. 1.0.0.0/8 was unassigned space until 2010 when it was assigned to APNIC. It was never "allocated for research" and the reason nobody wanted it is all the cross-talk with internal devices using something they shouldn't have.
  - icedchai 8y ago
    Whois literally says 1.1.1.0/24 is a research prefix. netnum: 1.1.1.0 - 1.1.1.255 netname: APNIC-LABS descr: APNIC and Cloudflare DNS Resolver project descr: Routed globally by AS13335/Cloudflare descr: Research prefix for APNIC Labs
    - eli 8y ago
      APNIC designated 1.0.0.0/24 and 1.1.1.0/24 out of the whole /8 to APNIC Labs for "research" because they were getting so much bogus traffic. That just happened a few years ago.
      - icedchai 8y ago
        I know.
godzillabrennus 8y ago
I’m one of the first 100 users Cloudflare had sign up when it launched. I know because you sent me a t-shirt with my domain (and the 99 others) on it. I switched over to your new DNS service the day it launched. I’m also an AT&T customer both residential and for corporate useage. It’s been fun giving them trouble to get them to route this correctly. Hopefully this is behind us now and the ip becomes properly routable by even larger parts of the Internet as you grow this. One question though, is there a plan to add typo correction? It’s the only thing I miss from using OpenDNS.
- eastdakota 8y ago
  Thanks for being an early adopter! I've misplaced my version of that tshirt, which is a serious bummer. Remember working with our designer to hide all the "naughty" domains in the rays of the Cloudflare sun. :-) I doubt we'll do typo correction. We're DNS purists. DNS should answer what you ask. Doing otherwise opens many cans of worms.
  - godzillabrennus 8y ago
    Bummer on the shirt! It is a great design. Although, I'm biased since your team gave my domain a prominent placement. That position on typo correction is a bummer. I fat finger typing domains on occasion and found it handy to have my DNS service take care of that for me. Hopefully in time you guys reconsider. I am sure common errors could be corrected and it would lead to a better browsing experience for folks using your service. Thanks though for making such an excellent service free and fast! Love the work you do!
    - kardos 8y ago
      How would that even work? You'd get certificate errors on any TLS site with typo-correcting-dns right?
      - icebraining 8y ago
        I think they reply with their own HTTP server IP, which then redirects you to the "correct" address. I assume it breaks if you type a wrong https:// https:// address, but I guess few people do that, they just type the domain and let the site redirect to https:// https:// if needed.
sslalready 8y ago
I love how this service is actually improving the 1/8 situation. It’s a very cool solution to a challenging problem. Well executed!
djrogers 8y ago
This is one of the things I love about HN - someone can post an inane and inaccurate slam of a free service, and the CEO of the company providing said service responds in a clear and friendly manner.
- jahvo 8y ago
  It's not inane and inaccurate, I also think running a DNS on 1.1.1.1 is fucking stupid
  - eropple 8y ago
    Why, exactly? Be specific.
    - jahvo 8y ago
      It's a weird address that was going to cause problems like this
      - ukblewis 8y ago
        But exactly like the commenter stated. Part of the goal is to fix IPs like this being inaccesible. This DNS is both easy to access and using what should be, a perfectly accessible IP
      - saagarjha 8y ago
        It's a nice, short, memorable address that Cloudflare has every right to use. What's wrong here?
      - asdsa5325 8y ago
        What's weird about it? It's a valid IP address, the fact that they are all 1's isn't noteworthy except it's easy to remember.
        mirimir 8y ago
        It seems a somewhat popular pattern for DNS: 1.1.1.1 1dot1dot1dot1.cloudflare-dns.com 2.2.2.2 not found 3.3.3.3 not found 4.4.4.4 not found 5.5.5.5 not found 6.6.6.6 not found 7.7.7.7 not found 8.8.8.8 google-public-dns-a.google.com 9.9.9.9 dns.quad9.net

dogecoinbase 8y ago

The space is allocated for research. To what end do you imagine it will be "usable", and for whom?

yjftsjthsd-h 8y ago
Well, it appears to be usable to 98.7% of networks for DNS lookups;)
jhall1468 8y ago
No it was not. 1.0.0.0/8 was unassigned space until 2010 when it was assigned to APNIC. It was never "allocated for research" and the reason nobody wanted it is all the cross-talk with internal devices using something they shouldn't have.
- icedchai 8y ago
  Whois literally says 1.1.1.0/24 is a research prefix. netnum: 1.1.1.0 - 1.1.1.255 netname: APNIC-LABS descr: APNIC and Cloudflare DNS Resolver project descr: Routed globally by AS13335/Cloudflare descr: Research prefix for APNIC Labs
  - eli 8y ago
    APNIC designated 1.0.0.0/24 and 1.1.1.0/24 out of the whole /8 to APNIC Labs for "research" because they were getting so much bogus traffic. That just happened a few years ago.
    - icedchai 8y ago
      I know.

godzillabrennus 8y ago

I’m one of the first 100 users Cloudflare had sign up when it launched. I know because you sent me a t-shirt with my domain (and the 99 others) on it. I switched over to your new DNS service the day it launched. I’m also an AT&T customer both residential and for corporate useage. It’s been fun giving them trouble to get them to route this correctly. Hopefully this is behind us now and the ip becomes properly routable by even larger parts of the Internet as you grow this. One question though, is there a plan to add typo correction? It’s the only thing I miss from using OpenDNS.

eastdakota 8y ago
Thanks for being an early adopter! I've misplaced my version of that tshirt, which is a serious bummer. Remember working with our designer to hide all the "naughty" domains in the rays of the Cloudflare sun. :-) I doubt we'll do typo correction. We're DNS purists. DNS should answer what you ask. Doing otherwise opens many cans of worms.
- godzillabrennus 8y ago
  Bummer on the shirt! It is a great design. Although, I'm biased since your team gave my domain a prominent placement. That position on typo correction is a bummer. I fat finger typing domains on occasion and found it handy to have my DNS service take care of that for me. Hopefully in time you guys reconsider. I am sure common errors could be corrected and it would lead to a better browsing experience for folks using your service. Thanks though for making such an excellent service free and fast! Love the work you do!
  - kardos 8y ago
    How would that even work? You'd get certificate errors on any TLS site with typo-correcting-dns right?
    - icebraining 8y ago
      I think they reply with their own HTTP server IP, which then redirects you to the "correct" address. I assume it breaks if you type a wrong https:// https:// address, but I guess few people do that, they just type the domain and let the site redirect to https:// https:// if needed.

sslalready 8y ago

I love how this service is actually improving the 1/8 situation. It’s a very cool solution to a challenging problem. Well executed!

djrogers 8y ago

This is one of the things I love about HN - someone can post an inane and inaccurate slam of a free service, and the CEO of the company providing said service responds in a clear and friendly manner.

jahvo 8y ago
It's not inane and inaccurate, I also think running a DNS on 1.1.1.1 is fucking stupid
- eropple 8y ago
  Why, exactly? Be specific.
  - jahvo 8y ago
    It's a weird address that was going to cause problems like this
    - ukblewis 8y ago
      But exactly like the commenter stated. Part of the goal is to fix IPs like this being inaccesible. This DNS is both easy to access and using what should be, a perfectly accessible IP
    - saagarjha 8y ago
      It's a nice, short, memorable address that Cloudflare has every right to use. What's wrong here?
    - asdsa5325 8y ago
      What's weird about it? It's a valid IP address, the fact that they are all 1's isn't noteworthy except it's easy to remember.
      - mirimir 8y ago
        It seems a somewhat popular pattern for DNS: 1.1.1.1 1dot1dot1dot1.cloudflare-dns.com 2.2.2.2 not found 3.3.3.3 not found 4.4.4.4 not found 5.5.5.5 not found 6.6.6.6 not found 7.7.7.7 not found 8.8.8.8 google-public-dns-a.google.com 9.9.9.9 dns.quad9.net