身份验证
请将 API 密钥作为 bearer 令牌发送。该密钥必须具有 domains.dns.manage 权限；缺少该权限的密钥将被拒绝并返回 403 状态码，而非 404。
此端点不需要组织 ID。您的密钥已用于识别其所属的组织，且响应范围也仅限于该组织。
免费试用
将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。
curl -X DELETE https://api.zinndigital.com/v1/domains/{domainId}/dns/records/{recordId} \
-H "Authorization: Bearer zdk_live_…"已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。 在 API 控制台中打开此端点
详细信息
Removes the record `recordId` from the domain's hosted zone. Requires `domains.dns.manage`. As for update, a record hidden from the caller's line 404s rather than confirming it exists. **Deleting an apex `MX` is refused** `409 MAIL_CHANGE_REFUSED` unless `confirm_mail_change=true` (issue #622). It fires on *any* apex MX deletion, not only the last one — "delete every MX one at a time" is the failure mode, and by the time the last one goes three deletions have already happened. The message says whether the domain would stop receiving mail entirely or merely fall back to a remaining host.
参数
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
domainId (path) | Uuid | 是 | The domain's id. |
recordId (path) | string | 是 | The DNS record's provider id. |
confirm_mail_change (query) | boolean | 否 | Set `true` to proceed with a record change that would move or remove this domain's inbound email (issue #622). Without it, a write that stops mail reaching a host it reaches tod… |
此端点可能返回的错误
401 · 403 · 404 · 409 · 429 · 502 · 503