host
Click on the red underlined text to get to the source
... As discussed in section 5, existing approaches to using DNS records
for dynamically determining the current host for a given application
service are limited in terms of the use cases supported. To address ...
... "Failure" is declared, and backtracking must be used, when
o the designated remote server (host and port) fails to provide
appropriate security ...
... hosting example in Section 4.3, the service
owner (thinkingcat.example) had to host pointers to the hosting
service ...
... NAPTR records for each service to map them to whatever local hosts it
chooses (this may change from time to time).
...
... SRV
resource records to determine the host and port providing the server.
This enables a distinction between naming an application service ...
... administrators to use several servers for a single
domain, to move services from host to host with little fuss, and
to designate some hosts ...
... single
domain, to move services from host to host with little fuss, and
to designate some hosts as primary servers for a service ...
... host to host with little fuss, and
to designate some hosts as primary servers for a service and
others as backups".
...
... The basic answer is that SRV records provide mappings from protocol
names to host and port. The use cases described herein require an
additional layer ...
... The expected output of this Application is the information necessary
for a client to connect to authoritative server(s) (host, port,
protocol) for a particular application service ...
... The pseudocode in Appendix A is crafted to find the first, most
preferred host-port pair for a particular application service and
...
... port pair for a particular application service and
protocol. If, for any reason, that host-port pair did not work
(connection refused ...
... application-level error), the client is expected
to try the next host-port in the S-NAPTR tree ...