WAPI – NSSET

Na tej straninsset-checknsset-infonsset-creatensset-updatensset-transfernsset-send-auth-info

This article deals with WAPI commands specifically for the WEDOS DNS (NSSET) service. For information on how to set up WAPI and troubleshoot common issues, see the article WAPI – Manual.

This tutorial deals with WAPI commands for NSSET, which is only used by CZ domains. You can find instructions for DNS in the article WAPI – DNS.

This article provides information on the following requests:


nsset-check

Use the nsset-check request to check whether the NSSET name is free for registration, or is in some other state.

Parameters

  • tld – domain TLD
  • name – NSSET name

Return Values

  • 1000 = NSSET je na voljo za registracijo
  • 2201 = neveljaven TLD
  • 2247 = nepodprta oblika NSSET
  • 3242 = NSSET ni na voljo
  • 3245 = NSSET je že registriran
  • 3246 = ni na voljo
  • 3247 = ni na voljo
  • 3248 = ni na voljo – karantena
  • 3249 = ni na voljo – rezervirano
  • 3250 = ni na voljo – blokirano
  • 3251 = že registrirano (pri nas)
  • 4218 = pošiljanje ni uspelo – napaka pri komunikaciji

Return Data

The request returns no data.

Templates

JSON request:

{
"request": {
"user": "your@login.tld",
"auth": "authentication string",
"command": "nsset-check",
"clTRID": "your ID",
"data": {
"tld": "cz",
"name": "NSSET name"
}
}
}

JSON response (OK):

{
  "response": {
    "code": 1000,
    "result": "OK",
    "timestamp": "UTF timestamp",
    "clTRID": "your ID",
    "svTRID": "server ID",
    "command": "nsset-check"
  }
}

nsset-info

Use the nsset-info request to download information about an NSSET.

Parameters

  • tld – TLD
  • name – NSSET name

Return Values

  • 1000 OK
  • 2201 = neveljaven TLD
  • 2209 = napaka v skladnji
  • 2247 = nepodprta oblika NSSET
  • 3214 = napaka – NSSET ni naložen
  • 3242 = NSSET ni na voljo
  • 4204 = napaka povezave, poskusite znova pozneje

Return Data

If successful, the request returns an nsset element in the data node with the following entries:

  • name – NSSET name
  • status – status
  • reg_owner – current registrar
  • reg_creator – NSSET creator (registrar)
  • reg_update – registrar who made last update
  • created_date – date of creation
  • updated_date – date of last update
  • transfer_date – date of transfer to another registrar
  • tech_c – NSSET technical contact
  • dns – DNS server list
  • server
    • name – server name
    • addr_ipv4 – IPv4 server address
    • addr_ipv6 – IPv6 server address

Templates

JSON request:

{
"request": {
"user": "your@login.tld",
"auth": "authentication string",
"command": "nsset-info",
"clTRID": "your ID",
"data": {
"tld": "cz",
"name": "NSSET name"
}
}
}

JSON response (OK):

{
  "response": {
    "code": 1000,
    "result": "OK",
    "timestamp": "UTF timestamp",
    "clTRID": "your ID",
    "svTRID": "server ID",
    "command": "nsset-info",
    "data": {
      "nsset": {
        "name": "NSSET name",
        "status": "status",
        "reg_owner": "current registrar",
        "reg_creator": "NSSET creator (registrar)",
        "reg_update": "last update registrar",
        "created_date": "date and time of creation",
        "updated_date": "date and time of last update",
        "transfer_date": "date and time of last transfer",
        "tech_c": "technical contact ID",
        "dns": {
          "server1": {
            "name": "DNS server name",
            "addr_ipv4": "DNS server IPv4",
            "addr_ipv6": "DNS server IPv6"
          }
        }
      }
    }
  }
}

nsset-create

Use the nsset-create request to create a new NSSET. NSSET contains a list of NS servers, each server contains a name entry and possibly also its IP address. You can also set a technical contact – if you do not, the default (WEDOS) will be set.

