Understanding How The API Works »
Creating a Transactional Signature Key (TSIGKey) in the API requires specific syntax depending on whether you are using REST or SOAP. Use this table to find the syntax for your command.
REST Syntax
| Click to view all REST Resources |
| TSIGKey/ POST — Creates a new TSIG Key.
HTTP Action — POST
URI — https://api.dynect.net/REST/TSIGKey/<name>/ |
Arguments:
- string
secret — Required. The key to be used.
- string
algorithm — Required. The encryption algorithm used in DNS transactions.
Valid Values:
hmac-md5
hmac-sha1
hmac-sha224
hmac-sha256
hmac-sha384
hmac-sha512
|
Response:
- string
name — Update the name for the specified TSIG Key.
- string
secret — The key to be used.
- string
algorithm — The encryption algorithm used in DNS transactions.
|
SOAP Syntax
| Click to view all SOAP Commands |
| CreateTSIGKey — Creates a new TSIG Key. |
Arguments:
- string
name — Required. Name of the TSIG Key.
- string
secret — Required. The actual key to use.
- string
algorithm — Required. The encryption algorithm used in DNS transactions.
Valid Values:
hmac-md5
hmac-sha1
hmac-sha224
hmac-sha256
hmac-sha384
hmac-sha512
- string
token — Required. The session identifier.
|
Response:
- hash
data
- string
name — Name of the TSIG Key.
- string
secret — The actual key.
- string
algorithm — The encryption algorithm used in DNS transactions.
|
Example Request — Click for More Info
{
'name' => 'Example TSIG Key',
'secret'=> '0jnu7SdsMvzzlmTDPYRceA==',
'algorithm'=> 'hmac-sha384',
'token' => 'asdlj34ot879834cdzjklfK',
}
|
DNS API Knowledge Base
