mirror of https://github.com/coredns/coredns.git synced 2025-11-01 02:33:14 -04:00

Files

Miek Gieben a412255ad1 middleware/cache: Add metrics (#132 )

Add prometheus metrics to the cache handler. This just used prometheus,
if the metrics middleware does not setup the handler, there is nobody
reading these metrics, but they are still reported. Seems the simplest
solution while keeping the whole middleware separation in tact.

2016-04-21 21:46:58 +01:00

cache_test.go

Cache (#126 )

2016-04-19 11:13:24 +01:00

cache.go

Cache (#126 )

2016-04-19 11:13:24 +01:00

handler.go

middleware/cache: Add metrics (#132 )

2016-04-21 21:46:58 +01:00

item_test.go

Cache (#126 )

2016-04-19 11:13:24 +01:00

item.go

Cache (#126 )

2016-04-19 11:13:24 +01:00

README.md

Updates to README

2016-04-19 10:26:29 +00:00

README.md

cache

cache enables a frontend cache.

Syntax

cache [ttl] [zones...]

ttl max TTL in seconds, if not specified the TTL of the reply (SOA minimum or minimum TTL in the answer section) will be used.
zones zones it should 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, i.e. a proxy that retrieves answer, or to minimize backend queries for middleware like etcd. Using a cache with the file middleware essentially doubles the memory load with no concealable increase of query speed.

The minimum TTL allowed on resource records is 5 seconds.

Examples

cache 10

Enable caching for all zones, but cap everything to a TTL of 10 seconds.

proxy . 8.8.8.8:53
cache miek.nl

Proxy to Google Public DNS and only cache responses for miek.nl (or below).