由于某种原因，我的 Ubuntu 22.04 LTS 安装的默认 DNS 客户端经常死机，但仍然是偶尔出现。我确信是 DNS 客户端的问题，因为命令
sudo systemctl restart system-resolved
在短时间内解决了我的问题。即使不重新启动 dns-client，我仍然可以通过其 IP 地址 ping 互联网上的服务器。
我有一台联想 Ideapad 3 15ALC6 笔记本电脑，安装了 Ubuntu 22.04 LTS 实例并进行了所有更新。由于笔记本电脑没有以太网适配器，我通过 USB 连接了一个以太网适配器。即使没有以太网适配器，只使用 WLAN，我也会遇到同样的问题。
注意：由于机身最大尺寸的原因，一些硬件信息被删除。
##更新## 硬件信息已删除，因为空间严重不足（本帖 30k 个字符）。如果您需要硬件信息，请告诉我如何获取您所需的特定数据。
我甚至不知道如何开始排除故障或在互联网上搜索问题所在。你可以想象，目前的情况令人沮丧。
如果您能给我任何关于如何解决该问题的提示，我将不胜感激:)
你好，Ronny
##更新##未运行：
systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2022-10-26 06:32:43 CEST; 12h ago
Docs: man:systemd-resolved.service(8)
man:org.freedesktop.resolve1(5)
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
Main PID: 561 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 11691)
Memory: 9.2M
CPU: 13.201s
CGroup: /system.slice/systemd-resolved.service
└─561 /lib/systemd/systemd-resolved
Okt 26 06:32:45 ronaldIdeaPad3 systemd-resolved[561]: enx00e04c692628: Bus client set search domain list to: fritz.box
Okt 26 06:32:45 ronaldIdeaPad3 systemd-resolved[561]: enx00e04c692628: Bus client set default route setting: yes
Okt 26 06:32:45 ronaldIdeaPad3 systemd-resolved[561]: enx00e04c692628: Bus client set DNS server list to: 192.168.178.67
Okt 26 06:32:47 ronaldIdeaPad3 systemd-resolved[561]: enx00e04c692628: Bus client set DNS server list to: 192.168.178.67, 2a02:908:d96:d660:402a:7fa5:de68:2dfc
Okt 26 06:32:49 ronaldIdeaPad3 systemd-resolved[561]: wlp1s0: Bus client set search domain list to: fritz.box
Okt 26 06:32:49 ronaldIdeaPad3 systemd-resolved[561]: wlp1s0: Bus client set default route setting: yes
Okt 26 06:32:49 ronaldIdeaPad3 systemd-resolved[561]: wlp1s0: Bus client set DNS server list to: 192.168.178.67
Okt 26 06:32:51 ronaldIdeaPad3 systemd-resolved[561]: wlp1s0: Bus client set DNS server list to: 192.168.178.67, 2a02:908:d96:d660:402a:7fa5:de68:2dfc
Okt 26 08:20:56 ronaldIdeaPad3 systemd-resolved[561]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 192.168.178.67.
Okt 26 11:53:45 ronaldIdeaPad3 systemd-resolved[561]: Grace period over, resuming full feature set (UDP+EDNS0) for DNS server 192.168.178.67.
未运行：
ronald@ronaldIdeaPad3:~$ sudo systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2022-10-26 19:13:35 CEST; 14min ago
Docs: man:systemd-resolved.service(8)
man:org.freedesktop.resolve1(5)
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
Main PID: 25991 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 11691)
Memory: 4.6M
CPU: 1.124s
CGroup: /system.slice/systemd-resolved.service
└─25991 /lib/systemd/systemd-resolved
Okt 26 19:13:35 ronaldIdeaPad3 systemd[1]: Starting Network Name Resolution...
Okt 26 19:13:35 ronaldIdeaPad3 systemd-resolved[25991]: Positive Trust Anchors:
Okt 26 19:13:35 ronaldIdeaPad3 systemd-resolved[25991]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Okt 26 19:13:35 ronaldIdeaPad3 systemd-resolved[25991]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.a>
Okt 26 19:13:35 ronaldIdeaPad3 systemd-resolved[25991]: Using system hostname 'ronaldIdeaPad3'.
Okt 26 19:13:35 ronaldIdeaPad3 systemd[1]: Started Network Name Resolution.
刚刚重启：
ronald@ronaldIdeaPad3:~$
ronald@ronaldIdeaPad3:~$ sudo systemctl restart systemd-resolved
ronald@ronaldIdeaPad3:~$ sudo systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2022-10-26 19:13:35 CEST; 9s ago
Docs: man:systemd-resolved.service(8)
man:org.freedesktop.resolve1(5)
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
Main PID: 25991 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 11691)
Memory: 4.6M
CPU: 96ms
CGroup: /system.slice/systemd-resolved.service
└─25991 /lib/systemd/systemd-resolved
Okt 26 19:13:35 ronaldIdeaPad3 systemd[1]: Starting Network Name Resolution...
Okt 26 19:13:35 ronaldIdeaPad3 systemd-resolved[25991]: Positive Trust Anchors:
Okt 26 19:13:35 ronaldIdeaPad3 systemd-resolved[25991]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Okt 26 19:13:35 ronaldIdeaPad3 systemd-resolved[25991]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.a>
Okt 26 19:13:35 ronaldIdeaPad3 systemd-resolved[25991]: Using system hostname 'ronaldIdeaPad3'.
Okt 26 19:13:35 ronaldIdeaPad3 systemd[1]: Started Network Name Resolution.
编辑3：journalctl -u systemd-resolved
Okt 26 19:13:35 ronaldIdeaPad3 systemd[1]: Stopping Network Name Resolution...
Okt 26 19:13:35 ronaldIdeaPad3 systemd[1]: systemd-resolved.service: Deactivated successfully.
Okt 26 19:13:35 ronaldIdeaPad3 systemd[1]: Stopped Network Name Resolution.
Okt 26 19:13:35 ronaldIdeaPad3 systemd[1]: systemd-resolved.service: Consumed 13.227s CPU time.
Okt 26 19:13:35 ronaldIdeaPad3 systemd[1]: Starting Network Name Resolution...
Okt 26 19:13:35 ronaldIdeaPad3 systemd-resolved[25991]: Positive Trust Anchors:
Okt 26 19:13:35 ronaldIdeaPad3 systemd-resolved[25991]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Okt 26 19:13:35 ronaldIdeaPad3 systemd-resolved[25991]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.a>
Okt 26 19:13:35 ronaldIdeaPad3 systemd-resolved[25991]: Using system hostname 'ronaldIdeaPad3'.
Okt 26 19:13:35 ronaldIdeaPad3 systemd[1]: Started Network Name Resolution.
Okt 26 19:28:25 ronaldIdeaPad3 systemd[1]: Stopping Network Name Resolution...
Okt 26 19:28:25 ronaldIdeaPad3 systemd[1]: systemd-resolved.service: Deactivated successfully.
Okt 26 19:28:25 ronaldIdeaPad3 systemd[1]: Stopped Network Name Resolution.
Okt 26 19:28:25 ronaldIdeaPad3 systemd[1]: systemd-resolved.service: Consumed 1.219s CPU time.
Okt 26 19:28:25 ronaldIdeaPad3 systemd[1]: Starting Network Name Resolution...
Okt 26 19:28:25 ronaldIdeaPad3 systemd-resolved[26234]: Positive Trust Anchors:
Okt 26 19:28:25 ronaldIdeaPad3 systemd-resolved[26234]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Okt 26 19:28:25 ronaldIdeaPad3 systemd-resolved[26234]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.a>
lines 1428-1481/1483 100%
答案1
更新（针对其他人遇到的问题）：经过短暂的等待和定期的更新安装（apt-get update、apt-get upgrade）后，这个问题中描述的效果只会偶尔发生，现在几乎不会发生。
我相信这是网络管理器的问题，它之前已被修补过。
因为我没有找到关于这个论文的任何提示，所以我不能毫无疑问地说这是我的问题的原因。