From fe0a7283d3789a9bb6b44619499e43b4f692819c Mon Sep 17 00:00:00 2001 From: Sean Chittenden Date: Tue, 29 Mar 2016 23:48:22 -0700 Subject: [PATCH] Reword `udp_answer_limit` for the better. --- website/source/docs/agent/options.html.markdown | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/website/source/docs/agent/options.html.markdown b/website/source/docs/agent/options.html.markdown index 669fd0e1a7..2b8c6b81b5 100644 --- a/website/source/docs/agent/options.html.markdown +++ b/website/source/docs/agent/options.html.markdown @@ -509,15 +509,17 @@ Consul will not enable TLS for the HTTP API unless the `https` port has been ass * `udp_answer_limit` - Limit the number of resource records contained in the answer section of a UDP-based DNS - response. The default number of resource records returned is `3`. In - environments where + response. When answering a question, Consul will use the complete list of + matching hosts, shuffle the list randomly, and then limit the number of + answers to `udp_answer_limit` (default `3`). In environments where [RFC 3484 Section 6](https://tools.ietf.org/html/rfc3484#section-6) Rule 9 is implemented and enforced (i.e. DNS answers are always sorted and therefore never random), clients may need to set this value to `1` to - preserve round-robin DNS (note: [https://tools.ietf.org/html/rfc3484](RFC - 3484) has been obsoleted by [RFC 6724](https://tools.ietf.org/html/rfc6724) - and as a result it should be increasingly uncommon to need to change this - value with modern resolvers). + preserve the expected randomized distribution behavior (note: + [https://tools.ietf.org/html/rfc3484](RFC 3484) has been obsoleted by + [RFC 6724](https://tools.ietf.org/html/rfc6724) and as a result it should + be increasingly uncommon to need to change this value with modern + resolvers). * `domain` Equivalent to the [`-domain` command-line flag](#_domain).