Understanding How The API Works »
Creating a new Geo Traffic Manager (Classic) service 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.
Please see the list of ISO-3166 two letter codes for the names of countries and their subdivisions or one of the predefined groups for the countries array.
NOTE: The Geo Traffic Management (classic) Service is deprecated. Legacy users of the service should contact Concierge for any questions on adding a Geo Traffic Management (classic) service to your zone. All other users should use Traffic Director instead. |
REST Syntax
Click to view all REST Resources |
/REST/Geo/ POST — Create a new Geo Traffic Manager service on the zone/node indicated.
HTTP Action — POST URI — https://api.dynect.net/REST/Geo/<service_name>/ |
Arguments — Click for More Info
Note: Each element in the following rdata arrays is a hash containing the string elements that follow the rdata array. |
Response — Click for More Info
|
SOAP Syntax
Click to view all SOAP Commands |
CreateGeo — Create a new Geo Traffic Manager service on the zone/node indicated. |
Arguments — Click for More Info
Note: Each element in the following rdata arrays is a hash containing the string elements that follow the rdata array. token — Required. The session identifier. |
Response — Click for More Info
|
Example Request — Click for More Info
{ 'name' => 'example Geo', 'ttl' => '3600', # Default TTL used if a record specific TTL does not exist 'groups' => [{ 'name' => 'simplegroup', 'countries' => ['US'], 'rdata' => { 'a_rdata' => [ { 'address' => '9.9.9.9',}, ], }, 'ttl' => { 'a_ttl' => '900' # Record specific TTL, takes precedence over the service TTL } }], 'nodes' => [{ 'zone' => 'example.com', 'fqdn' => 'admin.example.com', }] 'token' => 'asdlj34ot879834cdzjklfK', } |