Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Infrastructure Security //

DNS

4/4/2018
08:05 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

Cloudflare vs. Google: Making DNS Protocol Better, More Secure

With the release of 1.1.1, Cloudflare is looking to make the DNS protocol better and more secure, while speeding up the Internet. Is this helping Google or leaving the company behind?

Dynamic Name System (DNS) is one of the basic plumbing operations that makes the Internet work. It takes words that people understand and translates them into numeric IP addresses that the Internet understands.

It's not a perfect arrangement, by any means. It's 35 years old and insecure.

While DNSSEC is a protocol that makes these conversations happen securely within DNS, information from the DNS boundary to the requestor is not secured. DNS requests can be monitored by some central authority -- such as a nation state or data miner fairly -- fairly easy. From that, traffic can be obtained and blocking of certain sites be initiated.

This is what happened in Turkey in 2014 when the government blocked Twitter.

In most areas though, it's the ISP that does the direct DNS requesting, which then actually monitors user activity and resells that data to marketers. This ability to resell is related to changes in government law dating to 2017, which no longer requires user consent for that to happen.

Cloudflare, the San Francisco web hosting service, wants to change this.

The company have developed a system eponymously named 1.1.1.1, which bypasses the usual DNS system to deliver DNS resolution that is three times faster than Google's service. Not only that, but Cloudflare also notes:

Cloudflare will never store any information in our logs that identifies an end user, and all logs collected by our public resolver will be deleted within 24 hours. We will continue to abide by our privacy policy and ensure that no user data is sold to advertisers or used to target consumers.

Cloudflare also committed to "retaining KPMG, the well-respected auditing firm, to audit our code and practices annually and publish a public report confirming we're doing what we said we would."

Take that, Google.

Cloudflare's privacy aims go deeper than just beating Google at speed of resolution. 1.1.1.1 supports emerging new open standards such as DNS-over-TLS, which takes the existing DNS protocol and adds transport layer encryption, as well as DNS-over-HTTPS, which includes security and supports other transport layers and new technologies such as HTTP/2 Server Push.

Google has dabbled in trying out DNS-over-TLS, thinking that it might grab more of that information-rich DNS traffic and mine it. Other browser creators were loath to send all that traffic to Google, so the method has not truly taken off as of yet.

1.1.1.1 may be a way to increase adoption of it, since it doesn't data mine.


The fundamentals of network security are being redefined -- don't get left in the dark by a DDoS attack! Join us in Austin from May 14-16 at the fifth-annual Big Communications Event. There's still time to register and communications service providers get in free!

Getting 1.1.1.1 to work with whatever device a user has is fairly simple. Although this site has explicit instructions for most systems, it basically comes down to replacing the current DNS resolver address with 1.1.1.1.

This kind of altruistic effort by Cloudflare may end up improving the quality of the Internet for everyone. If it does, then the demand for the company's services may grow as it becomes even more ubiquitous in practice. But, this is one of the rare examples of a company following Spike Lee's imprecation to Do The Right Thing.

Related posts:

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Cloud Security Startup Lightspin Emerges From Stealth
Kelly Sheridan, Staff Editor, Dark Reading,  11/24/2020
Look Beyond the 'Big 5' in Cyberattacks
Robert Lemos, Contributing Writer,  11/25/2020
Why Vulnerable Code Is Shipped Knowingly
Chris Eng, Chief Research Officer, Veracode,  11/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: We are really excited about our new two tone authentication system!
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-4126
PUBLISHED: 2020-12-01
HCL iNotes is susceptible to a sensitive cookie exposure vulnerability. This can allow an unauthenticated remote attacker to capture the cookie by intercepting its transmission within an http session. Fixes are available in HCL Domino and iNotes versions 10.0.1 FP6 and 11.0.1 FP2 and later.
CVE-2020-4129
PUBLISHED: 2020-12-01
HCL Domino is susceptible to a lockout policy bypass vulnerability in the LDAP service. An unauthenticated attacker could use this vulnerability to mount a brute force attack against the LDAP service. Fixes are available in HCL Domino versions 9.0.1 FP10 IF6, 10.0.1 FP6 and 11.0.1 FP1 and later.
CVE-2020-9115
PUBLISHED: 2020-12-01
ManageOne versions 6.5.1.1.B010, 6.5.1.1.B020, 6.5.1.1.B030, 6.5.1.1.B040, ,6.5.1.1.B050, 8.0.0 and 8.0.1 have a command injection vulnerability. An attacker with high privileges may exploit this vulnerability through some operations on the plug-in component. Due to insufficient input validation of ...
CVE-2020-9116
PUBLISHED: 2020-12-01
Huawei FusionCompute versions 6.5.1 and 8.0.0 have a command injection vulnerability. An authenticated, remote attacker can craft specific request to exploit this vulnerability. Due to insufficient verification, this could be exploited to cause the attackers to obtain higher privilege.
CVE-2020-14193
PUBLISHED: 2020-11-30
Affected versions of Automation for Jira - Server allowed remote attackers to read and render files as mustache templates in files inside the WEB-INF/classes & <jira-installation>/jira/bin directories via a template injection vulnerability in Jira smart values using mustache partials. The ...