domain
Click on the red underlined text to get to the source
... regular expression that would be used by a client program to
rewrite a string into a domain name. Regular expressions were chosen
for their compactness to expressivity ratio allowing for a great deal
...
... rewrite procedure in various ways or to provide information on how to
communicate with the host at the domain name that was the result of
the rewrite.
...
... Domain
The domain name to which this resource record refers. This is the
'key' for this entry in the rule database ...
... NAPTR
records with equal "order" values SHOULD be 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 ...
... NAPTR RR exists at the
domain name produced by the current rewrite rule. Since the "P"
flag specifies a new algorithm, it may or may not be 'terminal ...
... the original string held by the client in order to construct the
next domain name to lookup. The grammar of the substitution
expression is given in the next section.
...
... that is, they should only be 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
...
... depending on the value of the flags field. This MUST be a fully
qualified domain-name. Unless and until permitted by future
standards action, name compression is not to be used for this
...
... URI MUST result in either a string that obeys the syntax for DNS
domain-names [1] or a URI [9 ...
... Flags field contains a 'u'.
Since it is possible for the regexp field to be improperly specified,
such that a non-conforming domain-name can be constructed, client
software SHOULD verify that the result is a legal DNS domain ...
... domain-name can be constructed, client
software SHOULD verify that the result is a legal DNS domain-name
before making queries on it.
...
... The algorithm starts with a string and some known key (domain).
NAPTR records for this key are retrieved, those with unknown Flags or
...
... advances toward the desired result. If so, the rule is applied to
the target string. If not, the process halts. The domain that
results from the regular expression is then used as the domain ...
... domain that
results from the regular expression is then used as the domain of the
next loop through the NAPTR algorithm ...
... SRV record type was originally specified it assumed that the
client did not know the specific domain-name before hand. The client
would construct a domain ...
... domain-name before hand. The client
would construct a domain-name more in the form of a question than the
usual case of knowing ahead of time that the domain-name should
...
... would construct a domain-name more in the form of a question than the
usual case of knowing ahead of time that the domain-name should
exist. I.e., if the client wants to know if there is a TCP ...
... domain, the client would
construct the domain-name _http._tcp.somedomain.com and ask the DNS
if that records exists. The underscores are used to avoid collisions
...
... DNS
if that records exists. The underscores are used to avoid collisions
with potentially 'real' domain-names.
...
...
In the case of NAPTR, the actual domain-name is specified by the
various fields in the NAPTR record. In this case the client ...
... that it has been told exists in an SRV record at that particular
domain-name. While this usage of SRV is slightly different than the
SRV ...
... SRV contains. Also, since the NAPTR
explicitly spells out the domain-name for which an SRV exists, that
domain ...
... NO transformations. Any
given NAPTR record may result in a domain-name to be used for SRV
queries ...
... NAPTR applications that make use of SRV MUST NOT attempt
to understand these domains or use them according to how the SRV
specification structures its query ...
... The first known domain-name or how to build it
...
... probe to DNS is for more NAPTR records where the new domain is '
gatech.edu' and the string is the same string as before.
...
...
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 mordred, could have their very own
NAPTR ...
...
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 occurances of a backslash must be escaped by
...
... URI. In order to convert the
phone number to a domain name for the first iteration all characters
other than digits are removed from the the telephone number ...
... E.164 phone number "+1-770-555-1212" converted to a domain-name it
would be "2.1.2.1.5.5.5.0.7.7.1.e164.arpa."
...
... regular expression.
REPLACEMENT A <domain-name> which specifies the new value in the
case where the regular expression is a simple replacement
...
... 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.
...
... 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. ...