New issue
Advanced search Search tips

Issue 829735 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Dec 18
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug


Show other hotlists

Hotlists containing this issue:
Chrome-Bug-Cleanup


Sign in to add a comment

BuiltInDnsClientEnabled -- unclear docs

Project Member Reported by tnagel@chromium.org, Apr 6 2018

Issue description

Please clarify the default state in the policy docs: If the policy is unset and the user doesn't configure any flags, is built-in DNS used or not?
 
Labels: Enterprise-Triaged
Status: Available (was: Untriaged)
Hello, I also have the same question. And an additional question of how to setup "BuiltInDnsClientEnabled" in Chrome?

Comment 3 by tnagel@chromium.org, Apr 23 2018

Cc: atwilson@chromium.org
Hey Drew, it seems this fell through the cracks.
Owner: mge...@chromium.org
mgersh: can you help here? I don't understand how kBuiltInDnsClientEnabled (https://cs.chromium.org/chromium/src/chrome/browser/io_thread.cc?rcl=2aea13c48978329e7ee2c768d0fa88a2b5faed3c&l=378) behaves for consumers (seems like it's impacted by field trials, varies by platform, etc).

Comment 5 by mge...@chromium.org, Apr 23 2018

Components: Internals>Network>DNS
Owner: pauljensen@chromium.org
Status: Assigned (was: Available)
Labels: Hotlist-Enterprise
Chrome's built-in DNS client (as opposed to using the system DNS resolver via getaddrinfo()) is controlled by a couple mechanisms.

It is enabled by default for Mac and ChromeOS here:
https://cs.chromium.org/chromium/src/chrome/common/chrome_features.cc?rcl=dabbfaf85eca64fa2134bb4b1008cf7e55f2453b&l=75

It is enabled by field trial for Android as per Issue 768874.
Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time.
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Wednesday, 12/12/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!
@tnagel: can you clarify which docs you are talking about?
Owner: tnagel@chromium.org
Assigning to tnagel@ since further action is pending their response.
Owner: pauljensen@chromium.org
I'm referring to these docs: http://www.chromium.org/administrators/policy-list-3#BuiltInDnsClientEnabled
Project Member

Comment 13 by bugdroid1@chromium.org, Dec 18

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

commit 488b7d4f4efddae7c5bb6d4e32e40c47f07515a8
Author: Paul Jensen <pauljensen@chromium.org>
Date: Tue Dec 18 15:16:20 2018

Clarify BuiltInDnsClientEnabled policy default behavior

Bug:  829735 
Change-Id: I696e786550c750b6e17a635b20ddf8dee5bee94c
Reviewed-on: https://chromium-review.googlesource.com/c/1380575
Reviewed-by: Lutz Justen <ljusten@chromium.org>
Commit-Queue: Paul Jensen <pauljensen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#617494}
[modify] https://crrev.com/488b7d4f4efddae7c5bb6d4e32e40c47f07515a8/components/policy/resources/policy_templates.json

Status: Fixed (was: Started)

Sign in to add a comment