Parameters

  • tld – TLD
  • name – NSSET name
  • dns – list of ns servers, each server entry contains information about that ns server
    • server
      • name – name (domain address)
      • addr_ipv4 – IPv4 address
      • addr_ipv6 – IPv6 adsress
  • tech_c – technical contact – optional

Return Values

  • 1000 = V redu, NSSET ustvarjen
  • 2201 = vnesen napačen TLD
  • 2210 = neveljavna oblika strežnikov ns
  • 2211 = preveč strežnikov ns
  • 2216 = neveljavna skladnja v tehničnem kontaktu
  • 2247 = nepodprta oblika NSSET
  • 3228 = ne podpira dela s kontakti
  • 3229 = napaka pri nalaganju kontakta
  • 3242 = NSSET ni na voljo
  • 3244 = Ustvarjanje NSSET ni uspelo
  • 3245 = NSSET je že registriran
  • 3246 = ni na voljo
  • 3247 = ni na voljo
  • 3248 = ni na voljo – karantena
  • 3249 = ni na voljo – rezervirano
  • 3250 = ni na voljo – blokirano
  • 3251 = že registrirano
  • 4212 = napaka povezave
  • 4218 = preverjanje ni uspelo – napaka pri komunikaciji
  • 4219 = ustvarjanje ni uspelo – napaka pri komunikaciji

Return Data

If successful, the command in the data node returns:

  • nsset – the created NSSET name

Templates

JSON request:

{
"request": {
"user": "your@login.tld",
"auth": "authentication string",
"command": "nsset-create",
"clTRID": "your ID",,
"data": {
"tld": "cz",
"name": "NSSET name",
"dns": {
"server1": {
"name": "DNS server name",
"addr_ipv4": "DNS server IPv4 address",
"addr_ipv6": "DNS server IPv6 address"
}
},
"tech_c": "technical contact ID"
}
}
}

JSON response (OK):

{
  "response": {
    "code": 1000,
    "result": "OK",
    "timestamp": "UTF timestamp",
    "clTRID": "your ID",
    "svTRID": "server ID",
    "command": "nsset-create",
    "data": {
      "nsset": "NSSET name"
    }
  }
}

nsset-update

Use the nsset-update request to modify an existing NSSET. The old entry will be completely overwritten, so enter all data carefully.

Parameters

  • tld – TLD – required
  • auth_info – NSSET AUTH-ID – required
  • name – NSSET name – required
  • dns – list of ns servers, each server entry contains information about that ns server – required
    • server – at least 2 required
      • name – server domain name – required
      • addr_ipv4 – IPv4 address – optional
      • addr_ipv6 – IPv6 address – optional
  • tech_c – technical contact ID – required

Return Values

  • 1000 = V redu, NSSET spremenjen
  • 2201 = vnesen napačen TLD
  • 2209 = napaka v skladnji
  • 2210 = neveljavna oblika seznama strežnikov DNS
  • 2211 = preveč strežnikov DNS
  • 2216 = neveljavna skladnja v kontaktu
  • 2247 = neveljaven NSSET
  • 3214 = napaka – NSSET ni naložen
  • 3228 = ne podpira dela s kontakti
  • 3229 = napaka pri nalaganju kontakta
  • 3242 = NSSET za to domeno ni podprt
  • 3252 = napaka pri avtorizaciji
  • 3254 = Sprememba NSSET ni uspela nsset
  • 4204 = NSSET ni na voljo – napaka povezave
  • 4220 = Sprememba NSSET ni uspela – napaka povezave
  • 4212 = kontakt ni na voljo – napaka povezave

Return Data

The request returns no data.

Templates

JSON request:

{
"request": {
"user": "your@login.tld",
"auth": "authentication string",
"command": "nsset-update",
"clTRID": "your ID",
"data": {
"tld": "cz",
"name": "NSSET name",
"auth_info": "NSSET AUTH-ID",
"dns": {
"server1": {
"name": "DNS server name"
},
"server2": {
"name": "DNS server name"
}
},
"tech_c": "technical contact ID"
}
}
}

