RFC 3403:Dynamic Delegation Discovery System (DDDS...
RFC-Ref

DNS


Click on the red underlined text to get to the source

... This document describes the way in which the Domain Name System (DNS) is used as a data store for the Rules that allow a DDDS Application ...
... The Naming Authority Pointer (NAPTR) DNS Resource Record (RR) specified here was originally produced by the URN ...
... URN Working Group as a way to encode rule-sets in DNS so that the delegated sections of a Uniform Resource Identifiers (URI ...
... Regular expressions were chosen for their compactness to expressivity ratio allowing for a great deal of information to be encoded in a rather small DNS packet. Over time this process was generalized for other Applications and ...


... This database uses the Domain Name System (DNS) as specified in [8] and [7 ...
... expressions to loose their ability to be universally applicable. All DNS resource records have a Time To Live (TTL) associated with ...
... Key Format: A Key is a validly constructed DNS domain-name. ...
... In order to request a set of rules for a given Key, the client issues a request, following standard DNS rules, for NAPTR Resource Records for the given domain ...
... Rule Insertion Procedure: Rules are inserted by adding new records to the appropriate DNS zone. If a Rule produces a Key that exists in a particular zone then only the entity that has administrative control ...


... packet format of the NAPTR RR is given below. The DNS type code for NAPTR is 35. ...
... PREFERENCE Although it is called "preference" in deference to DNS terminology, this field is equivalent to the Priority value in the ...
... load balancing standpoint. It is important to note that DNS contains several load balancing mechanisms and if load balancing ...
... Expression in the DDDS Algorithm. It is simply a historical optimization specifically for DNS compression that this field exists. The fields are also mutually exclusive. If a record ...
... Additional section processing requires upgraded DNS servers, thus it will take many years before applications can expect to see relevant records in the additional information section. ...
... Additional Section Processing by DNS Servers ...
... DNS servers MAY add RRsets to the additional information section that are relevant to the answer and have the same authenticity as the data in the answer section. Generally this will be made up of A and SRV records ...
... Applications MAY inspect the Additional Information section for relevant records but Applications MUST NOT require that records of any type be in the Additional Information section of any DNS response in order for clients to function. All Applications must be capable ...


... Next, the client queries the DNS for NAPTR records for the domain- ...
... lookup is not terminal and our next probe to DNS is for more NAPTR records where the new domain ...


... Advice for DNS Administrators ...
... regular expressions. Not only are they difficult to get correct on their own, but there is the previously mentioned interaction with DNS. Any backslashes in a regexp must be entered twice in a zone file in order to appear once in a query response. ...
... More seriously, the need for double backslashes has probably not been tested by all implementors of DNS servers. In order to mitigate zone file problems, administrators ...


... The NAPTR record, like any other DNS record, can be signed and validated according to the procedures specified in DNSSEC ...


... Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database", RFC 3403prop, October 2002. ...
... Gulbrandsen, A., Vixie, P. and L. Esibov, "A DNS RR for specifying the location of services (DNS SRV ...
... DNS RR for specifying the location of services (DNS SRV)", RFC 2782prop, February 2000. ...
... Faltstrom, P., "E.164 number and DNS", RFC 2916(-> 3761prop), September 2000. ...



Google
Web
RFC-Ref