domains

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

Update a DNS record.

Санҷиши ҳаққоният

Kaliti API-ро ҳамчун рамзи доранда (bearer token) фиристед. Калит бояд дорои иҷозати domains.dns.manage бошад; калиди бидуни он бо хатои 403 рад карда мешавад, на 404.

Ин нуқтаи поёнӣ ягон рақами мушаххаси созмонро талаб намекунад. Калиди шумо аллакай созмонеро, ки ба он тааллуқ дорад, муайян мекунад ва ҷавоб ба он маҳдуд карда мешавад.

Санҷидан

Ҳар чизро дар қаavски кунҷӣ бо қиматҳои худ ва ҷойи нигоҳдорандаи калидро бо калима аз панели идоракунии худ иваз кунед.

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> }'

Воarid шудаед? Консоли API дар панели идоракунии шумо рақами мушаххаси ташкилоти воқеӣ ва калиди худро пур мекунад ва дархостро бар зидди API-и фаъол иҷро мекунад, то шумо посухи воқеиро бубинед. Ин нуқтаи ниҳоиро дар консоли API кушоед

Тафсилот

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.

Параметрҳо

Ном	Намуд	Талаб карда мешавад	Ин чӣ аст
`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…

Ҷисми дархост

Ном	Намуд	Талаб карда мешавад	Ин чӣ аст
`name`	`string`	Бале	The record name — `@`/empty for the apex, or a relative/absolute host.
`type`	`DnsRecordType`	Бале	A DNS resource-record type the shared editor supports (docs/31 §5.2).
`value`	`string`	Бале	—
`ttl`	`integer`	Не	—
`priority`	`object`	Не	—
`proxied`	`object`	Не	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…

Ҷавоб

Ном	Намуд	Талаб карда мешавад	Ин чӣ аст
`id`	`string`	Бале	The provider-assigned record id.
`name`	`string`	Бале	The record name — `@` for the apex, or a relative/absolute host.
`type`	`DnsRecordType`	Бале	A DNS resource-record type the shared editor supports (docs/31 §5.2).
`value`	`string`	Бале	The record value (target/content).
`ttl`	`integer`	Бале	Time-to-live in seconds.
`priority`	`object`	Не	Priority for MX/SRV records; null otherwise.
`proxied`	`object`	Не	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`	Бале	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`	Не	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…

Хатоҳое, ки ин нуқтаи ниҳоӣ метавонад баргардонад

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

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