Updating the Traffic Director (DSF) service instance 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.
Understanding How The API Works »
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/DSF/ PUT — Updates the indicated Traffic Director (DSF) service.
HTTP Action — PUT
URIs — https://api.dynect.net/REST/DSF/<service_id>/ |
Arguments — Click for More Info
- string
label — Name of the Traffic Director (DSF) service.
NOTE: The following special characters are not allowed in the Traffic Director (DSF) Service label field: * < > % /
NOTE: A Traffic Director Service label may not start with a special character (Example: .special_td).
- string
ttl — The default TTL to be used across the service.
- string
publish — If Y, service will be published on creation.
- 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
- array
nodes — A list of zone, FQDN pairs in a hash that are to be linked to the Traffic Director service:
- string
zone — Required. Name of the zone.
- string
fqdn — Required. Fully qualified domain name of a node in the zone.
- array
notifiers — A list of notifiers associated with the Traffic Director service.
- string
notifier_id — ID of the notifier to link to the Traffic Director service.
- array
rulesets — A list of Rulesets that are defined for the Traffic Director service:
Click for Ruleset fields.
- hash
dnskey_rdata — DNSKEY record rdata.
- string
algorithm — Required. Which public-key encryption algorithm is to sign this zone. A value of 5 is for the algorithm RSA/SHA-1, which is considered mandatory.
- string
flags — Required. Numeric value that states that this DNSKEY is the zone’s key.
- string
protocol — Required. Always set to 3 (DNSSEC).
- string
public_key — Required. Enter the DNSSEC public key from your current DNSSEC signed zone.
- hash
ds_rdata — DS record rdata.
- string
algorithm — Required. The algorithm number used by the DNSKEY resource record.
- string
digest — Required. The digest of the DNSKEY resource record this DS refers to.
- string
digtype — Required. Identifies the algorithm used to construct the digest .
- string
keytag — Required. The key tag of the DNSKEY resource record.
- hash
ipseckey_rdata IPSECKEY record rdata.
- string
precedence — Required. Similar to the preference value in MX records. IF multiple IPSECKEYs exist on a node, the lower value (10) takes precedence over the higher value (20).
- string
gatetype — Required. Value that states what type of gateway is used, if any.
- string
algorithm — Required. Identifies the public key’s cryptographic algorithm and the format of the public key field.
- string
gateway — Required. The gateway used to create the IPsec tunnel. Based on the Gateway type.
- string
public_key — Required. Base 64 encoding of the public key.
- hash
key_rdata KEY record rdata.
- string
algorithm — Required. Numeric value for the algorithm used RSA/MD5, the recommended algorithm, is 1.
- string
flags — Required.
- string
protocol — Required.Numeric value for the protocol used 1= TLS, 2=Email, 3=DNSSEC, 4= IPsec.
- string
public_key — Required. The public key.
- hash
kx_rdata KX record rdata.
- string
preference — Required.Similar to the MX record’s preference. Lower value (10) takes precedence over higher value (20) if multiple KX records exist on the same node.
- string
exchange — Required.The hostname that will act as the key exchanger. Must have a CNAME record and either an A record or an AAAA record.
- hash
loc_rdata LOC record rdata.
- string
altitude — Required.Measured in meters above sea level. Example: -44m
- string
horiz_pre — Required. Precision in meters. Example: 30m
- string
latitude — Required. Measured in degrees, minutes, and seconds. Example: 42 21 54 N
- string
longitude — Required. Measured in degrees, minutes, and seconds. Example: 71 06 18 W
- string
size — Required. Size in meters. Example: 10m
- string
version — Required.
- string
vert_pre — Required. Precision in meters. Example 10m
- hash
mx_rdata MX record rdata.
- string
exchange — Required. Hostname of the server responsible for accepting mail messages in the zone.
- string
preference — Required. The MX record with the lowest preference number is used first, then the record with the next highest number.
- hash
naptr_rdata NAPTR record rdata.
- string
order — Required. Similar to the MX Record’s preference value or SRV record’s priority value. The lowest value is used first, highest value used last.
- string
preference — Required. If one or more NAPTR records have the same value for ORDER, the value of preference is used to decide which record is used first. Lowest number goes first.
- string
flags — Required.
- string
services — Required. Always starts with e2u+ then the string that defines the type and optionally the subtype of the URI where this NAPTR points.
- string
regexp — Required. Enter regular expression for this NAPTR record.
- string
replacement — Required. Specifies the next domain name to look up if this is a non-terminal NAPTR.
- hash
ns_rdata NS record rdata.
- string
nsdname — Required. Hostname of the authoritative Nameserver for this zone.
- hash
nsap_rdata NSAP record rdata.
- string
nsap — Required. Hex-encoded NSAP identifier.
- hash
ptr_rdata PTR record rdata.
- string
ptrdname — Required. Hostname where the IP address should be directed.
- hash
px_rdata PX record rdata.
- string
preference — Required. Numeric preference.
- string
map822 — Required. Mail hostname.
- string
mapx400 — Required. X.400 address mapping.
- hash
rp_rdata RP record rdata.
- string
mbox — Required. Email address of the Responsible Person with the @ symbol replaced with a dot ‘.’.
- string
txtdname — Required. Hostname where there is a TXT record with more information.
- hash
spf_rdata SPF record rdata.
- string
txtdata — Required. Free text box.
- hash
srv_rdata SRV record rdata.
- string
port — Required. Port number where the service is running.
- string
priority — Required. Numeric value for priority usage. Lower value takes precedence where two records of the same type exist on the zone/node.
- string
target — Required. Domain name of a host where the service is running on the specified port .
- string
weight — Required. Secondary prioritizing of records to serve. Records of equal priority should be served based on their weight.
- hash
sshfp_rdata SSHFP record rdata.
- string
algorithm — Required. The algorithm for SSH key.
- string
fptype — Required. A type of fingerprint hash.
- string
fingerprint — Required. The hex-encoded fingerprint.
- hash
txt_rdata TXT record rdata.
- string
txtdata — Required. Free text field.
- 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.
|
Response — Click for More Info
- string
service_id — Identifier for the Traffic Director service.
- string
label Name of the Traffic Director service.
- string
active — Indicates whether or not the Traffic Director service is active.
Valid values:
Y if the service is active.
N if the service is inactive.
- string
ttl — The default TTL to be used across the Traffic Director service.
- string
link_id — ID representing the link.
- string
active — Indicates whether or not the link is active.
- array
notifiers — List of notifiers associated with the Traffic Director service.
- string
notifier_id — ID of the Notifier object.
- string
label — label of the notifier.
- array
recipients — List of recipients for this notifier.
- string
active — Indicates whether or not the Notifier is active.
- array
rulesets — A list of Rulesets that are defined for the service:
Click for Ruleset fields.
- array
nodes — A list of zone and FQDN pairs to identify nodes that are attached to the Traffic Director (DSF) service.
- string
zone — Name of the zone.
- string
fqdn — Fully qualified domain name of a node in the zone.
- string
pending_change — Indicates whether or not the service has any changes pending.
|
SOAP Syntax
Click to view all SOAP Commands |
UpdateDSF — Updates the indicated Traffic Director (DSF) service. |
Arguments — Click for More Info
- string
service_id — Required. ID of the Traffic Director service.
- string
label — Required. Name of the Traffic Director service.
NOTE: The following special characters are not allowed in the Traffic Director (DSF) Service label field: * < > % /
NOTE: A Traffic Director Service label may not start with a special character (Example: .special_td).
- string
ttl — The default TTL to be used across the Traffic Director service.
- string
publish — If Y, service will be published on creation.
- 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
- array
nodes — A list of zone, FQDN pairs in a hash that are to be linked to the Traffic Director service:
- string
zone — Required.Name of the zone.
- string
fqdn — Required.Fully qualified domain name of a node in the zone.
- array
notifiers — A list of notifiers associated with the Traffic Director service.
- string
notifier_id — ID of the notifier to link to the service.
- array
rulesets — A list of Rulesets that are defined for the service:
Click for Ruleset fields.
- 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
token — Required. The session identifier.
|
Response — Click for More Info
- hash
data
- string
service_id — Identifier for the Traffic Director service.
- string
label Name of the Traffic Director service.
- string
active — Indicates whether or not the service is active.
Valid values:
Y if the service is active.
N if the service is inactive.
- string
ttl — The default TTL to be used across the service.
- string
link_id — ID representing the link.
- string
active — Indicates whether or not the link is active.
- array
notifiers — List of notifiers associated with the service.
- string
notifier_id — ID of the Notifier object.
- string
label — label of the notifier.
- array
recipients — List of recipients for this notifier.
- string
active — Indicates whether or not the Notifier is active.
- array
rulesets — A list of Rulesets that are defined for the service:
Click for Ruleset fields.
- array
nodes — A list of zone and FQDN pairs to identify nodes that are attached to the Traffic Director service.
- string
zone — Name of the zone.
- string
fqdn — Fully qualified domain name of a node in the zone.
- string
pending_change — Indicates whether or not the service has any changes pending.
|
Example Request — Click for More Info
{
'service_id' => 'fv298...', # ID shortened...
'label' => 'Example Traffic Director Service',
'attached_nodes' => [{
'zone' => 'foorbar.com',
'node' => 'nh.foobar.com',
}],
'ttl' => '3600',
'rulesets' => [{
'label' => 'Example Ruleset',
'criteria_type' => 'geoip',
'criteria' => {
'geoip' => {
'country' => ['US'],
}
},
'response_pools' => [{
'label' => 'Response Pool Example',
'core_set_count' => '1',
'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',
}],}
],
}]
}],
'publish' => 'true',
'token' => 'asdlj34ot879834cdzjklfK'
}
|
DNS API Knowledge Base