Making DNS record changes more reliable

DNS is the very first step in accessing any website, API, or pretty much anything on the Internet, which makes it mission-critical to keeping your site up and running. This week, we are launching two significant changes that allow our customers to better maintain and update their DNS records.

D

DinaCloudflare

·May 25, 2020

Safer DNS edits land in the Cloudflare dashboard

DNS is the first lookup any client makes before reaching a website, API, or other Internet service, which makes it one of the most critical components of uptime. This week Cloudflare is shipping two updates aimed at making DNS record management more reliable: a confirmation step for record edits on its authoritative DNS platform, and a new onboarding flow for secondary DNS customers.

A save step for record changes

Cloudflare's DNS propagation is fast—typically under five seconds across its global network. That speed has always had a trade-off: in the dashboard, clicking out of an edited record field immediately pushed the change live. A mistyped value or an accidental toggle of the proxy status could take down a site or API before anyone noticed.

To address that, Cloudflare has introduced an explicit Save button for DNS record edits. Instead of committing changes the moment you blur an input, the new flow lets you review the update before it takes effect.

Making DNS record changes more reliable Embedded Image - xDYEWp

The confirmation layout applies to every record type and covers changes to content, TTL, and proxy status. The intent is to give users an extra checkpoint without slowing down the propagation itself once a change is confirmed.

Making DNS record changes more reliable Embedded Image - NRexAP

Cloudflare is asking for feedback on the new flow via a survey linked at the top of the DNS tab in the dashboard.

Secondary DNS onboarding rework

For customers using Cloudflare as a secondary DNS provider, the company has also launched a new onboarding experience. The details of the flow are outlined in a separate announcement, but the change is positioned as a faster and more resilient way to serve DNS records alongside a primary provider.