Symptom
without the fix added by this DDTS, tracker probe counters are reset every 2 mins if DNS Cache Timeout is set to 2 mins (default value). This cause Tracker feature to function incorrectly - (Explanation) when there is a network issue that MUST lead to tracker down scenario, tracker will not go down. This is because tracker go down if probe failures are more than "Threshold" number configured. For example "Threshold = 5" and if each probes are sent 1 second apart, it takes 5+1 seconds to bring down the tracker. However if the DNS cache timeout is 2 mins, all counters are reset to 0 every 2mins. This cause Tracker never go down.
Conditions
DNS cache timeout set to 2 mins
Workaround
Set system DNS cache timeout to large value more than 15 mins
Further Problem Description
DNS cache timeout value under system template
CLI -> conf terminal->system -> time->dns cache timeout
