Lines Matching refs:queries
17 Resolvers handle :ref:`recursive user queries <recursive_query>` and provide
18 complete answers; that is, they issue one or more :ref:`iterative queries
24 information results in a new series of queries to the DNS hierarchy.
48 queries<iterative_query>` (2) to the DNS hierarchy to obtain the answer. The
87 .. Attention:: While the diagram above shows **recursive user queries**
90 IPs that can send such queries, the resolver is termed an **open resolver**.
133 Resolvers are configured to send :ref:`iterative queries<iterative_query>` to
139 queries (mapping an IP address to a name). If the private IP addresses are not
151 Mail systems in particular perform reverse DNS queries as a first-line spam
190 // Two corporate subnets we wish to allow queries from
206 // recursive queries only allowed from these ips
285 All other recursive queries will result in access to the DNS hierarchy to
293 This forwarding resolver configuration forwards all recursive queries, other
298 from which it will accept recursive queries.
306 // Two corporate subnets we wish to allow queries from
322 // recursive queries only allowed from these ips
329 // this defines the addresses of the resolvers to which queries will be forwarded
334 // indicates all queries will be forwarded other than for defined zones
402 All other recursive queries will be forwarded to resolve the query.
409 This forwarding resolver configuration only forwards recursive queries for the
411 other recursive queries, other than those for the defined zones and those for
415 those IPs from which it will accept recursive queries.
420 // Two corporate subnets we wish to allow queries from
436 // recursive queries only allowed from these ips
500 // which queries for this zone will be forwarded
505 // indicates all queries for this zone will be forwarded
532 All other recursive queries will result in access to the DNS hierarchy to
558 When a resolver queries for these records, BIND rotates them and