You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/12/19 02:07:07 UTC
[jira] [Commented] (TS-428) New DNS configuration option
[ https://issues.apache.org/jira/browse/TS-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852423#comment-13852423 ]
ASF subversion and git services commented on TS-428:
----------------------------------------------------
Commit 44a8614853f2d622861aa3ee434b1eb9fe255bb7 in branch refs/heads/master from [~mlibbey]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=44a8614 ]
[TS-428] Add proxy.config.dns.validate_query_name to drecords.config doc from Jira notes.
> New DNS configuration option
> ----------------------------
>
> Key: TS-428
> URL: https://issues.apache.org/jira/browse/TS-428
> Project: Traffic Server
> Issue Type: New Feature
> Components: Documentation
> Reporter: Leif Hedstrom
> Fix For: Docs
>
>
> There is a new DNS configuration option, from the records.config file:
> # This provides additional resilience against DNS forgery, particularly in
> # forward or transparent proxies, but requires that the resolver populates
> # the queries section of the response properly.
> CONFIG proxy.config.dns.validate_query_name INT 0
> This setting is disabled by default, enabling it will force us to validate the name in response from the resolver to make sure it matches the request we made. This could potentially break if the resolver does not populate the queries section with the requested name.
> Enabling this option is highly recommended, particularly for running ATS in a forward or transparent proxy configuration.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)