UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.110 Safari/537.36

Example URL:

Steps to reproduce the problem:
Have several DNS resolvers in /etc/resolv.conf, with rotate off.

What is the expected behavior?
The resolvers will be tried in order.

What went wrong?
It seems that Chrome sometimes gets into a state where some of the revolvers are skipped. The still appear in chrome://net-internals/#dns, but tcpdump show they are not even tried.

Perhaps they timed out and were marked "down"?

The resolvers are not used for at least several minutes (IDK how long it takes, haven't been patient enough to wait it out).

Did this work before? N/A 

Chrome version: 57.0.2987.110  Channel: stable
OS Version: 57
Flash Version: Shockwave Flash 25.0 r0

My system DNS tries the resolvers in order each time. Chrome should as well. Or at least if it does short-circuit, do so for a relatively short amount of time, e.g. 30 seconds.