domains

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

Update a DNS record.

Lahat ng domains endpoint

Pagpapatotoo

Magpadala ng API key bilang isang bearer token. Kailangang taglayin ng key ang pahintulot na domains.dns.manage; ang key na wala nito ay tatanggihan gamit ang 403, hindi 404.

Ang endpoint na ito ay hindi nangangailangan ng id ng organisasyon. Natutukoy na ng iyong key ang organisasyong kinabibilangan nito, at nakatuon ang tugon dito.

Subukan ito

Palitan ang anuman sa loob ng mga panaklong na may anggulo ng iyong sariling mga halaga, at ang placeholder ng key na may key mula sa iyong dashboard.

curl -X PUT https://api.zinndigital.com/v1/domains/{domainId}/dns/records/{recordId} \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "name": <string>, "type": <DnsRecordType>, "value": <string> }'

Nakalagda? Ang API console sa iyong dashboard ay awtomatikong naglalagay ng iyong tunay na ID ng organisasyon at sariling susi, at pinapatakbo ang kahilingan laban sa live na API upang makita mo ang aktwal na tugon. Buksan ang endpoint na ito sa console ng API

Mga Detalye

Replaces the record `recordId` in the domain's hosted zone. Requires `domains.dns.manage`. A record hidden from the caller's product line (an A/AAAA on the Footprint-Free line) is indistinguishable from an absent one — a 404 — so it cannot be probed by id (register #93). **Repointing a live apex `MX` is refused** `409 MAIL_CHANGE_REFUSED` unless `confirm_mail_change=true` (issue #622) — it silently stops the customer's email reaching the mailboxes it reaches today, which is data loss rather than a configuration change. So is moving the only apex `MX` onto a subdomain: the record survives, the domain's mail does not. A change that alters only TTL or preference is not refused, because mail still arrives at the same host.

Mga Parameter

PangalanUriKailanganAno ito
domainId (path)UuidOoThe domain's id.
recordId (path)stringOoThe DNS record's provider id.
confirm_mail_change (query)booleanHindiSet `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…

Katawan ng kahilingan

PangalanUriKailanganAno ito
namestringOoThe record name — `@`/empty for the apex, or a relative/absolute host.
typeDnsRecordTypeOoA DNS resource-record type the shared editor supports (docs/31 §5.2).
valuestringOo
ttlintegerHindi
priorityobjectHindi
proxiedobjectHindiServe this record through the provider's HTTP proxy — Cloudflare's orange cloud. **`A` and `AAAA` only**; sending it on any other type is a `422` rather than a silent drop, beca…

Tugon

PangalanUriKailanganAno ito
idstringOoThe provider-assigned record id.
namestringOoThe record name — `@` for the apex, or a relative/absolute host.
typeDnsRecordTypeOoA DNS resource-record type the shared editor supports (docs/31 §5.2).
valuestringOoThe record value (target/content).
ttlintegerOoTime-to-live in seconds.
priorityobjectHindiPriority for MX/SRV records; null otherwise.
proxiedobjectHindiWhether this record is served through the provider's HTTP proxy — Cloudflare's **orange cloud**. Applies to `A` and `AAAA`; providers without a proxy ignore it. ⛔⛔ **Three state…
ownerDnsRecordOwnerOoWho may change this record. `platform` means the platform created it and converges it — the A/AAAA record at the apex or `www` that points the domain at the hosting we run for i…
driftDnsRecordDriftHindiWhat the last reconcile found about a **platform-owned** record at the provider, or `null` when the provider agrees with us (the overwhelmingly common case). `changed` — a recor…

Mga error na maibabalik ng endpoint na ito

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