Feature request: ability to add custom DNS entries for development purposes |
||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 8350.68.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Steps to reproduce the problem: 1. Navigate to "chrome://settings" 2. Type "dns" into search 3. Type "host" into search What is the expected behavior? There should be an option that looks like: "Custom DNS Configuration" And that should allow one to both provide the ability to set the DNS server addresses as well as the ability to add "Host Overrides" or "DNS Overrides" that are the equivalent of modifying "/etc/hosts". The ability to modify "/etc/hosts" is very useful for development purposes (e.g. so that a development server on a remote machine expecting a particular value for "Host:" is able to receive it). What went wrong? There is no ability to customize "/etc/hosts", and DNS resolution can only be modified at the router (not within the Chromebook, itself). Did this work before? N/A Chrome version: 52.0.2743.116 Channel: n/a OS Version: 8350.68.0 Flash Version:
,
Sep 19 2016
I think this would be a good idea to add, however we would likely only want to persist it when devtools is open to help reduce chance of an attacker changing this setting and redirect popular websites to malicious site. +paulirish, What do you think? Maybe too high of a security risk?
,
Sep 20 2016
,
Sep 22 2016
This seems like a chromeos specific request, right? I don't think this'd be too neccessary on mac/linux/windows.
,
Sep 22 2016
With respect to comment #2, I think doing this only when devtools is open is fine for the "/etc/hosts" modification, but not really for the DNS server. For example, if I want to make my Chromebook point at Google's Public DNS servers (rather than the ISP's servers), I shouldn't need to constantly browse with devtools open. Instead of requiring devtools to be open, why not require the user to have very recently authenticated or prompt the user to authenticate?
,
Sep 26 2016
+stevenjb, are you guys working on anything for ChromeOS around this?
,
Sep 26 2016
On Chrome OS, Nameservers for a network configuration can be set via settings. Unfortunately because the network configuration page for each network is generated, it won't show up in a search.
,
Sep 26 2016
We've decided to not pursue supporting custom DNS inside of DevTools. While it could be useful, we have higher priority items at this time. To me, it'd make sense for this feature to land in ChromeOS rather than in the devtools (shared across all platforms)
,
Sep 27 2016
Please note, there are actually two feature requests here:
1. Custom DNS server address (e.g. to point to public DNS). This would,
indeed, make more sense in Chrome OS than in general DevTools
2. The ability to manually override the resolution of specific domains
(similar to manually editing "/etc/hosts"). This, on the other hand,
would make a lot of sense either in DevTools or in Chrome OS.
Regardless of where these are best implemented, can you triage to the appropriate place rather than simply closing the request?
,
Sep 27 2016
> can you triage to the appropriate place rather than simply closing the request? Sure, sending to the Chrome OS side of things.
,
Oct 11 2016
,
May 9 2017
,
May 25 2017
,
May 25 2017
To be able to set/force DNS settings of chrome managed devices remotely from the chromeOS Admin Console is a necessity for our environment. This would be ideal and would save us a headache or ten.
,
May 28 2018
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by einbinder@chromium.org
, Sep 19 2016Labels: -Type-Bug -Pri-2 Pri-3 Type-Feature
Owner: allada@chromium.org
Status: Assigned (was: Unconfirmed)