History

Miek Gieben d35394a8df middleware/caching: don't set TTL on OPT When setting the TTL on all RR in the message we would also do this for the OPT RR. This is wrong as the OPT RR does not have a TTL.		2016-05-22 19:43:58 +01:00
..
cache.go	middleware/caching: don't set TTL on OPT	2016-05-22 19:43:58 +01:00
cache_test.go	Add middleware/dnssec (#133 )	2016-04-26 17:57:11 +01:00
handler.go	Add middleware/dnssec (#133 )	2016-04-26 17:57:11 +01:00
item.go	middleware/caching: don't set TTL on OPT	2016-05-22 19:43:58 +01:00
item_test.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).