domains

PUT /v1/domains/{domainId}/glue

Create or replace the glue record for one nameserver inside this domain.

All domains endpoints

All developer docs →

Authentication

Send an API key as a bearer token. The key must carry the domains.dns.manage permission; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X PUT https://api.zinndigital.com/v1/domains/{domainId}/glue \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "host": <string> }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Requires domains.dns.manage. host must be strictly inside the domain (e.g. ns1.example.com for example.com); at least one of ipv4/ipv6, each a public unicast address (private, loopback, link-local, reserved, documentation and multicast addresses are refused with 422). Answers with the record as READ BACK from the registry. Audit-logged (domain.glue.set).

Parameters

NameTypeRequiredWhat it is
domainId (path)UuidYesThe domain's id.

Request body

NameTypeRequiredWhat it is
hoststringYes—
ipv4objectNoA public IPv4 address.
ipv6objectNoA public IPv6 address.
registryGlueRegistryStateNo—

Response

NameTypeRequiredWhat it is
hoststringYes—
ipv4objectNoA public IPv4 address.
ipv6objectNoA public IPv6 address.
registryGlueRegistryStateNo—

Errors this endpoint can return

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