status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Some tweaks to the documentation for a_record_limit

This commit is contained in:
Preetha 2018-03-08 11:23:07 -06:00 committed by GitHub
parent 57310a6446
commit 251cdb9c24
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
website/source/docs/agent/options.html.md
View File

@ -949,17 +949,15 @@ Consul will not enable TLS for the HTTP API unless the `https` port has been ass
* <a name="udp_answer_limit"></a><a href="#udp_answer_limit">`udp_answer_limit`</a> - Limit the number of
resource records contained in the answer section of a UDP-based DNS
response. Since this parameters is applied only for DNS queries of 512 bytes (without support of EDNS or
TCP, this setting is now replaced by <a href="#a_record_limit">`a_record_limit`</a> if randomization of
A/AAAA records is needed.
Its only usage is to limit the size of response of legacy DNS queries (not TCP, not EDNS), so you should
probably not use it.
response. This parameter applies only to UDP DNS queries that are less than 512 bytes. This setting is deprecated
and replaced in Consul 1.0.7 by <a href="#a_record_limit">`a_record_limit`</a>.
* <a name="a_record_limit"></a><a href="#a_record_limit">`a_record_limit`</a> - Limit the number of
resource records contained in the answser section of a A, AAAA or ANY DNS response (both TCP and UDP).
resource records contained in the answer section of a A, AAAA or ANY DNS response (both TCP and UDP).
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 `a_record_limit` (default: no limit). This limit does not apply to SRV records.
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