10db2a80df
* Add middleware/cache Add a caching middleware that caches nxdomain, nodata and successful responses. It differentiates between DNSSEC on normal DNS replies. Each reply is compress and scrubbed so it will fit the specific client asking for it. * first simple test, less exporting of stuff * more * Add middleware/cache Add a caching middleware that caches nxdomain, nodata and successful responses. It differentiates between DNSSEC on normal DNS replies. Each reply is compressed and scrubbed so it will fit the specific client asking for it. The TTL is decremented with the time spend in the cache. There is syntax that allows you to cap the TTL for all records, no matter what. This allows for a shortlived cache, just to absorb query peaks. +Tests * cache test infrastructure * Testing |
||
|---|---|---|
| .. | ||
| handler.go | ||
| loadbalance.go | ||
| loadbalance_test.go | ||
| README.md | ||
loadbalance
loadbalance acts as a round-robin DNS loadbalancer by randomizing A and AAAA records in the
message. See Wikipedia about the pros and cons
on this setup.
It will take care to sort any CNAMEs before any address records.
Syntax
loadbalance [policy]
policyis how to balance, the default is "round_robin"
Examples
loadbalance round_robin