hosting
POST /v1/sites/{siteId}/edge-domains/{hostname}/dns
Publish this domain's DNS records for the customer.
身份验证
请将 API 密钥作为 bearer 令牌发送。该密钥必须具有 hosting.deploy.manage 权限；缺少该权限的密钥将被拒绝并返回 403 状态码，而非 404。
此端点不需要组织 ID。您的密钥已用于识别其所属的组织，且响应范围也仅限于该组织。
免费试用
将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。
curl -X POST https://api.zinndigital.com/v1/sites/{siteId}/edge-domains/{hostname}/dns \
-H "Authorization: Bearer zdk_live_…"已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。 在 API 控制台中打开此端点
详细信息
Writes the records and then resolves them, so the answer is what the internet says rather than what we did. Three tiers in order — the customer's own connected DNS provider, then our nameservers with the zone pre-built, then the records to publish by hand — and the tier that was actually used comes back as `mode`. In `nameservers` mode the `nameservers` array is the one thing left for the customer to do. Requires `hosting.deploy.manage`.
参数
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
siteId (path) | Uuid | 是 | Site ID (UUIDv7). |
hostname (path) | string | 是 | The bound hostname, lower-cased and without a trailing dot. |
响应
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
hostname | string | 是 | — |
mode | string<unknown, our_zone, byo_dns, nameservers, manual> | 是 | — |
zone | string | 是 | — |
vendor | string | 是 | — |
detail | string | 是 | — |
nameservers | string[] | 是 | Populated only in `nameservers` mode — the zone is built and the records are in it, and setting these at the registrar is the one thing left to do. |
records | DnsRecordPlan[] | 是 | — |
checks | DnsRecordCheck[] | 是 | — |
resolves | boolean | 是 | — |
此端点可能返回的错误
401 · 403 · 404 · 422 · 429