Mirrors/coredns
1
0
Fork 0
mirror of https://github.com/coredns/coredns.git synced 2025-11-01 02:33:14 -04:00
Code Issues Packages Projects Releases Wiki Activity

middleware/cache: rename categories (#321)

Browse Source 
Rename: positive -> success
negative -> denial

There is a third (unused category) which is error. Start using these
new in the caching middleware and later in the logging middleware.
This commit is contained in:
Miek Gieben
2016-10-08 15:12:28 +01:00
committed by GitHub
parent 6cf14746ad
commit b44d82839f
5 changed files with 21 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
middleware/cache/README.md vendored
View File

@@ -9,7 +9,7 @@ cache [ttl] [zones...]
~~~
* `ttl` max TTL in seconds. If not specified, the maximum TTL will be used which is 1 hour for
positive responses and half an hour for negative ones.
noerror responses and half an hour for denial of existence ones.
* `zones` zones it should cache for. If empty, the zones from the configuration block are used.
Each element in the cache is cached according to its TTL (with `ttl` as the max).
@@ -20,17 +20,19 @@ Or if you want more control:
~~~ txt
cache [ttl] [zones...] {
postive capacity [ttl]
negative capacity [ttl]
noerror capacity [ttl]
denial capacity [ttl]
}
~~~
* `ttl` and `zones` as above.
* `positive`, override the settings for caching positive responses, capacity indicates the maximum
* `success`, override the settings for caching noerror responses, capacity indicates the maximum
number of packets we cache before we start evicting (LRU). Ttl overrides the cache maximum TTL.
* `negative`, override the settings for caching negative responses, capacity indicates the maximum
* `denial`, override the settings for caching denial of existence responses, capacity indicates the maximum
number of packets we cache before we start evicting (LRU). Ttl overrides the cache maximum TTL.
There is a third category (`error`) but those responses are never cached.
The minimum TTL allowed on resource records is 5 seconds.
If monitoring is enabled (via the `prometheus` directive) then the following extra metrics are added: