Understanding How The API Works »
Creating a new Response Pool 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.
NOTE: Total number of records in a single Response Pool may not be more than 255.
WARNING: Dyn recommends setting an explicit fallback record entry in all Traffic Director services to ensure a query is always answered with a record. See TD Best Practices – Fallback Entry for more information on setting up a fall back entry.
REST Syntax
Click to view all REST Resources |
/REST/DSFResponsePool/ POST — Create a new Response Pool.
HTTP Action — POST
URIs — https://api.dynect.net/REST/DSFResponsePool/<service_id>/
|
Arguments — Click for More Info
- string
label — Required. A label for the Response Pool.
Click for Response Pool Fields.
- string
core_set_count — If fewer than this number of core record sets are eligible, status will be set to fail. Defaults to 0.
- string
eligible — Indicates whether or not the Response Pool can be served.
Valid values:
false — When automation is set to manual, sets the serve_mode field to ‘Do Not Serve’.
true — Default. When automation is set to manual, Response Pool can be served.
NOTE: When automation is set to manual, eligible must be set to false.
- string
automation — Defines how eligible can be changed in response to monitoring.
Valid values:
auto — Sets the serve_mode field to ‘Monitor & Obey’. Default.
auto_down — Sets the serve_mode field to ‘Monitor & Remove’.
manual — Couples with eligible value to determine other serve_mode field values.
- string
publish — Indicates whether or not the changes will be published immediately.
Y — Service will be published on creation.
N — Service will be published when zone changes are published.
- string
notes — A custom note field. All content in the string is added to the Zone Notes for the zones attached to this service when the zone is published. Only used when publish = Y
- string
dsf_ruleset_id — ID of the Ruleset to join.
- string
index — When specified with dsf_ruleset_id , indicates the position of the Response Pool.
NOTE: DSF Response Pool will be placed at the end of the chain if the dsf_ruleset_id is provided but the index is not.
- array
rs_chains — A list of Record Set Failover Chains that are defined for this Response Pool.
|
Response — Click for More Info
- string
service_id — Identifier for the Traffic Director (DSF) Service.
- string
dsf_response_pool_id — Identifier for the Response Pool.
Click for Response Pool fields
- string
label — A label for the Response Pool.
- string
automation — Defines how eligible can be changed in response to monitoring.
Valid values:
auto — Sets the serve_mode field to ‘Monitor & Obey’. Default.
auto_down — Sets the serve_mode field to ‘Monitor & Remove’.
manual — Couples with eligible value to determine other serve_mode field values.
- string
core_set_count — If fewer than this number of core record sets are eligible, status will be set to fail.
- string
eligible — Indicates whether or not the Response Pool can be served.
Valid values:
false — When automation is set to manual, sets the serve_mode field to ‘Do Not Serve’.
true — Default. When automation is set to manual, Response Pool can be served.
NOTE: When automation is set to manual, eligible must be set to false.
- string
pending_change — Indicates whether or not the response has any changes pending.
- array
rs_chains — A list of Record Set Failover Chains that are defined for this Response Pool.
- string
status — The status of the pool indicated by any attached monitors.
Valid values:
ok — The object is available (up).
unknown — The object has not provided a status to the monitor.
down — Response Pool unable to satisfy core sets, Ineligible due to previous failure, or End of failover for Record Set.
- string
response_time — Time it took to receive a response from the endpoints.
- string
torpidity — Performance indicator for the Record. Lower is better.
- string
last_monitored — Epoch timestamp of the last time the Record Set was monitored.
- string
pending_change — Indicates whether or not the object will be added, updated, or deleted.
string status — The status of the pool indicated by any attached monitors.
Valid values:
ok — The object is available (up).
unknown — The object has not provided a status to the monitor.
down — Response Pool unable to satisfy core sets, Ineligible due to previous failure, or End of failover for Record Set.
string last_monitored — Epoch timestamp of the last time the Record Set was monitored.
string pending_change — Indicates whether or not the response has any changes pending.
array rulesets — A list of Rulesets that contain this Response Pool.
string status — The status of the pool indicated by any attached monitors.
Valid values:
ok — The object is available (up).
unknown — The object has not provided a status to the monitor.
down — Response Pool unable to satisfy core sets, Ineligible due to previous failure, or End of failover for Record Set.
string last_monitored — Epoch timestamp of the last time the Response Pool was monitored.
|
SOAP Syntax
Click to view all SOAP Commands |
CreateDSFResponsePool — Creates a new Response Pool.
|
Arguments — Click for More Info
- string
service_id — Identifier for the Traffic Director (DSF) service where the Record Set Failover Chain belongs.
- string
label — Required. A label for the Response Pool.
Click for Response Pool fields.
- string
core_set_count — If fewer than this number of core record sets are eligible, status will be set to fail. Defaults to 0.
- string
publish — Indicates whether or not the changes will be published immediately.
Y — Service will be published on creation.
N — Service will be published when zone changes are published.
- string
notes — A custom note field. All content in the string is added to the Zone Notes for the zones attached to this service when the zone is published. Only used when publish = Y
- string
eligible — Indicates whether or not the Response Pool can be served.
Valid values:
false — When automation is set to manual, sets the serve_mode field to ‘Do Not Serve’.
true — Default. When automation is set to manual, Response Pool can be served.
NOTE: When automation is set to manual, eligible must be set to false.
- string
automation — Defines how eligible can be changed in response to monitoring.
Valid values:
auto — Sets the serve_mode field to ‘Monitor & Obey’. Default.
auto_down — Sets the serve_mode field to ‘Monitor & Remove’.
manual — Couples with eligible value to determine other serve_mode field values.
- string
dsf_ruleset_id — ID of the Ruleset to join.
- string
index — When specified with dsf_ruleset_id , indicates the position of the Response Pool.
NOTE: Response Pool will be placed at the end of the chain if the dsf_ruleset_id is provided but the index is not.
- array
rs_chains — A list of Record Set Failover Chains that are defined for this Response Pool.
- string
token — Required. The session identifier.
|
Response — Click for More Info
string pending_change — Indicates whether or not the response has any changes pending.
array rulesets — A list of Rulesets that contain this Response Pool
string status — The status of the pool indicated by any attached monitors
string last_monitored — Epoch timestamp of the last time the Response Pool was monitored
|
Example Request — Click for More Info
{
'service_id' => 'fv298...', # ID shortened...
'label' => 'Response Pool Example',
'core_set_count' => '1',
'dsf_ruleset_id' => '4ae3n...', # ID shortened...
'index' => '2',
'rs_chains' => [{
'label' => 'Example Record Set Failover Chain',
'core' => 'true',
'record_sets' => [{
'label' => 'US East - AAAA',
'rdata_class' => 'AAAA',
'ttl' => '3600',
'records' => [{
'label' => 'USEast007',
'weight' => '5',
'automation' => 'auto',
'endpoints' => ['127.1.5.1','176.2.66.7'],
'endpoint_up_count' => '1',
'master_line' => '2001:0db8:85a3:0000:0000:8a2e:0370:7334',
}],
},{
'dsf_record_set_id' => '0bi5k...', # ID shortened...,
},{
'failover' => 'failover.com',
}],}
],
'token' => 'asdlj34ot879834cdzjklfK'
}
|
<< DNS API Knowledge Base