Thanks Jason. Is there anyway to query ATS to dump which resolvers it thinks it's using?
> On Mar 24, 2015, at 9:45, Jason Strongman <firstname.lastname@example.org
> if you can reproduce this on the fly, maybe try fleshing it out via a
> system call tracer.
> so stop ATS, then start ATS accompanied by a system call tracer..
> something like strace..
> make sure to pass the -f and '-s 10000' arguments to strace. -f
> follows child processes and -s defines the max string size to capture.
> once ATS starts reporting this DNS error, stop the trace, then run
> through the output file. you will then see where the DNS servers are
> defined. thats my brute force way of approaching things.
> On Sun, Mar 22, 2015 at 2:34 AM, Jason J. W. Williams
>> We just saw a bunch of "connection to DNS server 188.8.131.52 lost,
>> move to 184.108.40.206" on one of our ATS instances:
>> What confuses me is the server's resolv.conf is:
>> nameserver 127.0.0.1
>> nameserver 220.127.116.11
>> So neither 18.104.22.168 nor 22.214.171.124 should be involved. Any advice
>> is greatly appreciated.
>> (I checked the records.config and proxy.config.dns.resolv_conf is set
>> to the expected resolv.conf above)
>> Any advice is appreciated.