lookup
Click on the red underlined text to get to the source
... specify a particular application. This separation is due to several
different applications all wanting to take advantage of the rewrite
rule lookup process. Each one has vastly different reasons for why
and how it uses the service, thus requiring that the definition of
...
... At this time only four flags, "S", "A", "U", and "P", are
defined. The "S", "A" and "U" flags denote a terminal lookup.
This means that this NAPTR record is the last one and that the
...
... NAPTR record is the last one and that the
flag determines what the next stage should be. The "S" flag
means that the next lookup should be for SRV records [4]. See
...
... Section 5 for additional information on how NAPTR uses the SRV
record type. "A" means that the next lookup should be for either
an A, AAAA, or A6 record. The "U" flag means that the next step
...
... an A, AAAA, or A6 record. The "U" flag means that the next step
is not a DNS lookup but that the output of the Regexp field is an
URI that adheres to the 'absoluteURI' production found in the
...
... 9]. Since there may be applications that use
NAPTR to also lookup aspects of URIs, implementors should be
...
... NAPTR is terminal, the next
lookup MUST be for a NAPTR. The client MAY choose not to perform
...
... NAPTR. The client MAY choose not to perform
the next lookup if the protocol is unknown, but that behavior
MUST NOT be relied upon.
...
... 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.
...
... expression returns the string "gatech.edu". Since the flags field
does not contain "s" or "a", the lookup is not terminal and our next
probe ...
... Using the rules specified for this application we extract the prefix,
"http", and lookup NAPTR records for http.uri.arpa. This might
return a record ...
... If the lookup after a rewrite fails, clients are strongly
encouraged to report a failure, rather than backing up to pursue
...