Lines Matching refs:resolver

20 an error), a resolver passes the answer to the user and places it in its cache.
22 resolver's cache until the :term:`TTL` of the cached answer has expired, when
33 .. figure:: resolver-forward.png
38 1. End-user systems are all distributed with a local **stub resolver** as a
42 2. A stub resolver has limited functionality; specifically, it cannot follow
43    :ref:`referrals<referral>`. When a stub resolver receives a request for a
46    a locally configured resolver (5), which may have the answer available in
49    resolver to which the local system sends the user query is configured, for
53 3. Alternatively, the user query can be sent to a **forwarding resolver** (4).
55    appear to be acting as a simple pass-though and, like the stub resolver,
56    require a full-service resolver (5). However, forwarding resolvers can be
60       resolver (4) results in two messages - the query and its answer. The resolver
63       cost (if the link is tariffed). Additionally, since the forwarding resolver is
71       forwarding resolver, which can be configured to stream DNS traffic as desired
75       to stream DNS traffic using a forwarding resolver structure.  The forwarding
76       resolver (4) may be configured, for example, to handle all in-domain traffic
77       (relatively safe) and forward all external traffic to a **hardened** resolver
84    resolver (5), or to only forward selective traffic (5) while directly
90    IPs that can send such queries, the resolver is termed an **open resolver**.
97    configuring a **closed resolver**. The resolver samples given here all
140 defined in one or more reverse-mapped zone file(s), the resolver sends them to
153 configuration files given here for both the resolver and the forwarding
154 resolver provide a reverse-mapping zone file for the private IP address
184 The resolver provides :ref:`recursive query support<recursive_query>` to a defined set of IP addres…
185 It is therefore a **closed** resolver and cannot be used in wider network attacks.
189         // resolver named.conf file
271 As a reminder, the configuration of this resolver does **not** access the DNS
293 This forwarding resolver configuration forwards all recursive queries, other
295 its cache, to a full-service resolver at the IP address 192.168.250.3, with an
296 alternative at 192.168.230.27. The forwarding resolver will cache all responses
389 As a reminder, the configuration of this forwarding resolver does **not**
409 This forwarding resolver configuration only forwards recursive queries for the
412 which the answer is already in its cache, are handled by this resolver. The
413 forwarding resolver will cache all responses from both the public network and
516 As a reminder, the configuration of this resolver does **not** access the DNS
558 When a resolver queries for these records, BIND rotates them and