我的google云VM无法解析外部URL,请看屏幕截图。

在解决这个问题上有任何帮助,非常感谢
建议附加resolv.conf屏幕截图

重新启动系统后,解决以下错误
systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2020-02-13 10:25:59 UTC; 41s ago
Docs: man:systemd-resolved.service(8)
https://www.freedesktop.org/wiki/Software/systemd/resolved
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
Main PID: 10316 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 4915)
CGroup: /system.slice/systemd-resolved.service
└─10316 /lib/systemd/systemd-resolved
Feb 13 10:26:38 dev.seconize.co systemd-resolved[10316]: Failed to open /etc/hosts: Permission denied
Feb 13 10:26:38 dev.seconize.co systemd-resolved[10316]: Failed to start query: Permission denied
Feb 13 10:26:40 dev.seconize.co systemd-resolved[10316]: Failed to open /etc/hosts: Permission denied
Feb 13 10:26:40 dev.seconize.co systemd-resolved[10316]: Failed to start query: Permission denied
Feb 13 10:26:40 dev.seconize.co systemd-resolved[10316]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with
Feb 13 10:26:40 dev.seconize.co systemd-resolved[10316]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with
Feb 13 10:26:40 dev.seconize.co systemd-resolved[10316]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with
Feb 13 10:26:40 dev.seconize.co systemd-resolved[10316]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with
Feb 13 10:26:40 dev.seconize.co systemd-resolved[10316]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with
Feb 13 10:26:40 dev.seconize.co systemd-resolved[10316]: Server returned error NXDOMAIN, mit发布于 2020-02-18 12:13:28
正如@sashank在评论中解释的那样,造成此问题的原因是文件/etc/hosts的权限错误。当权限固定后,重新启动systemd-resolved服务最终解决了这个问题。
https://serverfault.com/questions/1002902
复制相似问题