[jira] [Updated] (TS-1916) There are cases where hostdb does not reference a ttl of nameserver.

["James Peach (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TS-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Peach updated TS-1916:
----------------------------

    Fix Version/s: 3.5.0

The code looks like it is trying to do the right thing here. For more information, you should try enabling the "hostdb" diagnostic tag and posting the resulting logs here. Maybe [~allanca] has seen something like this?

Pushing out to 3.5.0.
                
> There are cases where hostdb does not reference a ttl of nameserver.
> --------------------------------------------------------------------
>
>                 Key: TS-1916
>                 URL: https://issues.apache.org/jira/browse/TS-1916
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: DNS
>            Reporter: ishioka keiichi
>             Fix For: 3.5.0
>
>
>    hostdb  is set as follows: 
>    CONFIG proxy.config.hostdb.ttl_mode INT 0
>    CONFIG proxy.config.hostdb.timeout INT 1
>    
>    If response of dns  the next,ATS queries the DNS every 30 seconds.
>    
>    $ dig foo.bar.com. A
>     ;; ANSWER SECTION:
>     foo.bar.com. 30 IN A 10.10.10.1
>     
>    If ttl is reduced as follow:, ATS will query the DNS every 10 seconds.
>   
>     $ dig foo.bar.com. A
>      ;; ANSWER SECTION:
>      foo.bar.com. 300 IN A 10.10.10.1 
>   
>    However, if it increased the value of ttl, ATS has continued to query DNS every 10 seconds.
>     
>     $ dig foo.bar.com. A
>      ;; ANSWER SECTION:
>      foo.bar.com. 300 IN A 10.10.10.1
>   
>   However, is adapted then HUP the traffic_server...
>   Why??
>   

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira