Lines Matching refs:resolver

110    servers to smart phones. This includes resolver libraries on different
116 validating resolver, how to sign DNS zone data, and other operational
206 (a.k.a. a *validating resolver*) asks for additional resource
210 validating resolver performs cryptographic computation to verify the
215 the validating resolver reaches a key that it trusts. In the ideal,
231     the validating resolver follows standard DNS protocol to track down
234     resolver, the outgoing query has a bit set indicating it wants
242 3.  The validating resolver requires cryptographic keys to be able to verify the
248     resolver can use this information to verify the answers received in
264 5.  The validating resolver asks the parent (``.org``) for the
268     point, the validating resolver compares this to the answer it received
279 7.  The validating resolver asks the ``.org`` authoritative name server for
283     keys and signatures). At this point, the validating resolver can
286 9.  The validating resolver asks root (``.org``'s parent) for the verifiable
290     on ``.org``. The validating resolver uses this information
300 11. The validating resolver asks the root name server for its cryptographic
304     resolver can verify the answer(s) received in #10.
315 each validating resolver would only have to trust one entity, that is,
316 the root name server. The validating resolver already has the root key
318 after the answer in #12 is received, the validating resolver compares it