Cloudflare is adding a new feature to its hosting and firewall products that the networking company hopes will address the slow uptake of the Domain Name System Security Extensions (DNSSEC) protocol.

The method to support the DNSSEC protocol has been a manual one before this, requiring a website owner to add a "DS record" to its account with their registrar.

A Cloudflare customer that is working with a registry that supports DNSSEC can activate it for their account by the press of a button from the Cloudflare dashboard.

DNSSEC proves authenticity and integrity -- though not confidentiality -- of a response from the authoritative nameserver. This makes it much harder for a bad actor to inject malicious DNS records into the resolution path through malware techniques such as BGP Leaks and cache poisoning. Trust in Domain Name System (DNS) can be critical when a domain is publishing record types that are used to declare trust for other systems.

(Source: iStock)

A simple way for a user to test if DNSSEC is enabled within their network is to try and load brokendnssec.net with a browser. If the page loads, the protocol is inactive.

The number of DNS queries validated by recursive resolvers for DNSSEC has remained flat over the years. Worldwide, less than 14% of DNS requests have DNSSEC validated by the resolver according to APNIC, which functions as the Regional Internet Registry for the Asia Pacific area.

Cloudflare believes that struggle to add a DS record may be at the root of the low utilization:

Locating the part of the registrar UI that houses DNSSEC can be problematic, as can the UI of adding the record itself. Additional factors such as varying degrees of technical knowledge amongst users and simply having to manage multiple logins and roles can also explain the lack of completion in the process. Finally, varying levels of DNSSEC compatibility amongst registrars may prevent even knowledgeable users from creating DS records in the parent.

While all of this is going on, the ICANN Organization is preparing to change the cryptographic keys that help to protect the Internet's DNS for the first time.

The changing of the keys, known as the "Root Key Signing Key (KSK) Rollover," is currently scheduled for October 11. Final ratification of that date has not yet been done.

ICANN attempted this update a year ago but had to cancel it at the last minute. The rollover was postponed due to "unclear data received just before the rollover." ICANN thinks the two thirds of users that do not use DNSSEC will not be impacted by the KSK rollover.

Related posts:

• DNS Rebinding Attack Could Affect Half a Billion IoT Devices
• How the Cloud Is Changing the Identity & Access Management Game
• Researchers Show How Attackers Can Crack LTE Data Link Layer
• Google, Roku, Sonus Rush Out Patches for DNS Vulnerability

— 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.