History

Miek Gieben 24176a97e6 Move to CODEOWNERS (#3489 ) * Move to CODEOWNERS No change in who own what; just a move to CODEOWNERS. This allows dreck cleanups. Added .dreck.yaml for alias and exec. Fixes: #3486 Signed-off-by: Miek Gieben <miek@miek.nl> * stickler bot Signed-off-by: Miek Gieben <miek@miek.nl> * sort the file Signed-off-by: Miek Gieben <miek@miek.nl>		2019-11-29 13:17:05 +00:00
..
handler.go	fix mis-spelling (#3310 )	2019-09-26 13:19:45 +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
README.md	Update README.md (#3242 )	2019-09-05 19:41:13 +01:00
setup.go	all: simply registering plugins (#3287 )	2019-09-20 08:02:30 +01:00
setup_test.go	Update Caddy to 1.0.1, and update import path (#2961 )	2019-07-03 09:04:47 +08:00

README.md

loadbalance

Name

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

Description

The loadbalance will act as a round-robin DNS load balancer by randomizing the order of A, AAAA, and MX records in the answer.

See Wikipedia about the pros and cons of 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
}