History

Miek Gieben 12b2ff9740 Use logging (#1718 ) * update docs * plugins: use plugin specific logging Hooking up pkg/log also changed NewWithPlugin to just take a string instead of a plugin.Handler as that is more flexible and for instance the Root "plugin" doesn't implement it fully. Same logging from the reload plugin: .:1043 2018/04/22 08:56:37 [INFO] CoreDNS-1.1.1 2018/04/22 08:56:37 [INFO] linux/amd64, go1.10.1, CoreDNS-1.1.1 linux/amd64, go1.10.1, 2018/04/22 08:56:37 [INFO] plugin/reload: Running configuration MD5 = ec4c9c55cd19759ea1c46b8c45742b06 2018/04/22 08:56:54 [INFO] Reloading 2018/04/22 08:56:54 [INFO] plugin/reload: Running configuration MD5 = 9e2bfdd85bdc9cceb740ba9c80f34c1a 2018/04/22 08:56:54 [INFO] Reloading complete * update docs * better doc		2018-04-22 21:40:33 +01:00
..
handler.go	all: fix plugin import ordering (#1717 )	2018-04-22 08:34:35 +01:00
loadbalance.go	Use logging (#1718 )	2018-04-22 21:40:33 +01:00
loadbalance_test.go	all: fix plugin import ordering (#1717 )	2018-04-22 08:34:35 +01:00
OWNERS	Add OWNERS file (#1486 )	2018-02-08 10:55:51 +00:00
README.md	Manual pages (#1346 )	2018-01-04 12:53:07 +00:00
setup.go	Use logging (#1718 )	2018-04-22 21:40:33 +01:00

README.md

loadbalance

Name

loadbalance - acts as a round-robin DNS loadbalancer by randomizing the order of A and AAAA records in the answer.

Description

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

Load balance replies coming back from Google Public DNS:

. {
    loadbalance round_robin
    proxy . 8.8.8.8 8.8.4.4
}