Difference between revisions of "Journalctl -u systemd-resolved"
Jump to navigation
Jump to search
Tags: Mobile web edit, Mobile edit |
|||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | {{lowercase}} | |
| − | |||
Nov 10 10:08:21 SERVER systemd[1]: systemd-resolved.service: Failed to run 'start' task: [[No space left on device]] | Nov 10 10:08:21 SERVER systemd[1]: systemd-resolved.service: Failed to run 'start' task: [[No space left on device]] | ||
| − | |||
Apr 05 11:05:39 hostname.example.com systemd[1]: Starting Network Name Resolution... | Apr 05 11:05:39 hostname.example.com systemd[1]: Starting Network Name Resolution... | ||
| Line 12: | Line 10: | ||
Apr 05 11:05:39 hostname.example.com systemd-resolved[446099]: Using system hostname ' hostname.example.com'. | Apr 05 11:05:39 hostname.example.com systemd-resolved[446099]: Using system hostname ' hostname.example.com'. | ||
Apr 05 11:05:39 hostname.example.com systemd[1]: Started Network Name Resolution. | Apr 05 11:05:39 hostname.example.com systemd[1]: Started Network Name Resolution. | ||
| + | |||
| + | Apr 05 11:05:40 hostname.example.com systemd-resolved[446099]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. | ||
| + | |||
| + | Apr 06 12:57:35 hostname.example.com systemd[1]: Stopping Network Name Resolution... | ||
| + | Apr 06 12:57:37 hostname.example.com systemd[1]: systemd-resolved.service: Succeeded. | ||
| + | Apr 06 12:57:37 hostname.example.com systemd[1]: Stopped Network Name Resolution. | ||
== See also == | == See also == | ||
Latest revision as of 17:58, 7 September 2021
Nov 10 10:08:21 SERVER systemd[1]: systemd-resolved.service: Failed to run 'start' task: No space left on device
Apr 05 11:05:39 hostname.example.com systemd[1]: Starting Network Name Resolution... Apr 05 11:05:39 hostname.example.com systemd-resolved[446099]: Positive Trust Anchors: Apr 05 11:05:39 hostname.example.com systemd-resolved[446099]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Apr 05 11:05:39 hostname.example.com systemd-resolved[446099]: Negative trust anchors: 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.arpa 21.172.in- addr.arpa 22.172.in-addr. arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test Apr 05 11:05:39 hostname.example.com systemd-resolved[446099]: Using system hostname ' hostname.example.com'. Apr 05 11:05:39 hostname.example.com systemd[1]: Started Network Name Resolution.
Apr 05 11:05:40 hostname.example.com systemd-resolved[446099]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Apr 06 12:57:35 hostname.example.com systemd[1]: Stopping Network Name Resolution... Apr 06 12:57:37 hostname.example.com systemd[1]: systemd-resolved.service: Succeeded. Apr 06 12:57:37 hostname.example.com systemd[1]: Stopped Network Name Resolution.
See also[edit]
systemd-resolve:systemd-resolve --help,systemd-resolve --status,/etc/systemd/resolved.conf,systemd-resolve --statistics,resolvectl status,journalctl -u systemd-resolved,systemd-resolve --set-dns,systemctl start systemd-resolved- {systemd-journald:
journalctl,/etc/systemd/journald.conf,journalctl logs,journalctl --list-boots,journalctl --disk-usage,journalctl -u kubelet,journalctl -u prometheus,journalctl --help
Advertising:
