Lines Matching refs:unicast
46 on the local link in the absence of any conventional unicast DNS
435 All Multicast DNS responses (including responses sent via unicast)
447 spoof answer packets (perhaps unicast to the victim host) which the
469 * For responses sent to a unicast destination address, the source IP
484 then even if the query indicates that a unicast response is preferred
487 reasonably predict that a unicast response with an apparently
550 configured unicast DNS server address that would otherwise be used.
571 is not exactly the same as unicast DNS, and should modify its
724 question as the "unicast response" bit. When this bit is set in a
725 question, it indicates that the Querier is willing to accept unicast
727 requesting unicast responses are referred to as "QU" questions, to
749 When receiving a question with the "unicast response" bit set, a
750 responder SHOULD usually respond with a unicast packet directed back
762 answering a probe question with the "unicast response" bit set, the
763 responder should always generate the requested unicast response, but
769 unicast replies are subject to all the same packet generation rules
794 makes sense for a Multicast DNS Querier to send its query via unicast
796 query via direct unicast, it SHOULD respond as it would for a
798 Unicast Responses". Since it is possible for a unicast query to be
807 always answered via unicast back to the Querier, since an answer sent
999 "unicast response" bit set. Since receiving a probe query gives a
1032 Except when a unicast response has been explicitly requested via the
1033 "unicast response" bit, Multicast DNS Responses MUST be sent to UDP
1113 directly back to the client, via unicast, to the query packet's
1114 source IP address and port. This unicast response MUST be a
1115 conventional unicast response as would be generated by a conventional
1116 unicast DNS server; for example, it MUST repeat the query ID and the
1119 The resource record TTL given in a legacy unicast response SHOULD NOT
1125 unicast responses sent to legacy clients to use the same high TTLs,
1130 Having sent this unicast response, if the Responder has not sent this
1140 to handle this correctly, responding by generating a unicast response
1234 with the "unicast response" bit set, to allow a defending host to
1235 respond immediately via unicast, instead of potentially having to
1239 old devices still in use that don't implement unicast responses.
1751 legacy unicast responses to UDP ports other than 5353.
2096 addressed to that port. However, incoming unicast UDP packets are
2098 This means that "QU" responses and other packets sent via unicast
2214 Attempts to remedy this for unicast DNS have been badly constrained
2267 limitation) the unicast DNS community settled on an extremely baroque
2413 In unicast response messages generated specifically in response to a
2414 particular (unicast or multicast) query, the Query ID MUST match the
2463 In legacy unicast response messages, the TC bit has the same meaning
2464 as in conventional unicast DNS: it means that the response was too
2529 qclass field is used to indicate that unicast responses are preferred
2581 and a conventional unicast DNS server on the same machine. If a
2582 conventional unicast DNS server wishes to implement mDNS as well,
2639 * defines a "unicast response" bit in the rrclass of query questions
2706 place of multiple unicast responses, when appropriate.
2757 unicast. Particularly in IPv6, where multicast addresses are