SRV Record
Click on the red underlined text to get to the source
... possible to create very
complex chains and dependencies with the NAPTR and SRV records.
Therefore, domain ...
... RR that is retrieved points to more NAPTR or
SRV records; each SRV record points to several A record lookups ...
...
o fewer branches is better: For both NAPTR and SRV records, provide
different targets with varying preferences where appropriate
...
... services
hosted elsewhere (i.e., where you cannot reasonably provide the
SRV records in your own zone).
...
... service. See section 4.4 for an example that cannot be served by
SRV records alone.
...
... service, yet the out-sourcer can independently
rank the preference and ordering of servers. This independence is
not achievable through the use of SRV records alone.
Thus, to find the EM services ...
... "s" flag and a replacement fields of "_ProtB._tcp.example.com".
So the client looks up SRV records for that target, ultimately
making the request of the NS ...
... NS for example.com.
4. The response includes the SRV records listed in Section 4.3.
5. The client ...
... IP address, on port 10001 (from the
SRV record), by using ProtB over tcp.
10. The server responds with an "OK" message.
...
... inherent limitations.
That is, although SRV records can be used to map from a specific
service name and protocol for a specific domain ...
... service name and protocol for a specific domain to a specific server,
SRV records are limited to one layer of indirection and are focused
on server administration rather than on application naming.
...
... multiple levels of redirection before the target server machine with
an SRV record is located, this proposal requires only a subset of
NAPTR strictly bound to domain names ...
... So Why Not Just SRV Records? ...
...
An expected question at this point is: this is so similar in
structure to SRV records, why are we doing this with DDDS/NAPTR?
...
... for the uses described here.
The basic answer is that SRV records provide mappings from protocol
names to host and port ...
... DNS queries along the way. If any of
them is compromised, bogus NAPTR and SRV records could be inserted to
redirect clients to unintended destinations ...