host
Click on the red underlined text to get to the source
... 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.
...
... target host. A client MUST attempt to
contact the target host with the lowest-numbered priority it can
reach; target hosts ...
... target host with the lowest-numbered priority it can
reach; target hosts with the same priority SHOULD be tried in an
order defined by the weight field. The range ...
... first in the selected order which is greater than or equal to
the random number selected. The target host specified in the
selected SRV RR is the next one to be contacted by the client ...
... SRV RRs to select
the next target host. Continue the ordering process until there
are no unordered SRV RRs ...
... Target
The domain name of the target host. There MUST be one or more
address records for this name, the name MUST NOT be an alias ...
... services for a single domain are spread over several
hosts, it seems advisable to have a list of address records at
the same DNS ...
... node as the SRV RR, listing reasonable (if perhaps
suboptimal) fallback hosts for Telnet, NNTP and other protocols
...
... Where one service is provided by several hosts, one can either
provide address records for all the hosts ...
... hosts, one can either
provide address records for all the hosts (in which case the
round-robin mechanism, where available, will share the load
...
... If a host is intended to provide a service only when the main
server(s) is/are down, it probably shouldn't be listed in
...
... service ("_ldap._tcp.example.com" for instance); each SRV RR
adds 20 bytes plus the name of the target host; each NS RR in the NS ...
... NS
section is 15 bytes plus the name of the name server host; and
finally each A RR in the additional data section is 20 bytes or so,
...
... SRV RR's and the client may want to connect to the
target host(s) involved, the client MUST look up the address
...
... "_foobar._tcp.example.com." and possibly A lookups of "new-fast-
box.example.com." and/or the other hosts named. The size of the SRV
reply is approximately 365 bytes:
...
... There is no way a site can keep its hosts from being referenced
as servers. This could lead to denial of service.
...
... DNS spoofers can supply false port numbers, as well as
host names and addresses. Because this vulnerability exists
...