# Delete a DNS record by ID > DELETE /api/services/cloudflare/zones/{zoneId}/dns/{recordId} on the Vigilbase One API. Source: https://docs.vigilbase.com/one/api/reference/services/delete-services-cloudflare-zones-zone-id-dns-record-id `DELETE https://one.vigilbase.com/api/services/cloudflare/zones/{zoneId}/dns/{recordId}` > Needs a recent sign-in: renewing a token doesn't count, and MCP sessions and API keys are always refused. See [changes that need a recent sign-in](https://docs.vigilbase.com/one/api#changes-that-need-a-recent-sign-in). ## Authorizations - `Authorization` (string, header, required): Bearer access token from Vigilbase Identity (`auth.vigilbase.com`), sent as `Authorization: Bearer `. The CLI gets one with `vigilbase login`. Organisation API keys can't call this endpoint: it needs a recent sign-in by a person. - Permissions checked: `write:services` ## Path parameters - `zoneId` (string, required) - `recordId` (string, required) ## Responses ### 200 Success ### 401 Authentication required ### 403 Not permitted ## Example request ```bash # Token from `vigilbase login`. API keys can't call this. curl --request DELETE \ --url 'https://one.vigilbase.com/api/services/cloudflare/zones/{zoneId}/dns/{recordId}' \ --header "Authorization: Bearer $VIGILBASE_TOKEN" ```