Lines Matching refs:unicast

46    on the local link in the absence of any conventional unicast DNS
427    All Multicast DNS responses (including responses sent via unicast)
439    spoof answer packets (perhaps unicast to the victim host) which the
455    * For responses sent to a unicast destination address, the source IP
470    then even if the query indicates that a unicast response is preferred
473    reasonably predict that a unicast response with an apparently
495    unicast directly to the address in question, but if this query is not
502    with or without an optional initial query unicast directly to the
548    is not exactly the same as unicast DNS, and should modify its
694    willing to accept unicast responses instead of the usual multicast
695    responses. These questions requesting unicast responses are referred
699    When retransmitting a question more than once, the 'unicast response'
708    When receiving a question with the 'unicast response' bit set, a
709    responder SHOULD usually respond with a unicast packet directed back
942    Except when a unicast reply has been explicitly requested via the
943    "unicast reply" bit, Multicast DNS Responses MUST be sent to UDP port
980    directly back to the client, via unicast, to the query packet's
981    source IP address and port. This unicast response MUST be a
982    conventional unicast response as would be generated by a conventional
983    unicast DNS server; for example, it MUST repeat the query ID and the
986    The resource record TTL given in a legacy unicast response SHOULD NOT
991    stale data. Were unicast responses sent to legacy clients to use the
996    Having sent this unicast response, if the Responder has not sent this
1538    legacy unicast responses to UDP ports other than 5353.
1888    Attempts to remedy this for unicast DNS have been badly constrained
1929    limitation) the unicast DNS community settled on an extremely baroque
2052    In unicast response messages generated specifically in response to a
2053    particular (unicast or multicast) query, the Query ID MUST match the
2093    In legacy unicast response messages, the TC bit has the same meaning
2094    as in conventional unicast DNS: it means that the response was too
2155    qclass field is used to indicate that unicast responses are preferred
2198      and a conventional unicast DNS server on the same machine. If a
2199      conventional unicast DNS server wishes to implement mDNS as well,
2257    * defines a "unicast response" bit in the rrclass of query questions
2308      place of multiple unicast responses, when appropriate.
2354    unicast. Particularly in IPv6, where multicast addresses are