Lines Matching full:unicast
46 on the local link in the absence of any conventional unicast DNS
88 21. Summary of Differences Between Multicast DNS and Unicast DNS..38
434 All Multicast DNS responses (including responses sent via unicast)
446 spoof answer packets (perhaps unicast to the victim host) which the
462 * For responses sent to a unicast destination address, the source IP
477 then even if the query indicates that a unicast response is preferred
478 (see Section 6.5, "Questions Requesting Unicast Responses"), the
480 reasonably predict that a unicast response with an apparently
503 unicast directly to the address in question, but if this query is not
510 with or without an optional initial query unicast directly to the
557 is not exactly the same as unicast DNS, and should modify its
686 6.5 Questions Requesting Unicast Responses
705 willing to accept unicast responses instead of the usual multicast
706 responses. These questions requesting unicast responses are referred
710 When retransmitting a question more than once, the 'unicast response'
719 When receiving a question with the 'unicast response' bit set, a
720 responder SHOULD usually respond with a unicast packet directed back
726 Unicast replies are subject to all the same packet generation rules
957 Except when a unicast reply has been explicitly requested via the
958 "unicast reply" bit, Multicast DNS Responses MUST be sent to UDP port
990 8.1 Legacy Unicast Responses
996 directly back to the client, via unicast, to the query packet's
997 source IP address and port. This unicast response MUST be a
998 conventional unicast response as would be generated by a conventional
999 unicast DNS server; for example, it MUST repeat the query ID and the
1002 The resource record TTL given in a legacy unicast response SHOULD NOT
1007 stale data. Were unicast responses sent to legacy clients to use the
1012 Having sent this unicast response, if the Responder has not sent this
1563 legacy unicast responses to UDP ports other than 5353.
1576 6.5, "Questions Requesting Unicast Responses").
1916 Unicast DNS has been plagued by the lack of any support for non-US
1919 Attempts to remedy this for unicast DNS have been badly constrained
1961 limitation) the unicast DNS community settled on an extremely baroque
1978 other of the "Ascii Compatible Encodings" proposed for Unicast DNS
1984 The simple rules for case-insensitivity in Unicast DNS also apply in
2086 In unicast response messages generated specifically in response to a
2087 particular (unicast or multicast) query, the Query ID MUST match the
2127 In legacy unicast response messages, the TC bit has the same meaning
2128 as in conventional unicast DNS: it means that the response was too
2190 qclass field is used to indicate that unicast responses are preferred
2234 and a conventional unicast DNS server on the same machine. If a
2235 conventional unicast DNS server wishes to implement mDNS as well,
2270 21. Summary of Differences Between Multicast DNS and Unicast DNS
2274 Unicast DNS. There are of course necessary differences by virtue of
2294 * defines a "unicast response" bit in the rrclass of query questions
2346 place of multiple unicast responses, when appropriate.
2393 unicast. Particularly in IPv6, where multicast addresses are
