Authenticatie
Stuur een API-sleutel mee als bearer token. De sleutel moet over de permissie domains.dns.manage beschikken; een sleutel zonder deze permissie wordt geweigerd met een 403 in plaats van een 404.
Dit eindpunt vereist geen organisatie-id. Uw sleutel identificeert al de organisatie waartoe deze behoort, en het antwoord is hierop afgestemd.
Probeer het
Vervang alles tussen punthaakjes door uw eigen waarden en de sleutelplaatsvervanger door een sleutel uit uw 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> }'Ingelogd? De API-console in je dashboard vult je echte organisatie-id en je eigen sleutel in, en voert het verzoek uit tegen de live API zodat je de daadwerkelijke respons kunt zien. Open dit eindpunt in de API-console
Details
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.
Parameters
| Naam | Type | Verplicht | Wat dit is |
|---|---|---|---|
domainId (path) | Uuid | Ja | The domain's id. |
recordId (path) | string | Ja | The DNS record's provider id. |
confirm_mail_change (query) | boolean | Nee | 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… |
Aanvraaglichaam
| Naam | Type | Verplicht | Wat dit is |
|---|---|---|---|
name | string | Ja | The record name — `@`/empty for the apex, or a relative/absolute host. |
type | DnsRecordType | Ja | A DNS resource-record type the shared editor supports (docs/31 §5.2). |
value | string | Ja | — |
ttl | integer | Nee | — |
priority | object | Nee | — |
proxied | object | Nee | Serve 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… |
Reactie
| Naam | Type | Verplicht | Wat dit is |
|---|---|---|---|
id | string | Ja | The provider-assigned record id. |
name | string | Ja | The record name — `@` for the apex, or a relative/absolute host. |
type | DnsRecordType | Ja | A DNS resource-record type the shared editor supports (docs/31 §5.2). |
value | string | Ja | The record value (target/content). |
ttl | integer | Ja | Time-to-live in seconds. |
priority | object | Nee | Priority for MX/SRV records; null otherwise. |
proxied | object | Nee | Whether 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… |
owner | DnsRecordOwner | Ja | Who 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… |
drift | DnsRecordDrift | Nee | What 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… |
Fouten die dit eindpunt kan retourneren
401 · 403 · 404 · 409 · 422 · 429 · 502 · 503