Updating DHCID Records 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.
See RFC 4701 for more information about the DHCID record.
Understanding How The API Works »
REST Syntax
Click to view all REST Resources |
/REST/DHCIDRecord/ PUT — Update an existing DHCID Record on the zone/node indicated.
HTTP Action — PUT
URI — https://api.dynect.net/REST/DHCIDRecord/<zone>/<fqdn>/<record_id>/ |
Arguments:
- hash
rdata — Required. RData defining the record to add.
- string
digest — Required. Base-64 encoded digest of DHCP data.
- string
ttl — TTL for the record in seconds. Set to “0” to use zone default
|
Response — Click for More Info
- string
fqdn — Fully qualified domain name of a node in the zone.
- hash
rdata — RData defining the record.
- string
digest — Base-64 encoded digest of DHCP data.
- string
record_type — The RRType of the record.
- string
ttl — TTL for the record.
- string
zone — Name of the zone.
|
SOAP Syntax
Click to view all SOAP Commands |
UpdateDHCIDRecord — Update an existing DHCID Record on the zone/node indicated. |
Arguments — Click for More Info
- string
fqdn — Required. Name of node where the record will be added.
- string
record_id — Required only if there is more than 1 record of this type on the node.
- hash
rdata — Required. RData defining the record to add.
- string
digest — Required. Base-64 encoded digest of DHCP data.
- string
token — Required. The session identifier.
- string
ttl — TTL for the record in seconds. Set to “0” to use zone default.
- string
zone — Required. Name of zone where the record will be added.
|
Response — Click for More Info
- hash
data
- string
fqdn — Fully qualified domain name of a node in the zone.
- hash
rdata — RData defining the record
- string
digest — Base-64 encoded digest of DHCP data.
- string
record_id — A numeric identifier for the record.
- string
record_type — The RRType of the record.
- string
ttl — TTL for the record.
- string
zone — Name of the zone.
|
Example Request — Click for More Info
{
'fqdn' => 'client.example.com',
'record_id' => '32',
'rdata' => {
'digest' => 'AAIBY2/AuCccgoJbsaxcQc9TUapptP69lOjxfNuVAA2kjEA='
},
'token' => 'asdlkfjasl23j4879afa',
'ttl' => '3600',
'zone' => 'example.com',
}
|
DNS API Knowledge Base