Naming Authority Pointer

Description

The NAPTR (Naming Authority Pointer) record is a type of DNS resource record defined in RFC 3403. It provides a mechanism for rewriting domain names into URIs or other domain names through a set of ordered rules. Each NAPTR record contains several fields: order, preference, flags, services, regexp, and replacement. The order field determines the sequence in which records are processed, while preference allows for load balancing among records of the same order. Flags indicate the next step after the rewrite (e.g., 'S' for SRV lookup, 'A' for A/AAAA lookup, 'U' for URI). The services field specifies the protocol and service applicable (e.g., 'E2U+sip' for SIP ENUM). The regexp field contains a regular expression pattern for rewriting the input string, and the replacement field provides a domain name for further DNS queries if regexp is not used. In 3GPP, NAPTR is primarily used in the IP Multimedia Subsystem (IMS) for ENUM lookups, where E.164 telephone numbers are translated into SIP URIs by querying DNS with a domain derived from the number. This enables inter-operator routing and service discovery. The process involves iterative DNS queries: first, a NAPTR query returns records with service parameters; based on the flags, subsequent SRV or A/AAAA queries are performed to resolve the actual endpoint. This flexible mechanism supports dynamic service selection and protocol negotiation, which is crucial for IMS interoperability and multimedia service delivery.

Purpose & Motivation

NAPTR was adopted in 3GPP to address the need for flexible and dynamic service discovery and routing in all-IP networks, particularly within IMS. As telecommunications moved towards SIP-based multimedia services, there was a requirement to map telephone numbers (E.164) to IP-based addresses (URIs) efficiently. Traditional static routing or hard-coded mappings were insufficient for scalable, multi-vendor environments. NAPTR, as part of the DNS framework, provides a standardized way to perform this mapping through DNS queries, enabling operators to delegate authority and configure complex routing rules. It solves problems related to number portability, service selection (e.g., choosing between SIP, tel, or other protocols), and load balancing across multiple servers. Its use in ENUM facilitates global interconnection of VoIP and IMS networks, replacing legacy circuit-switched routing with DNS-based lookups.

Key Features

• DNS resource record for dynamic delegation and service discovery
• Supports ordered and preferential rule processing for routing
• Enables ENUM (E.164 to URI mapping) for IMS and VoIP
• Integrates with SRV and A/AAAA records for endpoint resolution
• Allows regexp-based rewriting of domain names
• Facilitates protocol and service negotiation through flags

Evolution Across Releases

Defining Specifications