domains

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

Update a DNS record.

Dhammaan domains bixiyayaasha

Xaqiijinta aqoonsiga

U dir furaha API ah calaamad dusha ah (bearer token). Furaha waa inuu wataa ruqadda domains.dns.manage; furaha aan wadan waxaa loo diidayaa 403, ee ma aha 404.

Boggan ma qaato aqoonsiga ururka. Furahaagu wuxuu horay u aqoonsanayaa ururka uu ka tirsan yahay, jawaabtuna waxay ku kooban tahay halkaas.

Isku day

Ku beddel wax kasta oo ku dhex jira qeebaha xaglaha ah qiimayaashaada, sidoo kalena haystaaha furaha ku beddel fure ka dhex muuqda dashboordigaaga.

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

Ma sign-garaysay? Qalabka API ee ku jira dashboard-kaagu wuxuu buuxiyaa aqoonsigaaga ururka ee dhabta ah iyo furahaaga gaarka ah, wuxuuna ku shaqeysiiyaa codsiga API-ga nool si aad u aragto jawaabta dhabta ah. Kani ka fur barta kontoroolka ee API

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.

Cabiraha

MagacaNoocLoo baahan yahayMaxay tahay
domainId (path)UuidHaaThe domain's id.
recordId (path)stringHaaThe DNS record's provider id.
confirm_mail_change (query)booleanMayaSet `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…

Codsiga jidhkiisa

MagacaNoocLoo baahan yahayMaxay tahay
namestringHaaThe record name — `@`/empty for the apex, or a relative/absolute host.
typeDnsRecordTypeHaaA DNS resource-record type the shared editor supports (docs/31 §5.2).
valuestringHaa
ttlintegerMaya
priorityobjectMaya
proxiedobjectMayaServe 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…

Jawaab

MagacaNoocLoo baahan yahayMaxay tahay
idstringHaaThe provider-assigned record id.
namestringHaaThe record name — `@` for the apex, or a relative/absolute host.
typeDnsRecordTypeHaaA DNS resource-record type the shared editor supports (docs/31 §5.2).
valuestringHaaThe record value (target/content).
ttlintegerHaaTime-to-live in seconds.
priorityobjectMayaPriority for MX/SRV records; null otherwise.
proxiedobjectMayaWhether 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…
ownerDnsRecordOwnerHaaWho 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…
driftDnsRecordDriftMayaWhat 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…

Cilladaha ay bartaani soo celin karto

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