mirror of https://github.com/coredns/coredns.git synced 2025-12-04 01:15:11 -05:00

Files

Miek Gieben 219bfd0493 middleware/metrics: cleanup (#355 )

* middleware/metrics: add more metrics

middleware/cache:
Add metrics for number of elements in the cache. Also export the total
size. Update README to detail the new metrics.

middleware/metrics

Move metrics into subpackage called "vars". This breaks the import
cycle and is cleaner. This allows vars.Report to be used in the
the dnsserver to log refused queries.

middleware/metrics: tests

Add tests to the metrics framework. The metrics/test subpackage allows
scraping of the local server. Do a few test scrape of the metrics that
are defined in the metrics middleware.

This also allows metrics integration tests to check if the caching and
dnssec middleware export their metrics correctly.

* update README

* typos

* fix tests

2016-10-26 10:01:52 +01:00

handler.go

middleware/metrics: cleanup (#355 )

2016-10-26 10:01:52 +01:00

loadbalance_test.go

Cleanup: put middleware helper functions in pkgs (#245 )

2016-09-07 11:10:16 +01:00

loadbalance.go

Doc: add package docs (#296 )

2016-09-25 08:39:20 +01:00

README.md

docs: rewrite using manpage style (#327 )

2016-10-10 20:13:22 +01:00

setup.go

Cleanups and tests (#272 )

2016-09-19 11:26:00 +01:00

README.md

loadbalance

loadbalance acts as a round-robin DNS loadbalancer by randomizing the order of A and AAAA records in the answer. See Wikipedia about the pros and cons on this setup.

It will take care to sort any CNAMEs before any address records, because some stub resolver implementations (like glibc) are particular about that.

Syntax

loadbalance [POLICY]

POLICY is how to balance, the default is "round_robin"

Examples

loadbalance round_robin