JSON response (OK):

{
  "response": {
    "code": 1000,
    "result": "OK",
    "timestamp": "UTF timestamp",
    "clTRID": "your ID",
    "svTRID": "server ID",
    "command": "nsset-update"
  }
}

nsset-transfer

The nsset-transfer request changes the NSSET registrar to WEDOS.

Parameters

  • tld – TLD
  • name – NSSET name
  • auth_info – NSSET AUTH-ID

Return Values

  • 1000 OK
  • 2100 = manjka obvezni parameter
  • 2101 = neveljavni vhodni parametri
  • 2201 = nepodprt TLD
  • 2209 = napaka v skladnji
  • 2215 = manjka auth_info
  • 2247 = neveljavno ime NSSET
  • 2249 = Prenos NSSET za ta TLD ni dovoljen
  • 3214 = napaka – NSSET ni naložen
  • 3242 = NSSET ni podprt
  • 3251 = NSSET je pri tem registrarju že registriran
  • 3255 = napaka pri avtorizaciji
  • 3256 Prenos NSSET ni uspel
  • 4204 = NSSET ni bil naložen – napaka povezave
  • 4221 = Prenos NSSET ni uspel – napaka povezave

Return Data

The request returns no data.

Templates

JSON command:

{
  "request": {
    "user": "your@login.tld",
    "auth": "authentication string",
    "command": "nsset-transfer",
    "clTRID": "your ID",
    "data": {
      "tld": "cz",
      "name": "NSSET name",
      "auth_info": "NSSET AUTH-ID"
    }
  }
}

JSON response (OK):

{
  "response": {
    "code": 1000,
    "result": "OK",
    "timestamp": "UTF timestamp",
    "clTRID": "your ID",
    "svTRID": "server ID",
    "command": "nsset-transfer"
  }
}

nsset-send-auth-info

The nsset-send-auth-info request sends the NSSET AUTH-ID to the NSSET technical contact email.

Parameters

  • tld – TLD
  • name – NSSET name

Return Values

  • 1000 = V redu, auth_info poslan na e-naslov kontakta
  • 2201 = nepodprt TLD
  • 2209 = Sintaksna napaka v NSSET
  • 2216 = sintaksna napaka v kontaktu
  • 2243 = za ta NSSET pošiljanje avtorizacijske kode ni dovoljeno
  • 2247 = nepodprta oblika NSSET
  • 3214 = napaka – branje NSSET ni uspelo
  • 3217 = pošiljanje avtorizacijske kode ni uspelo
  • 3228 = ne podpira dela s kontakti
  • 3229 = branje kontakta ni uspelo
  • 3242 NSSET ni na voljo
  • 3257 = pošiljanje ni uspelo, NSSET ni na voljo
  • 4204 = NSSET ni na voljo – povezava ni uspela
  • 4212 = kontakt ni na voljo – povezava ni uspela
  • 4222 = pošiljanje ni uspelo – povezava ni uspela

Return Data

The request returns no data.

Templates

JSON request:

{
  "request": {
    "user": "your@login.tld",
    "auth": "authentication string",
    "command": "nsset-send-auth-info",
    "clTRID": "your ID",
    "data": {
      "tld": "cz",
      "name": "NSSET name"
    }
  }
}

JSON response (OK):

{
  "response": {
    "code": 1000,
    "result": "OK",
    "timestamp": "UTF timestamp",
    "clTRID": "your ID",
    "svTRID": "server ID",
    "command": "nsset-send-auth-info"
  }
}

Ali vam je bil ta članek v pomoč?

Vaše mnenje nam pomaga izboljšati naše članke.

Vaše sporočilo prejme ekipa za dokumentacijo, ki nanj ne odgovarja. Če potrebujete pomoč, nas kontaktirajte prek kontaktnega obrazca. Ne vpisujte gesel ali osebnih podatkov.

Didn’t find what you were looking for?

Send us your question using the contact form.