[ 
https://issues.apache.org/jira/browse/TS-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908835#action_12908835
 ] 

Zhao Yongming commented on TS-437:
----------------------------------

here is my config and debug info:
zym6400 trafficserver # grep dns records.config
CONFIG proxy.config.http.no_dns_just_forward_to_parent INT 0
CONFIG proxy.config.dns.search_default_domains INT 1
CONFIG proxy.config.dns.splitDNS.enabled INT 0
CONFIG proxy.config.dns.splitdns.def_domain STRING NULL
CONFIG proxy.config.dns.url_expansions STRING NULL
CONFIG proxy.config.dns.round_robin_nameservers INT 1
CONFIG proxy.config.dns.nameservers STRING 8.8.8.8
CONFIG proxy.config.dns.validate_query_name INT 0
CONFIG proxy.config.dns.proxy.enabled INT 0
CONFIG proxy.config.dns.proxy_port INT 53
CONFIG proxy.config.diags.debug.tags STRING dns*


[Sep 13 23:02:52.341] Server {46962643572000} NOTE: cache clustering enabled
[Sep 13 23:02:52.349] Server {46962643572000} DEBUG: (dns) ink_dns_init: called 
with init_called = 0
[Sep 13 23:02:52.358] Server {46962643572000} DEBUG: (dns) localhost=zym6400
[Sep 13 23:02:52.358] Server {46962643572000} DEBUG: (dns) Round-robin 
nameservers = 1
[Sep 13 23:02:52.358] Server {46962643572000} DEBUG: (dns) Nameserver list 
specified "8.8.8.8"
[Sep 13 23:02:52.358] Server {46962643572000} DEBUG: (dns) Nameserver list - 
parsing "8.8.8.8"
[Sep 13 23:02:52.358] Server {46962643572000} DEBUG: (dns) Adding nameserver 
8.8.8.8:53 to nameserver list
[Sep 13 23:02:52.359] Server {46962643572000} NOTE: cache clustering enabled
[Sep 13 23:02:52.417] Server {46962643572000} NOTE: logging initialized[7], 
logging_mode = 3
[Sep 13 23:02:52.422] Server {46962643572000} NOTE: traffic server running
[Sep 13 23:02:52.422] Server {46962643572000} DEBUG: (dns) 
DNSHandler::startEvent: on thread0
[Sep 13 23:02:52.422] Server {46962643572000} DEBUG: (dns) open_con: opening 
connection 127.0.0.1:53
[Sep 13 23:02:52.422] Server {46962643572000} DEBUG: (dns) random port = 19138
[Sep 13 23:02:52.422] Server {46962643572000} DEBUG: (dns) opening connection 
127.0.0.1:53 SUCCEEDED for 0
[Sep 13 23:02:52.422] Server {46962643572000} DEBUG: (dns) open_con: opening 
connection 74.82.42.42:53
[Sep 13 23:02:52.422] Server {46962643572000} DEBUG: (dns) random port = 41153
[Sep 13 23:02:52.422] Server {46962643572000} DEBUG: (dns) opening connection 
74.82.42.42:53 SUCCEEDED for 1
[Sep 13 23:02:52.422] Server {46962643572000} DEBUG: (dns) open_con: opening 
connection 192.168.199.1:53
[Sep 13 23:02:52.422] Server {46962643572000} DEBUG: (dns) random port = 17828
[Sep 13 23:02:52.422] Server {46962643572000} DEBUG: (dns) opening connection 
192.168.199.1:53 SUCCEEDED for 2

[Sep 13 23:02:52.832] Server {46962643572000} NOTE: cache enabled


> 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.

Reply via email to