Configuration Parameters
Polycom, Inc. 57
DNS-NAPTR
Add up to 12 DNS-NAPTR record entries using parameters in the following table. Specify each parameter
for DNS-NAPTR record x, where x is from 1 to 12.
DNS-SRV
Add up to 12 DNS-SRV record entries using parameters in the following table. Specify each parameter for
DNS-SRV record x, where x is from 1 to 12.
DNS-NAPTR Parameters
Parameter Permitted values Default
dns.cache.NAPTR.x.flags A single character from [A-Z, 0-9] Null
The flags to control aspects of the rewriting and interpretation of the fields in the record. Characters are
case-sensitive. At this time, only ‘S’, ‘A’, ‘U’, and ‘P’ are defined as flags. See RFC 2915 for details of the permitted
flags.
dns.cache.NAPTR.x.name domain name string Null
The domain name to which this resource record refers.
dns.cache.NAPTR.x.order 0 to 65535 0
An integer specifying the order in which the NAPTR records must be processed to ensure the correct ordering of
rules.
dns.cache.NAPTR.x.preference 0 to 65535 0
A 16-bit unsigned integer that specifies the order in which NAPTR records with equal "order" values should be
processed. Low numbers are processed before high numbers.
dns.cache.NAPTR.x.regexp string containing a substitution expression Null
This parameter is currently unused.
Applied to the original string held by the client. The substitution expression is applied in order to construct the next
domain name to look up. The grammar of the substitution expression is given in RFC 2915.
dns.cache.NAPTR.x.replacement domain name string with SRV prefix Null
The next name to query for NAPTR records depending on the value of the flags field. It must be a fully qualified
domain-name.
dns.cache.NAPTR.x.service string Null
Specifies the service(s) available down this rewrite path. For more information, see RFC 2915.
dns.cache.NAPTR.x.ttl 300 to 536870912 (2^29), seconds 300
The TTL describes the time period the system uses the configured static cache record. If a dynamic network request
receives no response, this timer begins on first access of the static record and once the timer expires, the next
lookup for that record retries a dynamic network request before falling back on the static entry and its reset TTL timer
again.
To Next Page
Loading...
