RR
Click on the red underlined text to get to the source
... non-terminal" -- that is,
more NAPTR RR lookups are to be performed. Thus, to process a NAPTR
record with an empty FLAG field ...
... target of a DNS query for SRV RRs,
and normal SRV processing is applied. In the case of an "A" flag, an
...
... S-NAPTR-designated DNS lookup fails to yield expected results
-- e.g., no A RR for an "A" target, no SRV record for an "S"
...
... application client first queries for the NAPTR RRs for the domain
of a named application service ...
... start looking for one protocol, observe
that a successive NAPTR RR set supports another of its preferred
protocols, and continue the S-NAPTR resolution based on that
...
... does so on behalf of example.com (as there is no such pointer in
example.com's NAPTR RR set).
It MAY choose which protocol to try first based on its own
...
... domain). However, the chosen
protocol MUST be listed in that first NAPTR RR set.
It MAY choose to run simultaneous DDDS ...
... DNS resolvers should fail to implement all aspects of the
NAPTR RR standard. A DDDS application is a client use convention.
...
... The complete set of NAPTR, SRV, and A RRs "reachable" through the S-
NAPTR process for a particular application service ...
...
A better approach is to have one NAPTR RR in the thinkingcat.example
domain point to all the hosted services ...
... SERVICE strings to determine whether there was a NAPTR RR that
matched the application service it was looking for, with an
...
... issues, not to provide application naming: As stated in [3], "The
SRV RR allows administrators to use several servers for a single
domain, to move services ...
... Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for specifying the location of services (DNS SRV)", RFC 2782prop ...