Manage Cloudflare DNS

Manage DNS through your team's Cloudflare connection

You need administrator access to the MetricPoints team and a Cloudflare connection covering the intended zone. Grant Zone Read and DNS Read to view records, plus DNS Edit to change them. Zone Edit is not needed for record changes.

1. Load and check the zone

1. Open All Sites → your site → Settings → Cloudflare DNS records.
2. Choose Load / refresh records. Confirm the displayed zone and connection. MP uses the site's existing team default, override, or legacy connection.
3. Search for a record or move between pages. This is a snapshot from the last refresh, not a live feed.

DNS belongs to the whole zone. A change made from one site's settings can affect other sites, email, and services in that domain. Restrict the connection's token to the zones your team should manage.

2. Prepare an addition, edit, or removal

• Add: enter a reason, select the record type, and enter its values. Use @ for the zone root or a full name such as www.example.com. Use Punycode for international domain names.
• Edit: choose Edit beside a record, change the intended fields, and enter a reason. MP preserves existing comments, tags, and advanced settings. Changing the record type requires a separate removal and addition.
• Remove: enter a reason in the form, then choose Preview removal beside the record.

The editor supports A, AAAA, CNAME, MX, TXT, NS, CAA, and SRV. Other record types remain visible and can be reviewed for removal; edit their specialized fields in Cloudflare. Records managed by another Cloudflare service may need to be changed in that service.

TTL is the cache lifetime in seconds: use 1 for Automatic, or 60–86400. A, AAAA, and CNAME can be proxied; proxied records use Automatic TTL. TXT accepts plain text or complete quoted DNS strings. MX needs a priority; CAA and SRV show their own fields.

3. Review and confirm

1. Choose Preview change or Preview removal. Check the connection, zone, reason, and before/after values.
2. Type the exact zone name into the confirmation field.
3. Choose Confirm and apply DNS change and accept the final confirmation.

Previews expire after ten minutes. Editing the form after a preview does not change the saved proposal; prepare a new preview for different values. MP rechecks the zone and existing record before applying. If either changed, refresh and review a new proposal.

If the page says DNS writes are disabled, you can still view records and prepare previews. Contact MetricPoints about write availability. The connection's manual IP security setting does not enable DNS writes.

4. Verify and retain the evidence

Open DNS change history to see the requester, time, reason, requested values, and outcome. Success means Cloudflare's record state was read back and matched the request. It does not mean every cached resolver has updated or that the website has recovered. Review fresh site checks separately.

• Conflict: the record, connection, or preview changed. No write was sent for that proposal. Refresh and start a new review.
• Failed: Cloudflare rejected the request. Check the token's DNS Edit permission and record values before preparing another action.
• Unknown or applying: the outcome is unconfirmed. Do not submit the same change again blindly. Further writes in this team's zone are paused.

For an unconfirmed action with a record ID, choose Verify provider state (read only) using the original connection. If an addition timed out without returning an ID, inspect the records in Cloudflare. Use Record manual review to explain what you found and release the hold. This records your review; it does not mark the original write as verified.

History includes MP-initiated actions, not every change made elsewhere in Cloudflare. Reversing an action requires a new preview and confirmation. MP does not automatically change a DNS monitoring baseline after an edit.