d1f17fa7e0
Move all (almost all) Go files in middleware into their own packages. This makes for better naming and discoverability. Lot of changes elsewhere to make this change. The middleware.State was renamed to request.Request which is better, but still does not cover all use-cases. It was also moved out middleware because it is used by `dnsserver` as well. A pkg/dnsutil packages was added for shared, handy, dns util functions. All normalize functions are now put in normalize.go |
||
|---|---|---|
| .. | ||
| cache.go | ||
| cache_test.go | ||
| handler.go | ||
| item.go | ||
| item_test.go | ||
| README.md | ||
| setup.go | ||
cache
cache enables a frontend cache.
Syntax
cache [ttl] [zones...]
ttlmax TTL in seconds. If not specified, the TTL of the reply (SOA minimum or minimum TTL in the answer section) will be used.zoneszones 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. For the negative cache, the SOA's MinTTL value is used.
A cache mostly makes sense with a middleware that is potentially slow (e.g., a proxy that retrieves an answer), or to minimize backend queries for middleware like etcd. Using a cache with the file middleware essentially doubles the memory load with no conceivable increase of query speed.
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:
- coredns_cache_hit_count_total, and
- coredns_cache_miss_count_total
They both work on a per-zone basis and just count the hit and miss counts for each query.
Examples
cache 10
Enable caching for all zones, but cap everything to a TTL of 10 seconds.
proxy . 8.8.8.8:53
cache example.org
Proxy to Google Public DNS and only cache responses for example.org (or below).