Lines Matching full:queries
64 Reload the server, but keep downtime to a minimum, so that user queries
68 impact the service of user queries. The cache is kept. Also user queries
111 num-queries-per-thread,
118 max-reuse-tcp-queries,
192 The '+d' option makes the reload drop queries that the worker threads are
193 working on. This is like flush_requestlist. Without it the queries are kept
194 so that users keep getting answers for those queries that are currently
195 processed. The drop makes it so that queries during the life time of the
200 queries are dropped.
202 queries. If the number of tags is increased in the newly loaded config, by
208 The old information is kept with the query until the queries are done.
209 This is gone when those queries are resolved and finished, or it is possible
325 Drop the queries that are worked on. Stops working on the queries that the
327 those queries, probably making those users request again later.
328 Useful to make the server restart working on queries with new settings,
332 Show what is worked on. Prints all queries that the server is currently
335 This prints the queries from the first thread, and not queries that are
355 do\-not\-query\-localhost, harden\-short\-bufsize, harden\-large\-queries,
357 harden\-referral\-path, prefetch, prefetch\-key, log\-queries,
426 Without arguments the current list of addresses used to forward all queries
435 queries to. The addresses must be separated with spaces. With '@port' the
446 domains return an error for uncached (new) queries, but cached queries work
559 .I threadX.num.queries
560 number of queries received by thread
563 number of queries rate limited by thread
566 number of queries with a valid DNS Cookie by thread
569 number of queries with a client part only DNS Cookie by thread
572 number of queries with an invalid DNS Cookie by thread
575 number of queries removed due to discard-timeout by thread
578 number of queries removed due to wait-limit by thread
581 number of queries that were successfully answered using a cache lookup
584 number of queries that needed recursive processing
587 number of queries that were encrypted and successfully decapsulated by dnscrypt.
590 number of queries that were requesting dnscrypt certificates.
593 number of queries received on dnscrypt port that were cleartext and not a
613 number of queries that are dropped because they waited in the UDP socket buffer
621 The number of replies sent to queries that needed recursive processing. Could be smaller than threadX.num.cachemiss if due to timeouts no replies were sent for some queries.
630 Number of requests in the request list that were overwritten by newer entries. This happens if there is a flood of queries that recursive processing and the server has a hard time.
633 Queries that were dropped because the request list was full. This happens if a flood of queries need recursive processing, and the server can not keep up.
636 Current size of the request list, includes internally generated queries (such
637 as priming queries and glue lookups).
640 Current size of the request list, only the requests from client queries.
643 Average time it took to answer queries that needed recursive processing. Note that queries that were answered from the cache are not in this average.
646 The median of the time it took to answer queries that needed recursive
647 processing. The median means that 50% of the user queries were answered in
648 less than this time. Because of big outliers (usually queries to non
657 .I total.num.queries
770 queries waiting for request stream completion.
778 information, queries read and responses written back to the clients.
782 recursive queries whose reply time fit between the lower and upper bound.
787 The total number of queries over all threads with query type A.
789 queries were received, thus =0 entries are omitted for brevity.
792 Number of queries with query types 256\-65535.
795 The total number of queries over all threads with query class IN (internet).
801 The total number of queries over all threads with query opcode QUERY.
805 Number of queries that were made using TCP towards the Unbound server.
808 Number of queries that the Unbound server made using TCP outgoing towards
812 Number of queries that the Unbound server made using UDP outgoing towards
816 Number of queries that were made using TLS towards the Unbound server.
820 Number of TLS session resumptions, these are queries over TLS towards
824 Number of queries that were made using HTTPS towards the Unbound server.
829 Number of queries that were made using QUIC towards the Unbound server.
830 These are also counted in num.query.tls, because TLS is used for these queries.
833 Number of queries that were made using IPv6 towards the Unbound server.
836 The number of queries that had the RD flag set in the header.
838 Note that queries with flags QR, AA or TC may have been rejected
842 number of queries that had an EDNS OPT record present.
845 number of queries that had an EDNS OPT record with the DO (DNSSEC OK) bit set.
846 These queries are also included in the num.query.edns.present number.
849 The number of queries that are turned away from being send to nameserver due to
853 The number of dnscrypt queries that did not find a shared secret in the cache.
857 The number of dnscrypt queries that found a nonce hit in the nonce cache and
861 The number of answers to queries, from cache or from recursion, that had the
865 The number of answers to queries that had the pseudo return code nodata.
868 These queries are also included in the num.answer.rcode.NOERROR number.
885 .I unwanted.queries
886 Number of queries that were refused or dropped because they failed the
926 shared secret when multiple dnscrypt queries are sent from the same client.
930 dnscrypt queries replay. The client nonce must be unique for each client public
936 The number of queries answered from auth\-zone data, upstream queries.
937 These queries would otherwise have been sent (with fallback enabled) to
941 The number of queries for downstream answered from auth\-zone data.
942 These queries are from downstream clients, and have had an answer from
946 The number of queries answered using cached NSEC records with NODATA RCODE.
947 These queries would otherwise have been sent to the internet, but are now
951 The number of queries answered using cached NSEC records with NXDOMAIN RCODE.
952 These queries would otherwise have been sent to the internet, but are now
956 Number of queries that got an answer that contained EDNS client subnet data.
959 Number of queries answered from the edns client subnet cache. These are
964 Number of queries answered from the external cache of cachedb.
969 Number of queries answered using configured RPZ policy, per RPZ action type.