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

Issue 704662 link

Starred by 0 users
Status: Fixed
Owner:
█ mge...@chromium.org
Last visit > 30 days ago
Closed: Aug 2017
Cc:
pauljensen@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

When getting DNS config on Android, old list of nameservers isn't cleared

Project Member Reported by mge...@chromium.org, Mar 23 2017 
I switched back and forth between cell and wifi a few times and got lists of nameservers in netlog that look like this (in order):

["[2001:4860:4860::8888]:53","[2001:4860:4860::8844]:53","[2001:4860:4860::8888]:53","[2001:4860:4860::8844]:53","[fd00:976a::9]:53","[fd00:976a::10]:53","[fd00:976a::9]:53","[fd00:976a::10]:53","[fd00:976a::9]:53","[fd00:976a::10]:53","192.168.1.1:53","[fd00:976a::9]:53","[fd00:976a::10]:53","[2001:4860:4860::8888]:53","[2001:4860:4860::8844]:53","[fd00:976a::9]:53","[fd00:976a::10]:53"]
["[2001:4860:4860::8888]:53","[2001:4860:4860::8844]:53","[2001:4860:4860::8888]:53","[2001:4860:4860::8844]:53","[fd00:976a::9]:53","[fd00:976a::10]:53","[fd00:976a::9]:53","[fd00:976a::10]:53","[fd00:976a::9]:53","[fd00:976a::10]:53","192.168.1.1:53","[fd00:976a::9]:53","[fd00:976a::10]:53","[2001:4860:4860::8888]:53","[2001:4860:4860::8844]:53","[fd00:976a::9]:53","[fd00:976a::10]:53","[2001:4860:4860::8888]:53","[2001:4860:4860::8844]:53"]
["[2001:4860:4860::8888]:53","[2001:4860:4860::8844]:53","[2001:4860:4860::8888]:53","[2001:4860:4860::8844]:53","[fd00:976a::9]:53","[fd00:976a::10]:53","[fd00:976a::9]:53","[fd00:976a::10]:53","[fd00:976a::9]:53","[fd00:976a::10]:53","192.168.1.1:53","[fd00:976a::9]:53","[fd00:976a::10]:53","[2001:4860:4860::8888]:53","[2001:4860:4860::8844]:53","[fd00:976a::9]:53","[fd00:976a::10]:53","[2001:4860:4860::8888]:53","[2001:4860:4860::8844]:53","[fd00:976a::9]:53","[fd00:976a::10]:53"]
["[2001:4860:4860::8888]:53","[2001:4860:4860::8844]:53","[2001:4860:4860::8888]:53","[2001:4860:4860::8844]:53","[fd00:976a::9]:53","[fd00:976a::10]:53","[fd00:976a::9]:53","[fd00:976a::10]:53","[fd00:976a::9]:53","[fd00:976a::10]:53","192.168.1.1:53","[fd00:976a::9]:53","[fd00:976a::10]:53","[2001:4860:4860::8888]:53","[2001:4860:4860::8844]:53","[fd00:976a::9]:53","[fd00:976a::10]:53","[2001:4860:4860::8888]:53","[2001:4860:4860::8844]:53","[fd00:976a::9]:53","[fd00:976a::10]:53","[2001:4860:4860::8888]:53","[2001:4860:4860::8844]:53"]

The info from ConnectivityService in logcat didn't look like this, so this is our bug, not Android's. This is Chrome 56 on Android N. Paul said that this is likely fixed in M and later starting with 57, but probably still happens on older devices.
Project Member

Comment 1 by bugdroid1@chromium.org, Aug 30 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/6051145dc296ec8d0990cdc2b2573b085173e5fa

commit 6051145dc296ec8d0990cdc2b2573b085173e5fa
Author: Miriam Gershenson <mgersh@chromium.org>
Date: Wed Aug 30 15:46:22 2017

On Android, clear nameservers before adding new ones

BUG= 704662 

Change-Id: I73415c5ea4370e65a7a69a48b94cdb43dbdda036
Reviewed-on: https://chromium-review.googlesource.com/627297
Commit-Queue: Miriam Gershenson <mgersh@chromium.org>
Reviewed-by: Julia Tuttle <juliatuttle@chromium.org>
Cr-Commit-Position: refs/heads/master@{#498473}
[modify] https://crrev.com/6051145dc296ec8d0990cdc2b2573b085173e5fa/net/dns/dns_config_service_posix.cc
[modify] https://crrev.com/6051145dc296ec8d0990cdc2b2573b085173e5fa/net/dns/dns_config_service_posix_unittest.cc

Comment 2 by mge...@chromium.org, Aug 30 2017

Status: Fixed (was: Assigned)
►

Sign in to add a comment