Lines Matching full:are

28 The available options are:
44 There are several commands that the server understands.
69 worked on are kept and continue, but with the new config options.
77 Zones loaded from disk (authority zones and RPZ zones) are included in such
80 Options that can be changed are for
169 Locks are acquired, but items are updated in sequence, so it is possible
172 old config and forwards from the new config. The stubs and forwards are
173 updated at the same time, so that they are viewed consistently, either old
175 microseconds instead of 0.3 milliseconds during which the worker threads are
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
198 When there are changes to the config tags, from the \fBdefine\-tag\fR option,
200 queries are dropped.
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
219 daemon release the file it is logging to.  If you are using syslog it will
225 Statistics are printed with one [name]: [value] per line.
253 domain names below the removed name), NOERROR nodata answers are the
306 The rrsets and key entries are removed so that new lookups will be performed.
308 The entries are set to expired in the implementation of this command (so,
325 Drop the queries that are worked on.  Stops working on the queries that the
335 This prints the queries from the first thread, and not queries that are
350 effect if set this way, the new values are not written to the config file,
351 not all options are supported.  This is different from the set_option call
354 The values that work are: statistics\-interval, statistics\-cumulative,
368 one on each line, is printed.  The options are shown from the config file
375 List the stub zones in use.  These are printed one by one to the output.
379 List the forward zones in use.  These are printed zone by zone to the output.
385 List the local zones in use.  These are printed one per line with zone type.
388 List the local data RRs in use.  The resource records are printed.
434 If one or more IPv4 or IPv6 addresses are given, those are then used to forward
439 used.  The config file is not changed, so after a reload these changes are
440 gone.  Other forward zones from the config file are not affected by this command.
443 List the domains that are ratelimited.  Printed one per line with current
450 List the ip addresses that are ratelimited.  Printed one per line with current
453 ips are dropped before checking the cache.
456 List the auth zones that are configured.  Printed one per line with a status,
458 zones are included.
469 is started, where the masters are probed to see if they have an updated zone
508 secrets are used to create DNS Cookies, but verification of a DNS Cookie
513 When there are no cookie secrets configured yet, the <secret> is added as
613 number of queries that are dropped because they waited in the UDP socket buffer
643 … recursive processing. Note that queries that were answered from the cache are not in this average.
655 buffers are full.
765 Memory in bytes in used by the TCP and TLS stream wait buffers.  These are
784 There are 40 buckets, with bucket sizes doubling.
789 queries were received, thus =0 entries are omitted for brevity.
817 These are also counted in num.query.tcp, because TLS uses TCP.
820 Number of TLS session resumptions, these are queries over TLS towards
825 These are also counted in num.query.tcp and num.query.tls, because HTTPS
830 These are also counted in num.query.tls, because TLS is used for these queries.
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
858 hence are considered a query replay.
868 These queries are also included in the num.answer.rcode.NOERROR number.
892 Some low level of late answers and delayed duplicates are to be expected
903 The number of items in the infra cache.  These are IP addresses with their
907 The number of items in the key cache.  These are DNSSEC keys, one item
912 number of hashes that are identical when a new element is inserted in the
914 with the performance of the hash table, hash values are incorrect or malicious.
918 number of hashes that are identical when a new element is inserted in the
920 with the performance of the hash table, hash values are incorrect or malicious.
923 The number of items in the shared secret cache. These are precomputed shared
926 shared secret when multiple dnscrypt queries are sent from the same client.
938 the internet, but are now answered from the auth zone.
942 These queries are from downstream clients, and have had an answer from
947 These queries would otherwise have been sent to the internet, but are now
952 These queries would otherwise have been sent to the internet, but are now
959 Number of queries answered from the edns client subnet cache.  These are
965 These are counted as cachemiss by the main counters, but hit the cachedb
970 Possible actions are: nxdomain, nodata, passthru, drop, tcp\-only, local\-data,