Cloudflare retires classic DNS: a publisher’s change checklist
The new DNS screen is now mandatory. Update your team’s instructions and check landing pages without unnecessary record changes.
On October 30, 2026, Cloudflare announced that its classic DNS page is no longer available and the new interface is the default on every plan. This completes a transition announced in May, rather than introducing a new domain connection method. Existing record types can now also be changed, such as A to CNAME; the announcement does not give the exact date that capability was added.
What to do now
A working landing page does not need a DNS change because the screen changed. Open the domain’s DNS Records page, locate the hostname, and update your team’s instructions. Before an actual edit, save an export using Import and Export → Export. Separately record the affected entry’s type, value, TTL, and proxy status. A DNS export is not a website backup.
Training scenario: only the interface changed
An editor cannot find the old screen for a product-review subdomain. The responsible operator matches the hostname and existing record, opens the published page, and checks its outbound link. Everything works, so the record stays unchanged. The deliverable is an updated guide with a secret-free screenshot of your own account, not an unnecessary migration.
Training scenario: moving a landing page
The host actually requires an A-to-CNAME change. Obtain the exact target hostname and confirmation of HTTPS setup first. Save the previous parameters and agree a verification window. Edit only the intended record with Edit → Save; never substitute an arbitrary hostname for an IP. Then check DNS resolution, HTTPS, page content, and the final link destination. If checks fail, pause new placements and investigate with the host; reverting a record does not instantly refresh every cache.
Change record template
Domain and subdomain; reason; owner; old type/value/TTL/proxy; new host-provided settings; export location; change time; DNS/HTTPS/page/link results; rollback condition. Fill this in before editing. This is our editorial worksheet, not a Cloudflare feature.
Limits and next step
The announcement concerns Cloudflare’s interface, not indexing rules or conversion approval. When a hosting partner manages DNS, follow that partner’s process. Check regional service conditions separately. For a campaign in our AffiliateCore platform, review the campaign link and offer terms in your account after checking your own site; changing DNS does not create an approved result.