Lines Matching refs:unicast

44    on the local link in the absense of any conventional unicast DNS
413    All Multicast DNS responses (including responses sent via unicast)
421    spoof answer packets (perhaps unicast to the victim host) which the
434    Multicast DNS where hosts issue unicast queries directed at Multicast
450    unicast directly to the address in question, but if this query is not
457    with or without an optional initial query unicast directly to the
500    is not exactly the same as unicast DNS, and should modify its
647    willing to accept unicast responses instead of the usual multicast
648    responses. These questions requesting unicast responses are referred
652    When retransmitting a question more than once, the 'unicast response'
661    When receiving a question with the 'unicast response' bit set, a
662    responder SHOULD usually respond with a unicast packet directed back
859    Except when a unicast reply has been explicitly requested via the
860    "unicast reply" bit, Multicast DNS Responses MUST be sent to UDP port
896    directly back to the client, via unicast, to the query packet's
897    source IP address and port. This unicast response MUST be a
898    conventional unicast response as would be generated by a conventional
899    unicast DNS server; for example, it must repeat the query ID and the
902    The resource record TTL given in a unicast response SHOULD NOT be
907    data. Were unicast responses sent to legacy clients to use the same
912    Having sent this unicast response, if the Responder has not sent this
1552    records in a response packet sent in legacy unicast responses to UDP
1926    In unicast response messages generated specifically in response to a
1927    particular (unicast or multicast) query, the Query ID MUST match the
1967    In legacy unicast response messages, the TC bit has the same meaning
1968    as in conventional unicast DNS: it means that the response was too
2059      and a conventional unicast DNS server on the same machine. If a
2060      conventional unicast DNS server wishes to implement mDNS as well,
2117    * defines a "unicast response" bit in the rrclass of query questions
2234    unicast. Particularly in IPv6, where multicast addresses are