This bug is forked from crbug.com/672952

Application Version (from "Chrome Settings > About Chrome"): 56.0.2924.18
Android Build Number (from "Android Settings > About Phone/Tablet"): LXI22.50-62
Device: Moto E

Steps to reproduce:

1) Put the device on a slow network (e.g., GIN-2gpoor)
2) Try to load a page that exists, e.g., http://aws1.mdw.la/fw
3) Wait for 30-60 seconds.
4) See a network error page with DNS_PROBE_FINISHED_NXDOMAIN

In this case the domain aws1.mdw.la absolutely exists and if you retry loading the page it will resolve and (eventually) load. However, in some cases Chrome is showing a DNS probe failure. The real root cause is that the device is on a slow network. My concern here is that users see this error and misinterpret it as a DNS failure.

See internal doc for more details on experiment:
https://docs.google.com/a/google.com/document/d/19ctmz25Dd4FsCUeFJeaIhWGBTENcVo5_KD626fRE4DM/edit?usp=sharing