address
Click on the red underlined text to get to the source
...
Currently, one must either know the exact address of a server to
contact it, or broadcast a question.
...
... domain name of the target host. There MUST be one or more
address records for this name, the name MUST NOT be an alias (in
the sense of RFC 1034std13 ...
... 2181prop). Implementors are urged, but
not required, to return the address record(s) in the Additional
Data section. Unless and until permitted by future standards
action, name compression ...
... SRV RR is futile (even if desirable). Therefore
SRV would have to coexist with address record lookups for existing
protocols, and DNS ...
... protocols, and DNS administrators should try to provide address
records to support old clients:
...
... single domain are spread over several
hosts, it seems advisable to have a list of address records at
the same DNS node ...
... NNTP and other protocols
likely to be used with this name. Note that some programs only
try the first address they get back from e.g. gethostbyname(),
and we don't know how widespread this behavior is.
...
... service is provided by several hosts, one can either
provide address records for all the hosts (in which case the
round-robin ...
... service only when the main
server(s) is/are down, it probably shouldn't be listed in
address records.
...
... Hosts that are referenced by backup address records must use the
port number specified in Assigned Numbers for the service ...
... query the DNS for address records for the Target or
use any such records found in the Additional Data
...
... SRV response.
for each address record found, try to connect to the
(protocol, address, service ...
... IN, QTYPE=A
for each address record found, try to connect to the
(protocol, address, service ...
... If the Additional Data section doesn't contain address records
for all the SRV RR's and the client ...
... target host(s) involved, the client MUST look up the address
record(s). (This happens quite often when the address record
...
... client MUST look up the address
record(s). (This happens quite often when the address record
has shorter TTL than the SRV ...
... provider.net." is
quoted and only needs to be counted once.
120 bytes for the 6 address records (assuming IPv4 only) mentioned
by the SRV ...
... port numbers, as well as
host names and addresses. Because this vulnerability exists
already, with names and addresses ...
... addresses. Because this vulnerability exists
already, with names and addresses, this is not a new
vulnerability, merely a slightly extended one, with little
...
... Authors' Addresses ...