Slashdot Mirror
Cloudflare Launches 1.1.1.1 Consumer DNS Service With a Focus On Privacy (betanews.com)
BrianFagioli writes: Today, Cloudflare announces a new consumer DNS service with a focus on privacy. Called '1.1.1.1.' it quite literally uses that easy-to-remeber IP address as the primary DNS server. Why announce on April Fool's Day? Because the IP is four ones and today's date is 4/1 -- clever. The secondary server is 1.0.0.1 -- also easy to remember.
The big question is why? With solid offerings from Google and Comodo, for instance, does the world need another DNS service? The answer is yes, because Cloudflare intends to focus on both speed, and more importantly, privacy.
The big question is why? With solid offerings from Google and Comodo, for instance, does the world need another DNS service? The answer is yes, because Cloudflare intends to focus on both speed, and more importantly, privacy.
Looks good so far. The Piratebay is not censored (but is usually in my country), for example.
Who is Ian?
Cloudflare is an American company which was funded as and began its life as a "honey-pot", where the owners realized that the only way to extend its reach was to grow and style it as a genuine business.
As an American company they also have to respond to and carry out orders from the NSA and CIA if there is a court order present (which there always is -- they have their own "courts").
There is a lot of power in being able to tell who is looking at what website, and being able to possibly redirect them elsewhere when needed. If you think for a second that your browsing is private and that this service will not be used for shady purposes, then you are kidding yourself.
From the article:
"What many Internet users don't realize is that even if you're visiting a website that is encrypted -- has the little green lock in your browser -- that doesn't keep your DNS resolver from knowing the identity of all the sites you visit. That means, by default, your ISP, every wifi network you've connected to, and your mobile network provider have a list of every site you've visited while using them," says Cloudflare.
How does this stop ISPs from knowing which sites you visit? Once Cloudfare's DNS serves up the IP address (instead of your ISP's DNS), you still need to send/receive traffic from that IP address, which the ISP can easily monitor. The only way to prevent this is to use a VPN, while making sure to use your VPN's DNS as well.
The Pirate bay was not censored for me. Fast.
On the surface, yes. But, there are a number of options available for transport privacy that do not require using a VPN (provided you actually trust Cloudflare not to use your data and are savvy enough to setup one of the options) https://developers.cloudflare....
Mind the gap...
How is this better than OpenNIC and DNSCrypt? Remember that Cloudfare is the company that has a CEO that "woke up in a bad mood" and decided to ban a domain from their service. Yeah, it was a bunch of Nazis, but it shows that they're not really committed to freedom ... just freedom for points of view that don't irritate them.
Works faster than level 3, hello Cloudflare.
You are being ripped off every second of every day, so that advertisers can help rip you off even more tomorrow.
Not casting aspersions, but I've yet to see a reason why I (or anyone) should trust CF. The "KPMG" 'audit' reason is absolutely not sufficient, too.
The service is free and lures folks in with "fast". When a service is free, you're the product (see recent FB kerfuffle).
And, no IPv6 endpoint seems like a big missing component when "competitors" have it.
Mind the gap...
Dell IPMI
So the old maxim that the Internet routes around the damage is true!
Ezekiel 23:20
I think you're confusing it with 10.x.x.x.
I don't think they are. For example: https://supportforums.cisco.co...
Just ran a benchmark of the service, here are my results:
Final benchmark results, sorted by nameserver performance:
(average cached name retrieval speed, fastest to slowest)
1. 0. 0. 1 | Min | Avg | Max |Std.Dev|Reliab%|
- Cached Name | 0.020 | 0.023 | 0.029 | 0.002 | 98.0 |
- Uncached Name | 0.022 | 0.090 | 0.287 | 0.075 | 100.0 |
- DotCom Lookup | 0.049 | 0.055 | 0.066 | 0.003 | 100.0 |
1dot1dot1dot1.cloudflare-dns.com
CLOUDFLARENET - Cloudflare, Inc., US
1. 1. 1. 1 | Min | Avg | Max |Std.Dev|Reliab%|
- Cached Name | 0.021 | 0.023 | 0.030 | 0.002 | 95.9 |
- Uncached Name | 0.022 | 0.096 | 0.325 | 0.082 | 100.0 |
- DotCom Lookup | 0.048 | 0.073 | 0.166 | 0.043 | 100.0 |
1dot1dot1dot1.cloudflare-dns.com
MEGAPATH2-US - MegaPath Networks Inc., US
8. 8. 4. 4 | Min | Avg | Max |Std.Dev|Reliab%|
+ Cached Name | 0.048 | 0.052 | 0.057 | 0.002 | 100.0 |
+ Uncached Name | 0.060 | 0.104 | 0.344 | 0.073 | 100.0 |
+ DotCom Lookup | 0.063 | 0.070 | 0.158 | 0.014 | 100.0 |
google-public-dns-b.google.com
GOOGLE - Google LLC, US
8. 8. 8. 8 | Min | Avg | Max |Std.Dev|Reliab%|
+ Cached Name | 0.049 | 0.053 | 0.060 | 0.002 | 98.0 |
+ Uncached Name | 0.057 | 0.106 | 0.367 | 0.077 | 100.0 |
+ DotCom Lookup | 0.063 | 0.073 | 0.156 | 0.020 | 100.0 |
google-public-dns-a.google.com
GOOGLE - Google LLC, US
I just run my own. Not that hard.
Ahhh...the great dumpster continuum. Many a free computer will be found there. -- sowth (748135)
A zero host address in the local subnet in IPv4 means a reference to the local network. No matter your subnet length, 1.0.0.0 will always have a zero host address. 0/8 is reserved for "Local Identification". So 1.0.0.1 is the lowest valid IPv4 address.
So now we have DNS servers on 1.1.1.1, 4.4.4.4, and 8.8.8.8. Who has 2.2.2.2 and can they put a DNS server on it?
#naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
They ate our & 's that day.
So now we have DNS servers on 1.1.1.1, 4.4.4.4, and 8.8.8.8. Who has 2.2.2.2
OK, all these different numerical addresses are starting to get confusing. Someone ought to invent some kind of protocol to automatically map human-readable names onto these obscure numbers.
Did you try the alternate 1.0.0.1?
OK, all these different numerical addresses are starting to get confusing. Someone ought to invent some kind of protocol to automatically map human-readable names onto these obscure numbers.
One one one one
Four four four four
Eight eight eight eight
#DeleteChrome
Other easy to remember public DNS Servers
With this and all other attempts to provide privacy or security, what chain of trust allows me to believe that this is actually private or secure.
Surely there are many organizations with the resources to flood Slashdot with posts assuring me that this, or any other service, is secure.
Is TOR secure, or a NSA honeypot? How could I possibly know? Without personally having deep technical expertise, how can I trust anything.
An comments about tinfoil hats could be legit, or yet more planted posts.
We need a root source of trust or everything else falls apart.
Too bad Cisco uses this for a virtual IP in some o
Like their wireless lan controllers.
It is a shame so many "networking companies" can so badly fuckup basics of networking like that.
Remember when Linksys hard coded a bunch of public MIT server addresses as "internal" because they didn't know the most commonly used private-reserved IP block was 192.168.*.* and thought all IPs under 192.* were?
Or when Juniper hard coded 128.* as a blackhole range?
Back on the current topic, 1.0.0.0/8 was reserved for packet radio networks from 1981 until only 2010.
I can only imagine Cisco isn't alone in incorrectly utilizing it for their own purposes.
A prior company I worked for used the 14.* block internally as well, although partially in their defense the company and its internal networks predated RFC1918 by a couple of years, and the 14/8 was similarly reserved as 1/8 for unroutable traffic before any blocks of addresses were specifically allocated as such.
1.1.1.1 valid cloudflare
2.2.2.2 invalid owned by Orange S.A. according to RIPE
3.3.3.3 invalid owned by Amazon
4.4.4.4 invalid owned by Level 3 Communications, Inc
5.5.5.5 invaild owned by TelefÃnica Germany
6.6.6.6 invalid owned by Headquarters, USAISC
7.7.7.7 invalid owned by DoD Network Information Center
8.8.8.8 valid google
9.9.9.9 valid quad9
Minimum threshold fixed. Thanks!
6.6.6. the network of the Beast
All I want is a secure system where it's easy to do anything I want. Is that too much to ask ~~ Randall Munroe
2.2.2.2 is Orange (France Telecom) according to whois data.
Just found out that I own 10.10.10.10, so I'm putting my DNS there to mark my territory.
How is this better than DNS Watch? They are a free, not ad-sponsered, privacy-focused DNS provider with goals of neutrality and anti-censorship.
Cloudflare is basically the Big Brother gatekeeper of the Internet at this point, with strong ties to the US. Them claiming "privacy" as something they care about is pretty absurd.
"What do you despise? By this are you truly known." --Princess Irulan, Manual of Muad'Dib
/)
> Dell IPMI defaults the network address to this ip when it doesn't get a response from the dhcp server.
Already addressed in RFC3927 for quite some time. Have Dell update their firmware.
"169.254.0.0/16 - This is the "link local" block. As described in [RFC3927], it is allocated for communication between hosts on a single link. Hosts obtain these addresses by auto-configuration, such as when a DHCP server cannot be found."
And they can tell what site you accessed based on the HOST header or the SNI parameter when negotiating SSL...
http://spamdecoy.net - free throwaway anonymous email - avoid spam!
and why does Slashdot still not allow comment editing?
Because its a stupid feature that would only benefit careless people such as yourself allowing you to feel no consequences for your carelessness, while potentially hurting everyone else who could then feel real consequences from your constant never ending carelessness.
"His name was James Damore."