History

John Belamaric 9d41fa663c Do not muck with ordering of XFRs (#2329 ) The loadbalancer plugin reorders records. It was doing this for zone transfers - if you had a CNAME in the zone then your transfer would be broken because it would get put before the SOA record.		2018-11-21 08:38:19 +01:00
..
handler.go	all: fix plugin import ordering (#1717 )	2018-04-22 08:34:35 +01:00
loadbalance.go	Do not muck with ordering of XFRs (#2329 )	2018-11-21 08:38:19 +01:00
loadbalance_test.go	Do not muck with ordering of XFRs (#2329 )	2018-11-21 08:38:19 +01:00
log_test.go	Clean up tests logging (#1979 )	2018-07-19 16:23:06 +01:00
OWNERS	Add OWNERS file (#1486 )	2018-02-08 10:55:51 +00:00
README.md	Remove trailing whitespace (#1955 )	2018-07-09 08:08:02 -04:00
setup.go	plugin/loadbalance: add parse and tests (#1947 )	2018-07-06 21:49:21 +00:00
setup_test.go	plugin/loadbalance: add parse and tests (#1947 )	2018-07-06 21:49:21 +00:00

README.md

loadbalance

Name

loadbalance - randomize the order of A, AAAA and MX records.

Description

The loadbalance will act as a round-robin DNS loadbalancer by randomizing the order of A, AAAA, and MX 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, and only option, is "round_robin".

Examples

Load balance replies coming back from Google Public DNS:

. {
    loadbalance round_robin
    forward . 8.8.8.8 8.8.4.4
}