Understanding How The API Works »
Deactivating a secondary zone using 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 |
Secondary/ PUT — Deactivates the secondary zone specified.
HTTP Action — PUT
URI — https://api.dynect.net/REST/Secondary/<zone>/
|
Arguments:
boolean deactivate — Required. Indicates the secondary zone specified should be deactivated.
|
Response — Click for More Info
- integer
task_id – The number assigned to the task to deactivate a secondary zone.
- string
active — State of the secondary service.
Valid values:
Y = active
N = inactive
- string
contact_nickname — Contact that receives notifications for this zone.
- array
masters — A list of IPv4 or IPv6 addresses of the master nameservers for this zone.
- string
tsig_key_name — Name of the TSIG key that will be used to sign transfer requests to your zone’s master.
- string
zone — Name of the zone.
|
SOAP Syntax
Click to view all SOAP Commands |
DeactivateSecondary — Deactivates the secondary zone specified.
|
Arguments:
string token — Required. The session identifier.
string zone — Required. Name of zone to update.
|
Response — Click for More Info
- integer
task_id – The number assigned to the task to deactivate a secondary zone.
- hash
data
- string
active — State of the secondary service.
Valid values:
Y = active
N = inactive
- string
contact_nickname — Contact that receives notifications for this zone.
- array
masters — A list of IPv4 or IPv6 addresses of the master nameservers for this zone.
- string
tsig_key_name — Name of the TSIG key that will be used to sign transfer requests to your zone’s master.
- string
zone — Name of the zone.
|
Example Request — Click for More Info
{
'token' => 'asdlkfjasl23j4879afa',
'zone' => 'example.com',
}
|
DNS API Knowledge Base