List accepted nameserver sets

GET

/domains/ns-sets

const url = 'https://api.nsin.ir/domains/ns-sets';
const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request GET \
  --url https://api.nsin.ir/domains/ns-sets \
  --header 'Authorization: Bearer <token>'

The nameserver sets a managed domain may be delegated to. The sets are parallel: each names the same NSIN nameserver nodes under a different hostname family. A delegation is accepted when it names every node — through any of that node’s hostnames, so families may be mixed — and nothing that is not an NSIN nameserver. Naming one node twice (in two families) does not count for the missing one, and any third-party nameserver fails the check outright. The first set is the one shown in the panel and is the recommended choice.

Once the delegation passes, the zone’s own apex NS records are rewritten to match the names you actually delegated to.

Authorizations

bearerAuth
apiKeyAuth

Responses

200

Accepted nameserver sets.

application/json

object

sets

Each entry is one complete, acceptable nameserver set.

Array<Array<string>>

Example

{
  "sets": [
    [
      "th.ns.nsin.ir",
      "ny.ns.nsin.ir",
      "eu.ns.nsin.ir"
    ]
  ]
}

401

Missing, malformed, revoked or expired API key. (A valid key whose account has been deactivated gets 403 account is inactive instead.)

application/json

The single error shape used by every endpoint.

object

error

required

Human-readable description of what went wrong.

string

Examples

invalidKey

{
  "error": "invalid API key"
}

429

The key exceeded its request budget (300 requests per minute by default).

application/json

The single error shape used by every endpoint.

object

error

required

Human-readable description of what went wrong.

string

Examples

limited

{
  "error": "rate limit exceeded"
}