You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2010/09/13 17:55:32 UTC
[jira] Resolved: (TS-437) CONFIG proxy.config.dns.nameservers
should take into effect
[ https://issues.apache.org/jira/browse/TS-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom resolved TS-437.
------------------------------
Resolution: Duplicate
I think this is a duplicate of TS-313, please reopen if it isn't.
> CONFIG proxy.config.dns.nameservers should take into effect
> -----------------------------------------------------------
>
> Key: TS-437
> URL: https://issues.apache.org/jira/browse/TS-437
> Project: Traffic Server
> Issue Type: Bug
> Affects Versions: 2.1.2
> Environment: v2.1.2 and trunk
> Reporter: Zhao Yongming
>
> CONFIG proxy.config.dns.nameservers is the nameserver specified to TS, but it does not take into effect without setting of proxy.config.dns.round_robin_nameservers. please refer file DNS.cc: DNSProcessor::dns_init
> and even if setup proxy.config.dns.round_robin_nameservers, the nameserver setting from system default /etc/resolv.conf is take into active.
> as the SplitDNS have separated file to config, we should make some clear usage of this proxy.config.dns.nameservers and system default config.
> I think proxy.config.dns.nameservers is a setting to let TS use dedicate DNS server for it, and if all that hosts failed, we then use system default. if they specify proxy.config.dns.round_robin_nameservers too, then we use rr mode in all NS servers.
> any comments?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.