Lines Matching refs:responder

222    single responder, and at most one responder should respond to any
224    set, a responder MUST probe to verify that no other responder
467    in the case of overlayed subnets. If a responder receives a query
469    source address not apparently on the same subnet as the responder,
472    responder SHOULD elect to respond by multicast anyway, since it can
709    responder SHOULD usually respond with a unicast packet directed back
710    to the querier. If the responder has not multicast that record
711    recently (within one quarter of its TTL), then the responder SHOULD
757    RR TTL as known by the Multicast DNS Responder, the responder MUST
862    that the responder determines than an unsolicited announcement is
909    believe that it will be the only responder on the link with a
933    responder SHOULD delay its response by a random amount of time
1027    When possible, a responder SHOULD, for the sake of network
1029    Multicast DNS response packet. For example, when a responder has
1112    If a responder knows by other means, with absolute certainty, that
1114    already be in use by any other responder on the network, then it MAY
1283    responder to be capable of issuing identical answers on the network.
1396      resource record set owned solely by that responder, then this
1956    address record with the name "cheshire.local", then a responder
1966    programmatically-generated CNAME records. For example, if a responder
1969    removed, then the responder may issue a response containing two
2085    Known Answer records may be following shortly. A responder MAY choose