Replacing all NAPTR 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 2915 for more information about NAPTR records.
Understanding How The API Works »
REST Syntax
Click to view all REST Resources |
/REST/NAPTRRecord/ PUT — Replacing all existing NAPTR Record on the zone/node indicated.
HTTP Action — PUT
URI — https://api.dynect.net/REST/NAPTRRecord/<zone>/<fqdn>/ |
Arguments — Click for More Info
- array
NAPTRRecords — Required. Individual records.
- hash
rdata — Required. RData defining the record to add.
- string
order — Required. Indicates the required priority for processing NAPTR records. Lowest value is used first.
- string
preference — Required. Indicates priority where two or more NAPTR records have identical order values. Lowest value is used first.
- string
flags — Required. Should be the letter “U”. This indicates that this NAPTR record terminal (E.164 number that maps directly to a URI).
- string
services — Required. Always starts with “e2u+” (E.164 to URI). After the e2u+ there is a string that defines the type and optionally the subtype of the URI where this NAPTR record points.
- string
regexp — Required. The NAPTR record accepts regular expressions.
- string
replacement — Required. The next domain name to find. Only applies if this NAPTR record is non-terminal.
- string
ttl — TTL for the record in seconds. Set to “0” to use zone default.
|
Response — Click for More Info
- array — Individual records.
- string
fqdn — Name of the node where the record will exist.
- hash
rdata — RData defining the record to add.
- string
order — Indicates the required priority for processing NAPTR records. Lowest value is used first.
- string
preference — Indicates priority where two or more NAPTR records have identical order values. Lowest value is used first.
- string
flags — Should be the letter “U”. This indicates that this NAPTR record terminal (E.164 number that maps directly to a URI).
- string
services — Always starts with “e2u+” (E.164 to URI). After the e2u+ there is a string that defines the type and optionally the subtype of the URI where this NAPTR record points.
- string
regexp — The NAPTR record accepts regular expressions. See RFC 2915 for more information about the format of the regular expression.
- string
replacement — The next domain name to find. Only applies if this NAPTR record is non-terminal.
- string
record_type — The RRType of the record.
- string
ttl — TTL for the record in seconds. Set to “0” to use zone default.
- string
zone — Name of zone where record is added.
|
SOAP Syntax
Click to view all SOAP Commands |
ReplaceNAPTRRecords — Replace all existing NAPTR Record on the zone/node indicated. |
Arguments — Click for More Info
- array
NAPTRRecords — Required. Individual records.
- string
fqdn — Required. Name of the node where the record exists.
- hash
rdata — Required. RData defining the record.
- string
order — Required. Indicates the required priority for processing NAPTR records. Lowest value is used first.
- string
preference — Required. Indicates priority where two or more NAPTR records have identical order values. Lowest value is used first.
- string
flags — Required. Should be the letter “U”. This indicates that this NAPTR record terminal (E.164 number that maps directly to a URI).
- string
services — Required. Always starts with “e2u+” (E.164 to URI). After the e2u+ there is a string that defines the type and optionally the subtype of the URI where this NAPTR record points.
- string
regexp — Required. The NAPTR record accepts regular expressions.
- string
replacement — Required. The next domain name to find. Only applies if this NAPTR record is non-terminal.
- string
ttl — TTL for the record in seconds. Set to “0” to use zone default.
- string
zone — Required. Name of zone where record exists.
- string
token — Required. The session identifier.
|
Response — Click for More Info
- array
data
- string
fqdn — Name of the node where the record will reside.
- hash
rdata — RData defining the record to add.
- string
order — Indicates the required priority for processing NAPTR records. Lowest value is used first.
- string
preference — Indicates priority where two or more NAPTR records have identical order values. Lowest value is used first.
- string
flags — Should be the letter “U”. This indicates that this NAPTR record terminal (E.164 number that maps directly to a URI).
- string
services — Always starts with “e2u+” (E.164 to URI). After the e2u+ there is a string that defines the type and optionally the subtype of the URI where this NAPTR record points.
- string
regexp — The NAPTR record accepts regular expressions. See RFC 2915 for more information about the format of the regular expression.
- string
replacement — The next domain name to find. Only applies if this NAPTR record is non-terminal.
- string
record_id — Numeric identifier for the NAPTR record.
- string
record_type — The RRType of the record.
- string
ttl — TTL for the record in seconds. Set to “0” to use zone default.
- string
zone — Name of zone where record is added.
|
Example Request — Click for More Info
{
'NAPTRRecords' => [
{
'fqdn' => 'www.example.com',
'rdata' => {
'order' => 1,
'preference' => 20,
'flags' => 's',
'services' => 'rcds+I2C',
'regexp' => '!^.*!example.!',
'replacement' => '_rcds._udp.example.com',
},
'ttl' => '3600',
'zone' => 'example.com',
},
{
'fqdn' => 'www.example.com',
'rdata' => {
'order' => 1,
'preference' => 10,
'flags' => 's',
'services' => 'rcds+I2C',
'regexp' => '!^.*!example.!',
'replacement' => '_rcds2._udp.example.com',
},
'ttl' => '3600',
'zone' => 'example.com',
}
],
'token' => 'asdlkfjasl23j4879afa',
}
|
DNS API Knowledge Base