Editorialize the comment re: UDPAnswerLimit

Prodded by: slackpad & fusiondog
This commit is contained in:
Sean Chittenden 2016-03-30 01:15:40 -07:00
parent 5ba7e74bb8
commit 19721f5c3d

View File

@ -81,11 +81,15 @@ type DNSConfig struct {
// Records returned in the ANSWER section of a DNS response. This is
// not normally useful and will be limited based on the querying
// protocol, however systems that implemented §6 Rule 9 in RFC3484
// may want to set this to 1 in order to achieve round-robin DNS.
// may want to set this to `1` in order to subvert §6 Rule 9 and
// re-obtain the effect of randomized resource records (i.e. each
// answer contains only one IP, but the IP changes every request).
// RFC3484 sorts answers in a deterministic order, which defeats the
// purpose of round-robin DNS. This RFC has been obsoleted by
// RFC6724, however a large number of Linux hosts using glibc(3)
// implemented §6 Rule 9 (e.g. CentOS 5-6, Debian Squeeze, etc).
// purpose of randomized DNS responses. This RFC has been obsoleted
// by RFC6724 and restores the desired behavior of randomized
// responses, however a large number of Linux hosts using glibc(3)
// implemented §6 Rule 9 and may need this option (e.g. CentOS 5-6,
// Debian Squeeze, etc).
UDPAnswerLimit int `mapstructure:"udp_answer_limit"`
// MaxStale is used to bound how stale of a result is