New issue
Advanced search Search tips

Issue 886933 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 829192
Owner: ----
Closed: Sep 28
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

DNS failure due to hardcoded DNS in Crostini ignoring ChromeOS (host) DNS settings

Reported by llun...@gmail.com, Sep 19

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 11021.13.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.16 Safari/537.36
Platform: 11021.13.0 (Official Build) dev-channel eve

Steps to reproduce the problem:
1. Connect to a local Wlan or a VPN
2. Start Terminal app
3. Try to resolve an non-public host name

What is the expected behavior?
Crostini should resolve the non-public host name against the DNS servers set by local dhcp or the VPN

What went wrong?
Crostini uses hard-coded public Google name servers and therefor can not resolve local names.

Did this work before? N/A 

Chrome version: 70.0.3538.16  Channel: dev
OS Version: 11021.13.0
Flash Version: 

See the following link for a discussion of the issue: https://www.reddit.com/r/Crostini/comments/8fz9ox/container_dns_issues/

This is related to https://bugs.chromium.org/p/chromium/issues/detail?id=829192
 
Components: OS>Systems>Containers
Mergedinto: 829192
Status: Duplicate (was: Unconfirmed)

Sign in to add a comment