RFC 2915:The Naming Authority Pointer (NAPTR) DNS ...
RFC-Ref

RFC - 2915

The Naming Authority Pointer (NAPTR) DNS Resource Record

Original: ftp://ftp.isi.edu/in-notes/rfc2915.txt
Authors: M. Mealling [Network Solutions, Inc.], R. Daniel [DATAFUSION, Inc.]
Date: September 2000
Category: Informational
 
This specification has been !!! obsoleted !!!



Obsoleted by:
RFC-3404prop Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI)
RFC-3403prop Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database
RFC-3402prop Dynamic Delegation Discovery System (DDDS) Part Two: The Algorithm
RFC-3401 Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS

Updates:
RFC-2168 Resolution of Uniform Resource Identifiers using the Domain Name System (Obsoleted by RFC-3401, RFC-3403prop, RFC-3402prop, RFC-3404prop) (Updated by RFC-2915)

Referred by: 16 RFC
Refers to: 9 RFC

Status

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2000). All Rights Reserved.

IESG Note

Abstract

This document describes a Domain Name System (DNS) resource record which specifies a regular expression based rewrite rule that, when applied to an existing string, will produce a new domain label or Uniform Resource Identifier (URI). Depending on the value of the flags field of the resource record, the resulting domain label or URI may be used in subsequent queries for the Naming Authority Pointer (NAPTR) resource records (to delegate the name lookup) or as the output of the entire process for which this system is used (a resolution server for URI resolution, a service URI for ENUM style e.164 number to URI mapping, etc).

This allows the DNS to be used to lookup services for a wide variety of resource names (including URIs) which are not in domain name syntax. Reasons for doing this range from URN Resource Discovery Systems to moving out-of-date services to new domains.

This document updates the portions of RFC 2168(-> 3404prop | 3403prop | 3402prop | 3401) specifically dealing with the definition of the NAPTR records and how other, non-URI specific applications, might use NAPTR.


About Resource

Google
Web
RFC-Ref