Lines Matching full:unicast
46 on the local link in the absence of any conventional unicast DNS
87 22. Summary of Differences Between Multicast DNS and Unicast DNS...46
442 All Multicast DNS responses (including responses sent via unicast)
454 spoof answer packets (perhaps unicast to the victim host) which the
477 * For responses sent to a unicast destination address, the source IP
492 then even if the query indicates that a unicast response is preferred
493 (see Section 6.5, "Questions Requesting Unicast Responses"), the
495 reasonably predict that a unicast response with an apparently
559 configured unicast DNS server address that would otherwise be used.
580 is not exactly the same as unicast DNS, and should modify its
713 6.5 Questions Requesting Unicast Responses
736 question as the "unicast response" bit. When this bit is set in a
737 question, it indicates that the Querier is willing to accept unicast
739 requesting unicast responses are referred to as "QU" questions, to
761 When receiving a question with the "unicast response" bit set, a
762 responder SHOULD usually respond with a unicast packet directed back
775 answering a probe question with the "unicast response" bit set, the
776 responder should always generate the requested unicast response, but
782 unicast replies are subject to all the same packet generation rules
804 6.7 Direct Unicast Queries to port 5353
807 makes sense for a Multicast DNS Querier to send its query via unicast
809 query via direct unicast, it SHOULD respond as it would for a
811 Unicast Responses". Since it is possible for a unicast query to be
820 always answered via unicast back to the Querier, since an answer sent
1016 "unicast response" bit set. Since receiving a probe query gives a
1049 Except when a unicast response has been explicitly requested via the
1050 "unicast response" bit, Multicast DNS Responses MUST be sent to UDP
1126 8.3 Legacy Unicast Responses
1132 directly back to the client, via unicast, to the query packet's
1133 source IP address and port. This unicast response MUST be a
1134 conventional unicast response as would be generated by a conventional
1135 unicast DNS server; for example, it MUST repeat the query ID and the
1138 The resource record TTL given in a legacy unicast response SHOULD NOT
1144 unicast responses sent to legacy clients to use the same high TTLs,
1149 Having sent this unicast response, if the Responder has not sent this
1159 to handle this correctly, responding by generating a unicast response
1255 with the "unicast response" bit set, to allow a defending host to
1256 respond immediately via unicast, instead of potentially having to
1260 old devices still in use that don't implement unicast responses.
1781 legacy unicast responses to UDP ports other than 5353.
1794 6.5, "Questions Requesting Unicast Responses").
1923 Conventional Unicast DNS seeks to provide a single unified namespace,
2116 16.1 Receiving Unicast Responses
2132 addressed to that port. However, incoming unicast UDP packets are
2134 This means that "QU" responses and other packets sent via unicast
2249 Unicast DNS has been plagued by the lack of any support for non-US
2252 Attempts to remedy this for unicast DNS have been badly constrained
2306 limitation) the unicast DNS community settled on an extremely baroque
2323 other of the "Ascii Compatible Encodings" proposed for Unicast DNS
2329 The simple rules for case-insensitivity in Unicast DNS also apply in
2454 In unicast response messages generated specifically in response to a
2455 particular (unicast or multicast) query, the Query ID MUST match the
2505 In legacy unicast response messages, the TC bit has the same meaning
2506 as in conventional unicast DNS: it means that the response was too
2572 qclass field is used to indicate that unicast responses are preferred
2625 and a conventional unicast DNS server on the same machine. If a
2626 conventional unicast DNS server wishes to implement mDNS as well,
2660 22. Summary of Differences Between Multicast DNS and Unicast DNS
2664 Unicast DNS. There are of course necessary differences by virtue of
2684 * defines a "unicast response" bit in the rrclass of query questions
2752 place of multiple unicast responses, when appropriate.
2804 unicast. Particularly in IPv6, where multicast addresses are
