New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 2 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Jun 2016
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: ----

Blocked on:
issue 545118

Sign in to add a comment

Issue 545123: Experiment with use Async DNS in Cronet

Reported by, Oct 19 2015 Project Member

Issue description

Currently Async DNS is not used neither by Chrome nor by Cronet on Android.
We should experiment with it in Cronet to measure potential benefits.

Comment 1 by, Oct 19 2015

Worth noting this has never been enabled (Even as a field trial) on Android, so users could run into a bunch of unexpected issues.

Comment 2 by, Oct 31 2015


Comment 3 by, Nov 6 2015

Found the original design doc of async DNS: goto/asyncdns (in case someone else like me who don't know how the build-in dns client works).

Comment 4 by, Dec 9 2015

Project Member
The following revision refers to this bug:

commit e92c4096de6e0b7761e4e97850245948878c0446
Author: pauljensen <>
Date: Wed Dec 09 19:13:48 2015

[Cronet] Allow experimenting with Chrome's internal DNS resolver.

Enable by adding "AsyncDNS":{"enable":true} to experimental options.
By default fallback to getaddrinfo() is enabled.
Note that this is only for experimentation because:
1. It's never been used in production
2. It's likely not the desired long term solution on
   Android as it does not contribute to the O/S DNS cache.

BUG= 545123 

Review URL:

Cr-Commit-Position: refs/heads/master@{#364117}


Comment 5 by, Jun 16 2016

Status: Fixed (was: Available)
We can now run experiments.

Sign in to add a comment