domains
PUT /v1/domains/{domainId}/dns/records/{recordId}
Update a DNS record.
Kimlik Doğrulama
Bearer token olarak bir API anahtarı gönderin. Anahtar domains.dns.manage iznine sahip olmalıdır; bu izne sahip olmayan bir anahtar 404 ile değil, 403 ile reddedilir.
Bu uç nokta hiçbir organizasyon kimliği almaz. Anahtarınız zaten ait olduğu organizasyonu tanımlar ve yanıt bu organizasyonla sınırlandırılır.
Dene
Köşeli parantez içindeki her şeyi kendi değerlerinizle ve anahtar yer tutucusunu panonuzdan bir anahtarla değiştirin.
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> }'Oturum açtınız mı? Panonuzdaki API konsolu, gerçek organizasyon kimliğinizi ve kendi anahtarınızı otomatik olarak doldurur ve isteği canlı API üzerinde çalıştırarak gerçek yanıtı görmenizi sağlar. Bu uç noktayı API konsolunda açın
Ayrıntılar
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.
Parametreler
| Ad | Tür | Zorunlu | Ne olduğu |
|---|---|---|---|
domainId (path) | Uuid | Evet | The domain's id. |
recordId (path) | string | Evet | The DNS record's provider id. |
confirm_mail_change (query) | boolean | Hayır | 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… |
İstek gövdesi
| Ad | Tür | Zorunlu | Ne olduğu |
|---|---|---|---|
name | string | Evet | The record name — `@`/empty for the apex, or a relative/absolute host. |
type | DnsRecordType | Evet | A DNS resource-record type the shared editor supports (docs/31 §5.2). |
value | string | Evet | — |
ttl | integer | Hayır | — |
priority | object | Hayır | — |
proxied | object | Hayır | 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… |
Yanıt
| Ad | Tür | Zorunlu | Ne olduğu |
|---|---|---|---|
id | string | Evet | The provider-assigned record id. |
name | string | Evet | The record name — `@` for the apex, or a relative/absolute host. |
type | DnsRecordType | Evet | A DNS resource-record type the shared editor supports (docs/31 §5.2). |
value | string | Evet | The record value (target/content). |
ttl | integer | Evet | Time-to-live in seconds. |
priority | object | Hayır | Priority for MX/SRV records; null otherwise. |
proxied | object | Hayır | 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 | Evet | 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 | Hayır | 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… |
Bu uç noktanın dönderebileceği hatalar
401 · 403 · 404 · 409 · 422 · 429 · 502 · 503