New issue
Advanced search Search tips

Issue 924334 link

Starred by 1 user

Issue metadata

Status: Unconfirmed
Owner: ----
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

/etc/resolv.conf resetting itself to broken nameserver every time I open terminal

Reported by laude...@gmail.com, Today (7 hours ago)

Issue description

Chrome Version: Google Chrome 71.0.3578.127
Chrome OS Version: Platform 11151.113.1
Chrome OS Platform: Pixelbook
Network info: Any network I connect to

Steps To Reproduce:
(1) Open terminal
(2) Try to ping google.com

Expected Result:
ping working

Actual Result:
failure in name resolution

Every single time I re-open the terminal, /etc/resolv.conf's nameserver is an IP address (in the 100.0.0.0/8 subnet, I think) that I do not recognize. I reset it to 1.1.1.1 and am then able to resolve things again. I'm not sure why this is happening, but settings in /etc/resolv.conf should almost definitely persist across reboots of the linux VM!

 

Sign in to add a comment