Use industry jargon re: DNS round-robin

s/randomized DNS round-robin/round-robin DNS/
pull/1712/head
Sean Chittenden 2016-03-29 23:07:42 -07:00
parent c2d4354563
commit fcee9779ae
1 changed files with 4 additions and 5 deletions

View File

@ -514,11 +514,10 @@ Consul will not enable TLS for the HTTP API unless the `https` port has been ass
[RFC 3484 Section 6](https://tools.ietf.org/html/rfc3484#section-6) Rule 9 [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 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 therefore never random), clients may need to set this value to `1` to
preserve randomized DNS round-robin (note: preserve round-robin DNS (note: [https://tools.ietf.org/html/rfc3484](RFC
[https://tools.ietf.org/html/rfc3484](RFC 3484) has been obsoleted by 3484) has been obsoleted by [RFC 6724](https://tools.ietf.org/html/rfc6724)
[RFC 6724](https://tools.ietf.org/html/rfc6724) and as a result it should and as a result it should be increasingly uncommon to need to change this
be increasingly uncommon to need to change this value with modern value with modern resolvers).
resolvers).
* <a name="domain"></a><a href="#domain">`domain`</a> Equivalent to the * <a name="domain"></a><a href="#domain">`domain`</a> Equivalent to the
[`-domain` command-line flag](#_domain). [`-domain` command-line flag](#_domain).