DELETE /v1/domains/{domainId}/dns/records/{recordId}

Uthibitishaji

Tuma ufunguo wa API kama tokeni ya kubeba. Ufunguo lazima uwe na ruhusa ya domains.dns.manage; ufunguo usio nayo unakataliwa kwa 403, si 404.

Endpoint hii haichukui kitambulisho cha shirika. Ufunguo wako tayari unalitambua shirika linalohusika, na jibu limewekewa kikomo kwa shirika hilo pekee.

Jaribu

Badilisha chochote kilicho ndani ya mabano ya pembe na maadili yako mwenyewe, na kishikiliaji cha ufunguo na ufunguo kutoka kwa dashibodi yako.

curl -X DELETE https://api.zinndigital.com/v1/domains/{domainId}/dns/records/{recordId} \
  -H "Authorization: Bearer zdk_live_…"

Umeingia kwenye akaunti? Dashibodi yako ya kiweko cha API inajaza kitambulisho chako halisi cha shirika na ufunguo wako mwenyewe, na kuendesha ombi dhidi ya API ya moja kwa moja ili uweze kuona jibu halisi. Fungua sehemu hii ya mwisho (endpoint) kwenye konsole ya API

Maelezo

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.

Vigezo

Hitilafu ambazo mwisho huu unaweza kurudisha

401 · 403 · 404 · 409 · 429 · 502 · 503