Return to FAQ/Help System menu

NAPTR-records are used to store rules used by DDDS (Dynamic Delegation Discovery System) applications.

One example is "ENUM" which allows an end user to type a telephone number into e.g. a web browser and access a listing of Internet resources (URI) for that number, such as addresses for IP telephony, email or web sites. For more information on "ENUM", see http://www.ripe.net/enum or http://enum.nic.at

The "Order" field is a number (0 to 65535) specifying the order in which multiple NAPTR records must be processed (low to high) by the application.

The "Preference" field is equivalent to the Priority value in the DDDS algorithm. It is a number (0-65535) that specifies the order (low to high) in which NAPTR records with equal Order values should be processed.

The "Flags" field contains flags to control aspects of the rewriting and interpretation of the fields in the record. Flags are single characters from the set A-Z and 0-9. The use of this field is specified by the individual DDDS application.

The "Services" field specifies the service parameters applicable to this delegation path. The individual DDDS application specifies the possible values for this field.

The "Reg. Exp." field contains a substitution expression that is applied to the original string held by the client in order to construct the next domain name to lookup. See the DDDS algorithm specification for the syntax of this field.

The "Replacement" field specifies the next domain name (fully qualified) to query for depending on the potential values found in the flags field. This field is used when the regular expression is empty (a simple replacement operation). The "Reg.Exp." and "Replacement" fields are mutually exclusive (only one can contain a value).

You can use the NSAP-record in the Raw form only on our servers.

Return to FAQ/Help System menu