domain
Click on the red underlined text to get to the source
... reached.
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 ...
... regular expression that would
be used by a client program to rewrite a string into a domain name.
Regular expressions ...
... Lookup Response:
The response to a request for a given Key (domain-name) will be a
series of NAPTR records. The format of a NAPTR Resource Record ...
... Section 6.2), there is a chance of collision between rules where
two NAPTR records appear in the same domain but they apply to more
than one Application. There are three ways to avoid collisions:
...
...
* create a new zone within the domain in common that contains
only NAPTR records that are appropriate for the application.
...
... +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
<character-string> and <domain-name> as used here are defined in RFC
1035std13 [7 ...
... processed, low numbers being processed before high numbers. This
is similar to the preference field in an MX record, and is used so
domain administrators can direct clients towards more capable
...
... 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.
...
... applied to the original string held by the client, never to the
domain name produced by a previous NAPTR rewrite. The latter is
tempting in some applications but experience has shown such use to
...
... REPLACEMENT
A <domain-name> which is the next domain-name to query for
depending on the potential values found in the flags field ...
... regular expression is a simple replacement
operation. Any value in this field MUST be a fully qualified
domain-name. Name compression is not to be used for this field.
...
... define the following values:
o What domain the Key that is produced by the First Well Known Rule
belongs to. Any application must ensure that its rules do not
collide with rules used by another application making use of this
...
... queries the DNS for NAPTR records for the domain-
name 'cid.urn.arpa'. The result is a single record:
...
... DNS is for
more NAPTR records where the new domain is 'example.com'.
Note that the rule does not extract the full domain name ...
... domain is 'example.com'.
Note that the rule does not extract the full domain name from the
CID, instead it assumes the CID ...
... CID comes from a host and extracts its
domain. While all hosts, such as 'bar', could have their very own
NAPTR ...
... terminal lookup and that the output of the rewrite will be a domain-
name for which an A record should be queried. Once the client ...
...
Recall that the regular expression used \2 to extract a domain name
from the CID, and \. for matching the literal ...
... CID, and \. for matching the literal '.' characters
separating the domain name components. Since '\' is the escape
character, literal occurrences of a backslash must be escaped by
...
... The above telephone number would then read
"2.1.2.1.5.5.5.0.7.7.1.e164.arpa.". This domain-name is then used to
retrieve Rewrite Rules as NAPTR records.
...
... subject to the
same attacks as normal domain names. Since they have not been easily
resolvable before, this may or may not be considered a problem.
...
... Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database", RFC 3403prop ...
... Mockapetris, P., "Domain names - implementation and specification", STD 13, RFC 1035std13, November 1987. ...
... Mockapetris, P., "Domain names - concepts and facilities", STD 13, RFC 1034std13, November 1987. ...
... Daniel, R. and M. Mealling, "Resolution of Uniform Resource Identifiers using the Domain Name System", RFC 2168(-> 3404prop | 3403prop | 3402prop | 3401), June 1997. ...