[
https://issues.apache.org/jira/browse/TS-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15422932#comment-15422932
]
Thomas Jackson commented on TS-2358:
------------------------------------
I'm not sure if this is still an issue-- haven't run into that problem. In
general SERVFAIL means the authoritive nameserver is having problems. So at
least in my infra trying another nameserver would return equally as broken
results-- although I do agree that it'd be good to try a different one (in case
one of your immediate upstream resolvers is having issues). I can add this to
my backlog of things to take a look at.
> DNS does not fail-over promptly for DNS server returning SERVFAIL
> -----------------------------------------------------------------
>
> Key: TS-2358
> URL: https://issues.apache.org/jira/browse/TS-2358
> Project: Traffic Server
> Issue Type: Bug
> Components: DNS
> Affects Versions: 3.2.5
> Reporter: William Bardwell
> Assignee: Thomas Jackson
> Fix For: sometime
>
> Attachments: ats.dns.txt
>
>
> If I have 2 dns servers listed in my resolv.conf and the first one is
> returning SERVFAIL for something that I try to lookup, ATS takes a long time
> to fail over, and won't do it for the first request to look something up.
> Using normal system commands (host, ping etc.) with the same resolv.conf work
> fine.
> I tried various config values with out much improvement. I could make it
> fail in 40sec instead of 60sec for the initial failure...
> debug logs will be attached, doing one DNS and then waiting a while and doing
> another. (Doing more before enough time has passed don't seem to help much.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
