DNS automation
v1.10.0
Change nameserver delegation (vanity sets or back to regfish)
Delegates the domain to one of the account's vanity nameserver sets (
vanity_set_id), or moves it to the regfish standard nameservers (vanity_set_id: null). Free-form nameservers are intentionally NOT supported on this endpoint; a delegation to external nameservers must be set up in the regfish dash. vanity_set_id: null works from every starting point: - From a vanity set: always possible, the hosted zone stays as it is. - From external nameservers: possible when the TLD charges no fee for a nameserver change. If regfish holds no DNS zone for the domain yet, it is created with the regfish NS records only; create your records right away (POST /dns/rr), they are served as soon as the registry has switched the delegation. A TLD that charges for the change answers 409 with a link to the regfish dash, where the fee is shown and confirmed; the API never bills it. An active or changing DNSSEC setup also answers 409: disable DNSSEC first. - Already on the regfish nameservers: idempotent; a missing zone is created, nothing is sent to the registry. Guarded by the Domain-Guardian (ns_change rule class), domain status checks (pending transfer, cancellation) and two daily change limits: 5 changes per domain and 50 changes per account, both counted across all of your API keys and OAuth clients. Issuing another credential does not raise either limit.PUT
/domains/{domain}/nameservers
Domains
Authentication
Parameters
Name
Type
Format
Required
Description
domain
string
-
Required
Fully Qualified Domain Name.
Request body
No description was provided in the specification.
nameserversUpdateRequestnameserversUpdateRequest
{
"vanity_set_id": 1
}Fields
Name
Type
Format
Required
Description
vanity_set_id
integer
-
Required
Id of one of the account's vanity nameserver sets, or `null` to move the domain to the regfish standard nameservers (also from external nameservers, see the endpoint description). Free-form nameservers are not supported on this endpoint.
Request example
PUT
curl --request PUT \
--url 'https://api.regfish.com/domains/www.example.com/nameservers' \
--header 'x-api-key: YOUR_API_KEY' \
--header 'content-type: application/json' \
--data '{
"vanity_set_id": 1
}'Responses
200
Delegation after the change
Response example 200
{
"success": true,
"code": 0,
"response": {
"domain": "example",
"mode": "standard",
"current": [
"example"
],
"vanity_set_id": 1,
"vanity_sets": [
{
"id": 1,
"host": "example",
"nameservers": [
null
]
}
]
}
}401
Unauthorized
Response example 401
{
"success": false,
"message": "Unauthorized",
"error": "Unauthorized"
}403
Blocked by the Domain-Guardian
Response example 403
{
"success": false,
"message": "Blocked by the Domain-Guardian",
"error": "Blocked by the Domain-Guardian"
}404
Domain or vanity set not found
Response example 404
{
"success": false,
"message": "Domain or vanity set not found",
"error": "Domain or vanity set not found"
}409
Domain state or plan does not allow the change
Response example 409
{
"success": false,
"message": "Domain state or plan does not allow the change",
"error": "Domain state or plan does not allow the change"
}429
Daily change limit reached
Response example 429
{
"success": false,
"message": "Daily change limit reached",
"error": "Daily change limit reached"
}500
Unexpected error
Response example 500
{
"success": false,
"message": "Unexpected error",
"error": "Unexpected error"
}Community
Forma parte de la comunidad
La DNS API de regfish es una gran solución para desarrolladores que quieren automatizar dominios y zonas DNS. Súmese a la comunidad y aproveche las ventajas de la automatización DNS. La DNS API está disponible gratis para todos los clientes de regfish.